Knowledgebase: Unified Communications
Why the SIP ACk message is not accepted by SN
Posted by Marc Aeberhard, Last modified by Daniel Lizaola on 22 November 2017 01:36 PM

The reason why the ACK for the 200 Ok from the SmartNode in some cases is not accepted, is due to an invalid branch ID in the via header.
Based on the description in RFC 3261, the branch ID for a 2xx response has to be different than in the former messages.
You will find this in section 8.1.1.7, in the RFC 3261.

This incidence shows a SIP message flow, where 200 OK and ACK are sent back and forth several times.

(1601 vote(s))
Helpful
Not helpful

Comments (0)
Post a new comment
 
 
Full Name:
Email:
Comments:
CAPTCHA Verification 
 
Please enter the text you see in the image into the textbox below (we use this to prevent automated submissions).