[Freeswitch-users] FS Choking on a 200 Response w/ a Duplicate "From" Header

[JP]

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 at 10.191.210.147>;tag=By8FpSr2m6NvF
   From: "" <sip:0000000000 at 10.191.210.147>;tag=By8FpSr2m6NvF
   To: <sip:1000 at 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
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.freeswitch.org/pipermail/freeswitch-users/attachments/20130605/e03fc4b5/attachment.html