Yes, the via is malformed Via: SIP/2.0/UDP 10.32.140.122:5060;rport;branch=z9hG4bK-38-dc39-6b4deb27;rport=5060
(rport)+ (rport=5060) equal trash. -----Original Message----- From: ext Brett Tate [mailto:[email protected]] Sent: Wednesday, April 20, 2011 11:01 AM To: Pavesi, Valdemar (NSN - US/Irving); [email protected] Subject: RE: [Sip-implementors] SIP request Cancel Issue > The rfc is not talking about match via from 200ok > and the invite. Look at the cseq; the 200 is for CANCEL. However the 200 has a malformed Via entry. > In reality the only problem that we have here is > the out of order from the server side. The ordering is irrelevant; the UAC must accommodate either order. The issue is the malformed Via entry. The via issue appears to be causing the UAC to ignore the 200 response and ignore the 487 response. > Before the 200k the server must send the 487 to > terminated the dialog and wait for ACK and then > send the 200ok-cseq-cancel. I disagree with that statement. That statement even conflicts with the typical CANCEL flow shown within RFC 3665 section 3.8. RFC 5407 provides some atypical CANCEL flows. > -----Original Message----- > From: ext Brett Tate [mailto:[email protected]] > Sent: Wednesday, April 20, 2011 10:12 AM > To: Pavesi, Valdemar (NSN - US/Irving); > [email protected] > Subject: RE: [Sip-implementors] SIP request Cancel Issue > > > This via with rport=5060 is the one generated by server > > on b-side . and we are talking about cancel the dialog > > on a-side. > > You might want to look at the call flow again. > > Voip1:10.32.140.122 > > INVITE sip:[email protected];transport=udp SIP/2.0 > From: "AHTV Ric > 1"<sip:[email protected]>;tag=13e7858-7a8c200a-13c4-5506-38-3625c56-38 > To: <sip:[email protected];transport=udp> > Call-ID: 14800c0-7a8c200a-13c4-5506-38-1b91bc30-38 > CSeq: 1 INVITE > Via: SIP/2.0/UDP > 10.32.140.122:5060;rport;branch=z9hG4bK-38-dc39-6b4deb27 > > <snip> > > Voip-1 Sends Cancel > > CANCEL sip:[email protected];transport=udp SIP/2.0 > From: "AHTV Ric > 1"<sip:[email protected]>;tag=13e7858-7a8c200a-13c4-5506-38-3625c56-38 > To: <sip:[email protected];transport=udp> > Call-ID: 14800c0-7a8c200a-13c4-5506-38-1b91bc30-38 > CSeq: 1 CANCEL > Via: SIP/2.0/UDP > 10.32.140.122:5060;rport;branch=z9hG4bK-38-dc39-6b4deb27 > Max-Forwards: 70 > Supported: 100rel,timer,replaces > Content-Length: 0 > > > Server responds with 200 Ok > > SIP/2.0 200 OK > Via: SIP/2.0/UDP > 10.32.140.122:5060;rport;branch=z9hG4bK-38-dc39-6b4deb27;rport=5060 > From: "AHTV Ric > 1"<sip:[email protected]>;tag=13e7858-7a8c200a-13c4-5506-38-3625c56-38 > To: <sip:[email protected];transport=udp>;tag=2406394696 > Call-ID: 14800c0-7a8c200a-13c4-5506-38-1b91bc30-38 > CSeq: 1 CANCEL > Contact: <sip:10.32.128.20> > Allow: > INVITE,ACK,CANCEL,BYE,REFER,OPTIONS,NOTIFY,SUBSCRIBE,PRACK,MESSAGE,INFO > Allow-Events: dialog > Supported: gruu > Content-Length: 0 > > > Server sends 487 > > > SIP/2.0 487 Request Terminated > Via: SIP/2.0/UDP > 10.32.140.122:5060;rport;branch=z9hG4bK-38-dc39-6b4deb27;rport=5060 > From: "AHTV Ric > 1"<sip:[email protected]>;tag=13e7858-7a8c200a-13c4-5506-38-3625c56-38 > To: <sip:[email protected];transport=udp>;tag=2406394696 > Call-ID: 14800c0-7a8c200a-13c4-5506-38-1b91bc30-38 > CSeq: 1 INVITE > Contact: <sip:10.32.128.20> > Allow: > INVITE,ACK,CANCEL,BYE,REFER,OPTIONS,NOTIFY,SUBSCRIBE,PRACK,MESSAGE,INFO > Allow-Events: dialog > Supported: gruu > Content-Length: 0 > > > Voip1 is not responding to 487 > _______________________________________________ Sip-implementors mailing list [email protected] https://lists.cs.columbia.edu/cucslists/listinfo/sip-implementors
