[Home]

Summary:ASTERISK-22445: res_pjsip_messaging: Message technology registers itself as SIP, preventing compatibility with chan_sip
Reporter:Matt Jordan (mjordan)Labels:
Date Opened:2013-09-03 11:28:31Date Closed:2013-09-18 09:39:06
Priority:MajorRegression?
Status:Closed/CompleteComponents:Resources/res_pjsip_messaging
Versions:12.0.0-alpha1 Frequency of
Occurrence
Related
Issues:
Environment:Attachments:
Description:The message technology is currently registering itself as 'sip'. This results in its registration being rejected if {{chan_sip}} is also loaded:

{noformat}
*CLI> module load res_pjsip_messaging.so
[Sep  3 11:25:57] ERROR[5170]: message.c:1252 ast_msg_tech_register: Message technology already registered for 'sip'
Unable to load module res_pjsip_messaging.so
Command 'module load res_pjsip_messaging.so' failed.
*CLI>
{noformat}

This should probably register itself as {{pjsip}}. That would allow it to work at the same time as {{chan_sip}}, and would also differentiate between which channel driver ends up servicing the message. It's also inline with dialing and other mechanisms that reference the new SIP stack.
Comments: