[SR-Users] VIA header question.

Chad ccolumbu at hotmail.com
Tue Aug 4 13:14:16 CEST 2015


Hi list,
I need a little help, I am a business owner trying to get Kamailio up and running as a SIP load balancer.
I hired a Kamailio consultant to help me do so, but Kamailio is not working and I am getting conflicting information.

My Kamailio consultant and my VOIP provider are telling me 2 different things and I don't know which one is right.

Kamailio sends SIP traffic to the VOIP provider with 2 VIA headers like this (in this order):
Via: SIP/2.0/UDP 10.10.10.254;branch=z9hG4bK7291.6a0bbd2e8fd639a47d7d2de606779e47.0.
Via: SIP/2.0/UDP 209.170.201.25:5060;received=10.10.10.102;branch=z9hG4bK742dc03d;rport=5060.

The VOIP provider says that is incorrect because they are supposed to reply back to the topmost VIA header so they reply 
to the 10.10.10.254 IP (which is not public) and the call ends.
The VOIP provider says Kamailio should send the VIA headers like this instead:
Via: SIP/2.0/UDP 209.170.201.25:5060;received=10.10.10.102;branch=z9hG4bK742dc03d;rport=5060.
Via: SIP/2.0/UDP 10.10.10.254;branch=z9hG4bK7291.6a0bbd2e8fd639a47d7d2de606779e47.0.

My Kamailio consultant says the way we are sending it is right and that the VOIP provider is processing the call 
incorrectly.

I read that the SIP proxy is supposed to remove the internal header from the 1st example above based on this RFC:
https://tools.ietf.org/html/rfc3261#section-16.7
Item: 3. Via
"The proxy removes the topmost Via header field value from the response."

If that applies to this situation (which I don't know if it does) then Kamailio should be removing the 10.10.10.254 VIA 
line and only sending 1 VIA header like this:
Via: SIP/2.0/UDP 209.170.201.25:5060;received=10.10.10.102;branch=z9hG4bK742dc03d;rport=5060.

Which would sort of make the VOIP provider right in that the topmost VIA line would then be the external IP, but how 
they said to fix it (reversing the VIA lines) is wrong.

Does anyone know what the right answer is here?
Please let me know.

THANKS for your help.

-- 

^C




More information about the sr-users mailing list