[SIPForum-discussion] via header

Nitin Kapoor nitinkapoorr at gmail.com
Mon Jan 11 04:04:47 UTC 2010


Anthony,

Not sure that we can use the port "0" in VIA header field or not. As far as
i know Port 0 is reserved, but is a permissible source port value if the
sending process does not expect messages in response.

But yes i also had the same problem just few days ago when my cisco 7960 was
able to make the calls but was not able to receive the calls through
ASTERISK. After analyzing the logs and traces i got to know that my UA was
not sending any port into the VIA header field, which is as below.

<INVITE sip:5126749296 at 58.152.219.220 <sip%3A5126749296 at 58.152.219.220>SIP/2.0
*Via: SIP/2.0/UDP 67.137.224.13:0;branch=z9hG4bK2aca727e*
From: "5126749296" <sip:5126749296 at 67.137.224.13:0>;tag=as399036a5
To: <sip:2147649296 at 67.153.209.220 <sip%3A2147649296 at 67.153.209.220>>
Contact: <sip:2022463521 at 9.137.224.13:0>
Call-ID: 38f0e703759fa812118353011dc04924 at 9.137.224.13
CSeq: 102 INVITE
User-Agent: Asterisk PBX
Date: Thu, 29 Jul 2004 19:10:57 GMT
Allow: INVITE, ACK, CANCEL, OPTIONS, BYE, REFER
Content-Type: application/sdp
Content-Length: 218
sippmh_parse_via: Invalid port number in Via[12:07:52]
sippmh_parse_via: Invalid port number in Via[12:07:52] Sendresponse: Error:
No Via Header present in Message! returned error.

At that time asterisk wasn't initializing the port to 5060.Then I had add
"port = 5060" to the top of my sip.conf file.

Thanks,
Nitin Kapoor




2010/1/8 Anthony Orlando <avorlando at yahoo.com>

> Is it valid for a via header to contain port=zero? such as x.x.x.x:0
>
> _______________________________________________
> This is the SIP Forum discussion mailing list
> TO UNSUBSCRIBE, or edit your delivery options, please visit
> http://sipforum.org/mailman/listinfo/discussion
> Post to the list at discussion at sipforum.org
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://sipforum.org/pipermail/discussion/attachments/20100110/278d446d/attachment-0002.html>


More information about the discussion mailing list