Summary:	ASTERISK-24777: chan_sip and chan_pjsip cannot coexist when using websocket transport
Reporter:	PowerPBX (PowerPBX)	Labels:
Date Opened:	2015-02-10 13:05:07.000-0600	Date Closed:	2015-02-10 13:21:35.000-0600
Priority:	Critical	Regression?
Status:	Closed/Complete	Components:	Channels/chan_sip/WebSocket
Versions:	12.8.1 13.2.0	Frequency of Occurrence
Related Issues:	is duplicated by ASTERISK-24106 WebSockets Automatically decides what driver it will use
Environment:		Attachments:
Description:	While testing WebRTC I discovered that I cannot connect with a chan_pjsip extension when chan_sip is enabled at the same time even though it is listening on a different udp port.  The extension is not found to be a chan_sip extension and authentication fails. This occurs even if there are no chan_sip extensions set to transport=ws.  As far as I can tell there is no way to prevent this other than disabling chan_sip. One possible improvement would be to add a feature that prevents chan_sip from listening to the websocket port.  Another possible improvement would be to allow chan_sip and chan_pjsip to listen on different websocket ports if that is architecturally possible.
Comments:	By: PowerPBX (PowerPBX) 2015-02-10 13:09:33.013-0600 A 3rd possible improvement and possibly the best would be to have have the WebRTC extension try authenticate to both chan_sip and chan_pjsip.  Perhaps it is supposed to do that and this is a bug? By: Matt Jordan (mjordan) 2015-02-10 13:20:21.929-0600 No, it isn't supposed to do that. The two stacks are completely separate entities. By: Matt Jordan (mjordan) 2015-02-10 13:21:27.329-0600 This is a duplicate of ASTERISK-24106.