On Wed, Jul 16, 2008 at 4:41 PM, Damien Herraud <d.herraud at gmail.com> wrote: > Hi, > > Now that SDP negociation and sending an INVITE method is working for my > app, I have an issue with the ACK request. > > Indeed when I try to make a call between two user agents both built with > my app, INVITE is sent correctly, OK is received but ACK does not reach the > callee. So the callee sends OK indefinitely. I have captured the packets > with Wireshark and the main difference between an ACK packet sent by my app > and an ACK sent by simpleua (which works) is : > > simpleua : Request-Line: ACK sip:bob at 137.122.88.181:5060;transport=UDP > SIP/2.0 > my app : Request-Line: ACK sip:bob at open-ims.test SIP/2.0 > > I don't know why it's different since I reused simpleua code for invite > dialog (the main difference is that I register on an IMS network with my > app). > > The request URI in ACK contains the URI in the Contact header that remote sends in 2xx response, or, the top-most route in case strict route is used. So just check these two fields. > > > Even more surprising, when I make a call from my app to pjsua, I get a > message 488 (Not Acceptable Here, this is normal since I don't have the same > codecs) from pjsua and my app answers with an ACK that reaches its > destination ! > > ACK for non-2xx response has different rule (it's sent to the original INVITE destination rather than the Contact in the response). -benny -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.pjsip.org/pipermail/pjsip_lists.pjsip.org/attachments/20080716/2b47bbcd/attachment.html
