Hi Ranjit, Thank you for the suggestion. Currently, the ACK contains the same 5 methods in the allow as the INVITE. In both cases, it is: Allow: INVITE, ACK, CANCEL, OPTIONS, BYE
Maybe it is not so good readable in the mail. The long list of allowed methods is from the other server. Thanks, Peter Hi Peter the Allow header in ACK contains only 4 methods - it should contain all the methods (same as INVITE). Modify the ACK request's Allow header to include additional methods and re-test Regards Ranjit On Thu, Feb 20, 2020 at 4:05 AM Dr. Peter Sties <p.st...@memics.de[1]> wrote: Hi Richard, Thanks for the suggestion. The messages between the servers are transferred via a TCP connection (and all to the same IP address). So I think it should be well received by the server. I am still clueless... Thanks, Peter Am Donnerstag, 20. Februar 2020, 11:00:56 CET schrieb Richard Phernambucq:> Hi,> > Header-wise your ACK appears OK.> > I suspect your problem is that the destination address for the ACK> (200.200.200.200) is not routable from your SIP-server. This might> explain why the provider's server keeps retransmitting the response.> > BR,> Richard> > On 20-2-2020 10:39, Dr. Peter Sties wrote:> > Hi !> > > > I have some problems within a SIP trunc where our SIP-server talks> > directly to different provider SIP servers. One of these servers on the> > other side does not recognize our ACK to the 200 OK message. The other> > server keeps on repeating the 200 OK message.> > > > I have gone through all the header fields and compared it with the SIP> > specification and examples but I do not have clue why the other side does> > not accept our ACK. I would be great if someone can have a look at it and> > give me some hints.> > > > Here is the SIP-Trace:> > 2020-02-10 13:04:27.467 <-- send SIP TO 200.200.200.200 653 bytes> > INVITE sip: +491234567@200.200.200.200[2] SIP/2.0> > Via: SIP/2.0/TCP 100.100.100.100:5060;branch=z9hG4bKDGT5EGVPVDE4I146> > From:> > <sip: +4987654321@100.100.100.[3]100:5060;user=phone>;tag=C8UF20CAKNLTLJ18> > To: <sip:+491234567@200.200.200.[4]200:5060;user=phone>> > Call-ID: E4COR3MNVB8AK908> > CSeq: 1 INVITE> > Contact: <sip:100.100.100.100:5060[5]>> > Max-Forwards: 70> > Allow: INVITE, ACK, CANCEL, OPTIONS, BYE> > Content-Type: application/sdp> > Content-Length: 206> > > > v=0> > o=om 73848 1 IN IP4 100.100.100.100> > s=call> > c=IN IP4 100.100.100.100> > t=0 0> > m=audio 50012 RTP/ AVP 8 101> > a=rtpmap:8 PCMA/8000> > a=rtpmap:101 telephone-event/8000> > a=fmtp: 101 0-15> > a=ptime:20> > a=sendrecv> > > > 2020-02-10 13:04:27.481 --> rcvd SIP FROM TCP 1 288 bytes> > SIP/2.0 100 Trying> > Via: SIP/2.0/TCP 100.100.100.100:5060;branch=z9hG4bKDGT5EGVPVDE4I146> > From:> > <sip: +4987654321@100.100.100.[3]100:5060;user=phone>;tag=C8UF20CAKNLTLJ18> > To: <sip:+491234567@200.200.200.[4]200:5060;user=phone>> > Call-ID: E4COR3MNVB8AK908> > CSeq: 1 INVITE> > Content-Length: 0> > > > > > 2020-02-10 13:04:28.473 --> rcvd SIP FROM TCP 1 729 bytes> > SIP/2.0 183 Session Progress> > Via: SIP/2.0/TCP 100.100.100.100:5060;branch=z9hG4bKDGT5EGVPVDE4I146> > From:> > <sip:+4987654321@100.100.100.[3]100:5060;user=phone>;tag=C8UF20CAKNLTLJ18> > To:> > <sip:+491234567@200.200.200. [4]200:5060;user=phone>;tag=SDuhhca99-6ossrg8l-> > CC-57> > Call-ID: E4COR3MNVB8AK908> > CSeq: 1 INVITE> > Contact: <sip: 200.200.200.200:5060[6];transport=tcp>> > Allow:> > INVITE,ACK,OPTIONS,BYE,CANCEL,REGISTER,INFO,PRACK,SUBSCRIBE,NOTIFY,UPDATE,> > MESSAGE,REFER Content-Length: 223> > Content-Type: application/sdp> > > > v=0> > o=HuaweiSoftX3000 27670846 27670846 IN IP4 200.200.200.200> > s=Sip Call> > c=IN IP4 200.200.200.200> > t=0 0> > m=audio 22978 RTP/AVP 8 101> > a=rtpmap:8 PCMA/8000> > a=rtpmap:101 telephone-event/8000> > a=ptime:20> > a=fmtp:101 0-15> > > > 2020-02-10 13:04:29.421 --> rcvd SIP FROM TCP 1 720 bytes> > SIP/2.0 180 Ringing> > Via: SIP/2.0/TCP 100.100.100.100:5060;branch=z9hG4bKDGT5EGVPVDE4I146> > From:> > <sip:+4987654321@100.100.100.[3]100:5060;user=phone>;tag=C8UF20CAKNLTLJ18> > To:> > <sip:+491234567@200.200.200. [4]200:5060;user=phone>;tag=SDuhhca99-6ossrg8l-> > CC-57> > Call-ID: E4COR3MNVB8AK908> > CSeq: 1 INVITE> > Allow:> > INVITE,ACK,OPTIONS,BYE,CANCEL,REGISTER,INFO,PRACK,SUBSCRIBE,NOTIFY,UPDATE,> > MESSAGE,REFER Contact: <sip:200.200.200.200:5060[6];transport=tcp>> > Content- Length: 223> > Content-Type: application/sdp> > > > v=0> > o=HuaweiSoftX3000 27670846 27670847 IN IP4 200.200.200.200> > s=Sip Call> > c=IN IP4 200.200.200.200> > t=0 0> > m=audio 22978 RTP/AVP 8 101> > a=rtpmap:8 PCMA/8000> > a=rtpmap:101 telephone-event/8000> > a=ptime:20> > a=fmtp:101 0-15> > > > 2020-02-10 13:04:33.781 --> rcvd SIP FROM TCP 1 782 bytes> > SIP/2.0 200 OK> > Via: SIP/2.0/TCP 100.100.100.100:5060;branch=z9hG4bKDGT5EGVPVDE4I146> > From:> > <sip: +4987654321@100.100.100.[3]100:5060;user=phone>;tag=C8UF20CAKNLTLJ18> > To:> > <sip:+491234567@200.200.200.[4]200:5060;user=phone>;tag=SDuhhca99-6ossrg8l-> > CC-57> > Call-ID: E4COR3MNVB8AK908> > CSeq: 1 INVITE> > Allow:> > INVITE,ACK,OPTIONS,BYE,CANCEL,REGISTER,INFO,PRACK,SUBSCRIBE,NOTIFY,UPDATE,> > MESSAGE,REFER P-Asserted-Identity:> > <sip: 491234567@100.100.100.100[7];user=phone>> > Contact: <sip: 200.200.200.200:5060[6];transport=tcp>> > Content-Length: 223> > Content-Type: application/sdp> > > > v=0> > o=HuaweiSoftX3000 27670846 27670848 IN IP4 200.200.200.200> > s=Sip Call> > c=IN IP4 200.200.200.200> > t=0 0> > m=audio 22978 RTP/AVP 8 101> > a=rtpmap:8 PCMA/8000> > a=rtpmap:101 telephone-event/8000> > a=ptime:20> > a=fmtp:101 0-15> > > > 2020-02-10 13:04:33.782 <-- send SIP TO 200.200.200.200 440 bytes> > ACK sip:_200.200.200.200:5060_;transport=tcp SIP/2.0> > Via: SIP/2.0/TCP 100.100.100.100:5060;branch=z9hG4bKTRLT5A2MP96ST762> > From:> > <sip:+4987654321@100.100.100.[3]100:5060;user=phone>;tag=C8UF20CAKNLTLJ18> > To:> > <sip:+491234567@200.200.200. [4]200:5060;user=phone>;tag=SDuhhca99-6ossrg8l-> > CC-57> > Call-ID: E4COR3MNVB8AK908> > CSeq: 1 ACK> > Contact: <sip:100.100.100.100:5060[5]>> > Max- Forwards: 70> > Allow: INVITE, ACK, CANCEL, OPTIONS, BYE> > Content-Length: 0> > > > > > 2020-02-10 13:04:34.279 --> rcvd SIP FROM TCP 1 782 bytes> > SIP/2.0 200 OK> > > Via: SIP/2.0/TCP 100.100.100.100:5060;branch=z9hG4bKDGT5EGVPVDE4I146> > From:> > <sip:+4987654321@100.100.100.[3]100:5060;user=phone>;tag=C8UF20CAKNLTLJ18> > To:> > <sip:+491234567@200.200.200. [4]200:5060;user=phone>;tag=SDuhhca99-6ossrg8l-> > CC-57> > Call-ID: E4COR3MNVB8AK908> > CSeq: 1 INVITE> > Allow:> > INVITE,ACK,OPTIONS,BYE,CANCEL,REGISTER,INFO,PRACK,SUBSCRIBE,NOTIFY,UPDATE,> > MESSAGE,REFER P-Asserted-Identity:> > <sip: 491234567@100.100.100.100[7];user=phone>> > Contact: <sip: 200.200.200.200:5060[6];transport=tcp>> > Content-Length: 223> > Content-Type: application/sdp> > > > v=0> > o=HuaweiSoftX3000 27670846 27670848 IN IP4 200.200.200.200> > s=Sip Call> > c=IN IP4 200.200.200.200> > t=0 0> > m=audio 22978 RTP/AVP 8 101> > a=rtpmap:8 PCMA/8000> > a=rtpmap:101 telephone-event/8000> > a=ptime:20> > a=fmtp:101 0-15> > > > > > > > _______________________________________________> > Sip-implementors mailing list> > Sip- implement...@lists.cs.columbia.edu[8] _______________________________________________ Sip-implementors mailing list Sip-implementors@lists.cs.columbia.edu https://lists.cs.columbia.edu/mailman/listinfo/sip-implementors
