The Contact fields in messages sent from different User Agents are not expected to be the same. The Contact header provides a URL which can be used to contact the UA about the dialog. If UAs were sending the same Contact as other UAs, they would be directing future requests to a different server.
It is the Request URI of the ACK that should match the Contact from the 200 OK. The ACK is not required to have a Contact at all, as the UAC’s Contact was already provided in the INVITE. Ben Newlin From: Users <users-boun...@lists.opensips.org> on behalf of Social Boh <soc...@bohboh.info> Date: Thursday, November 9, 2023 at 9:16 AM To: OpenSIPS users mailling list <users@lists.opensips.org> Subject: [OpenSIPS-Users] Strange ACK between OpenSIPS and Kamailio EXTERNAL EMAIL - Please use caution with links and attachments ________________________________ Hello list, I have a problem in communication between an OpenSIPs and a Kamailio. The call comes from OpenSIPs to Kamailio, it is answered but the ACK that OpenSIPs sends to Kamailio I think is not correct: 200OK from Kamailio to OpenSIPs: Contact: <sip:194.195.XXX.XXX:49999><sip:194.195.XXX.XXX:49999> ACK from OpenSIPs to Kamailio: Contact: <sip:u...@177.242.xxx.xxx;did=86a.799c1654><sip:u...@177.242.xxx.xxx;did=86a.799c1654> I think the ACK Contact Header from OpenSIPs to Kamailio should have the same 200 OK content 194.195.XXX.XXX is a Asterisk PBX 177.242.XXX.XXX is OpenSIPs Result Kamailio don't send ACK to Asterisk PBX and the call ends about 30 seconds. Any hint, please? -- --- I'm SoCIaL, MayBe
_______________________________________________ Users mailing list Users@lists.opensips.org http://lists.opensips.org/cgi-bin/mailman/listinfo/users
