FS Choking on a 200 Response w/ a Duplicate "From" Header
I thought I would bounce this off the mailing list before filing a Jira ticket. I'm facing an issue where FS doesn't acknowledge a 200 OK response with a duplicate "From" header: recv 422 bytes from udp/[10.191.210.149]:5060 at 17:21:22.634270: ------------------------------------------------------------------------ SIP/2.0 200 OK Via: SIP/2.0/UDP 10.191.210.147:5080;rport;branch=z9hG4bKNv1g56Djj6BKj From: "" <sip:0000000000@10.191.210.147>;tag=By8FpSr2m6NvF From: "" <sip:0000000000@10.191.210.147>;tag=By8FpSr2m6NvF To: <sip:1000@10.191.210.149:5060>;tag=1 Call-ID: 1efaef87-48a7-1231-d08a-000c29ccde0a CSeq: 44890363 INVITE Contact: <sip:10.191.210.149:5060;transport=UDP> Content-Type: application/sdp Content-Length: 0 Although I've not yet stepped through the code, it is my suspicion that the Sofia SIP stack is not accepting the response. Aside from the re-transmissions of the response that I'm seeing in the logs, there are no other error, info, or trace statements coming from any other FS module. RFC 3261 seems a bit vague in my opinion as to whether or not this is even allowed. As a side note, this issue came up while doing integration testing with OpenSER 1.3.4. OpenSER seems to stick in the duplicate From header whenever it does a serial proxy to multiple carriers and the first carrier leg times out. I'm wondering if anyone on the mailing list was familiar with this issue and perhaps knew of some fix/workaround on the FreeSWITCh end. Thanks, JP
Is 2 From headers even technically allow? On 6/5/13 2:03 PM, "JP" <jaykris@gmail.com> wrote:
I thought I would bounce this off the mailing list before filing a Jira ticket.
I'm facing an issue where FS doesn't acknowledge a 200 OK response with a duplicate "From" header:
recv 422 bytes from udp/[10.191.210.149]:5060 at 17:21:22.634270: ------------------------------------------------------------------------ SIP/2.0 200 OK Via: SIP/2.0/UDP 10.191.210.147:5080;rport;branch=z9hG4bKNv1g56Djj6BKj From: "" <sip:0000000000@10.191.210.147 <mailto:sip%3A0000000000@10.191.210.147> >;tag=By8FpSr2m6NvF From: "" <sip:0000000000@10.191.210.147 <mailto:sip%3A0000000000@10.191.210.147> >;tag=By8FpSr2m6NvF To: <sip:1000@10.191.210.149:5060 <http://sip:1000@10.191.210.149:5060>
;tag=1 Call-ID: 1efaef87-48a7-1231-d08a-000c29ccde0a CSeq: 44890363 INVITE Contact: <sip:10.191.210.149:5060;transport=UDP> Content-Type: application/sdp Content-Length: 0
Although I've not yet stepped through the code, it is my suspicion that the Sofia SIP stack is not accepting the response. Aside from the re-transmissions of the response that I'm seeing in the logs, there are no other error, info, or trace statements coming from any other FS module. RFC 3261 seems a bit vague in my opinion as to whether or not this is even allowed.
As a side note, this issue came up while doing integration testing with OpenSER 1.3.4. OpenSER seems to stick in the duplicate From header whenever it does a serial proxy to multiple carriers and the first carrier leg times out. I'm wondering if anyone on the mailing list was familiar with this issue and perhaps knew of some fix/workaround on the FreeSWITCh end.
Thanks,
JP
_________________________________________________________________________ Professional FreeSWITCH Consulting Services: consulting@freeswitch.org http://www.freeswitchsolutions.com
FreeSWITCH-powered IP PBX: The CudaTel Communication Server http://www.cudatel.com
Official FreeSWITCH Sites http://www.freeswitch.org http://wiki.freeswitch.org http://www.cluecon.com
FreeSWITCH-users mailing list FreeSWITCH-users@lists.freeswitch.org http://lists.freeswitch.org/mailman/listinfo/freeswitch-users UNSUBSCRIBE:http://lists.freeswitch.org/mailman/options/freeswitch-users http://www.freeswitch.org
-- Ken http://www.FreeSWITCH.org http://www.ClueCon.com http://www.OSTAG.org irc.freenode.net #freeswitch
Yes, good question. But it looks like OpenSER is inserting the duplicate
From header and the RFC specifically does not say that this is illegal.
-JP On Wed, Jun 5, 2013 at 12:14 PM, Ken Rice <krice@freeswitch.org> wrote:
Is 2 From headers even technically allow?
On 6/5/13 2:03 PM, "JP" <jaykris@gmail.com> wrote:
I thought I would bounce this off the mailing list before filing a Jira ticket.
I'm facing an issue where FS doesn't acknowledge a 200 OK response with a duplicate "From" header:
recv 422 bytes from udp/[10.191.210.149]:5060 at 17:21:22.634270: ------------------------------------------------------------------------ SIP/2.0 200 OK Via: SIP/2.0/UDP 10.191.210.147:5080;rport;branch=z9hG4bKNv1g56Djj6BKj From: "" <sip:0000000000@10.191.210.147 < mailto:sip%3A0000000000@10.191.210.147 <sip%3A0000000000@10.191.210.147>>
;tag=By8FpSr2m6NvF From: "" <sip:0000000000@10.191.210.147 < mailto:sip%3A0000000000@10.191.210.147 <sip%3A0000000000@10.191.210.147>> ;tag=By8FpSr2m6NvF To: <sip:1000@10.191.210.149:5060 <http://sip:1000@10.191.210.149:5060> ;tag=1
Call-ID: 1efaef87-48a7-1231-d08a-000c29ccde0a CSeq: 44890363 INVITE Contact: <sip:10.191.210.149:5060;transport=UDP> Content-Type: application/sdp Content-Length: 0
Although I've not yet stepped through the code, it is my suspicion that the Sofia SIP stack is not accepting the response. Aside from the re-transmissions of the response that I'm seeing in the logs, there are no other error, info, or trace statements coming from any other FS module. RFC 3261 seems a bit vague in my opinion as to whether or not this is even allowed.
As a side note, this issue came up while doing integration testing with OpenSER 1.3.4. OpenSER seems to stick in the duplicate From header whenever it does a serial proxy to multiple carriers and the first carrier leg times out. I'm wondering if anyone on the mailing list was familiar with this issue and perhaps knew of some fix/workaround on the FreeSWITCh end.
Thanks,
JP
------------------------------ _________________________________________________________________________ Professional FreeSWITCH Consulting Services: consulting@freeswitch.org http://www.freeswitchsolutions.com
FreeSWITCH-powered IP PBX: The CudaTel Communication Server http://www.cudatel.com
Official FreeSWITCH Sites http://www.freeswitch.org http://wiki.freeswitch.org http://www.cluecon.com
FreeSWITCH-users mailing list FreeSWITCH-users@lists.freeswitch.org http://lists.freeswitch.org/mailman/listinfo/freeswitch-users UNSUBSCRIBE:http://lists.freeswitch.org/mailman/options/freeswitch-users http://www.freeswitch.org
-- Ken *http://www.FreeSWITCH.org http://www.ClueCon.com http://www.OSTAG.org *irc.freenode.net #freeswitch
_________________________________________________________________________ Professional FreeSWITCH Consulting Services: consulting@freeswitch.org http://www.freeswitchsolutions.com
FreeSWITCH-powered IP PBX: The CudaTel Communication Server http://www.cudatel.com
Official FreeSWITCH Sites http://www.freeswitch.org http://wiki.freeswitch.org http://www.cluecon.com
FreeSWITCH-users mailing list FreeSWITCH-users@lists.freeswitch.org http://lists.freeswitch.org/mailman/listinfo/freeswitch-users UNSUBSCRIBE:http://lists.freeswitch.org/mailman/options/freeswitch-users http://www.freeswitch.org
participants (2)
-
JP
-
Ken Rice