[SIPForum-discussion] Problem: Asterisk is ignoring INVITE Messages

chintu sschintalwar at gmail.com
Tue Apr 29 15:45:44 UTC 2008


Hi alex

In sip.conf you need to add the host ip from which INVITE received by
asterisk



On 4/25/08, alexander.deuschlinger at chello.at <
alexander.deuschlinger at chello.at> wrote:
>
> Hi!
>
> We are experementing with SIP and Asterisk in school.
> We had no big problems so far, but now we have a problem with sending an
> INVITE-Message to another host, because Asterisk ignores them.
> And we cannot figure out where this failure comes from.
>
> So, please help us to get this thing done.
>
> Here is the SIP debug:
>
> The Registration-Part is function successfully for the users 2000 and
> 2001.
>
> INVITE-Part:
>
> <--- SIP read from 192.168.100.50:5070 --->
> INVITE sip:2000 at 192.168.100.32 <sip%3A2000 at 192.168.100.32> SIP/2.0
> Via: SIP/2.0/UDP 192.168.100.50:5070;branch=z9hG4bK-eE6hF;rport=
> From: <sip:2001 at 192.168.100.32 <sip%3A2001 at 192.168.100.32>>
> To: <sip:2000 at 192.168.100.32 <sip%3A2000 at 192.168.100.32>>
> Call-ID: eE6h at 192.168.100.32
> CSeq: 3 INVITE
> Contact: <sip:2001 at 192.168.100.50 <sip%3A2001 at 192.168.100.50>>
> User-Agent: TwinSIP Communicator
> Content-Type: application/sdp
> Content-Length: 99
>
> v=0
> o=andy 2634 2634 IN IP4 192.168.100.50
> s=test von alex
> t=0 0
> m=audio 9050 udp PCM/32000/8/1
>
> <------------->
> --- (10 headers 5 lines) ---
> Sending to 192.168.100.50 : 5070 (no NAT)
> Using INVITE request as basis request - eE6h at 192.168.100.32
>
> <--- Reliably Transmitting (no NAT) to 192.168.100.50:5070 --->
> SIP/2.0 407 Proxy Authentication Required
> Via: SIP/2.0/UDP 192.168.100.50:5070;branch=z9hG4bK-eE6hF;rport=;received=
> 192.168.100.50
> From: <sip:2001 at 192.168.100.32 <sip%3A2001 at 192.168.100.32>>
> To: <sip:2000 at 192.168.100.32 <sip%3A2000 at 192.168.100.32>>;tag=as3887b859
> Call-ID: eE6h at 192.168.100.32
> CSeq: 3 INVITE
> User-Agent: Asterisk PBX
> Allow: INVITE, ACK, CANCEL, OPTIONS, BYE, REFER, SUBSCRIBE, NOTIFY
> Supported: replaces
> Proxy-Authenticate: Digest algorithm=MD5, realm="asterisk",
> nonce="4e5f93f7"
> Content-Length: 0
>
>
> <------------>
> Scheduling destruction of SIP dialog 'eE6h at 192.168.100.32' in 32000 ms
> (Method: INVITE)
> Found user '2001'
>
> <--- SIP read from 192.168.100.50:5070 --->
> INVITE sip:2000 at 192.168.100.32 <sip%3A2000 at 192.168.100.32> SIP/2.0
> Via: SIP/2.0/UDP 192.168.100.50:5070;branch=z9hG4bK-eE6hF;rport=
> From: <sip:2001 at 192.168.100.32 <sip%3A2001 at 192.168.100.32>>
> To: <sip:2000 at 192.168.100.32 <sip%3A2000 at 192.168.100.32>>;tag=as3887b859
> Call-ID: eE6h at 192.168.100.32
> CSeq: 3 INVITE
> Contact: <sip:2001 at 192.168.100.50 <sip%3A2001 at 192.168.100.50>>
> User-Agent: TwinSIP Communicator
> Content-Type: application/sdp
> Content-Length: 99
> Proxy-Authorization: Digest username="2001", realm="asterisk",
> nonce="4e5f93f7", uri="192.168.100.32",
> response="39abd8d49d07c1cbb489b0fc467d2856", algorithm=MD5
>
>
> <------------->
> --- (11 headers 0 lines) ---
> Ignoring this INVITE request
> Retransmitting #1 (no NAT) to 192.168.100.50:5070:
> SIP/2.0 407 Proxy Authentication Required
> Via: SIP/2.0/UDP 192.168.100.50:5070;branch=z9hG4bK-eE6hF;rport=;received=
> 192.168.100.50
> From: <sip:2001 at 192.168.100.32 <sip%3A2001 at 192.168.100.32>>
> To: <sip:2000 at 192.168.100.32 <sip%3A2000 at 192.168.100.32>>;tag=as3887b859
> Call-ID: eE6h at 192.168.100.32
> CSeq: 3 INVITE
> User-Agent: Asterisk PBX
> Allow: INVITE, ACK, CANCEL, OPTIONS, BYE, REFER, SUBSCRIBE, NOTIFY
> Supported: replaces
> Proxy-Authenticate: Digest algorithm=MD5, realm="asterisk",
> nonce="4e5f93f7"
> Content-Length: 0
>
>
> ---
>
> <--- SIP read from 192.168.100.50:5070 --->
> INVITE sip:2000 at 192.168.100.32 <sip%3A2000 at 192.168.100.32> SIP/2.0
> Via: SIP/2.0/UDP 192.168.100.50:5070;branch=z9hG4bK-eE6hF;rport=
> From: <sip:2001 at 192.168.100.32 <sip%3A2001 at 192.168.100.32>>
> To: <sip:2000 at 192.168.100.32 <sip%3A2000 at 192.168.100.32>>;tag=as3887b859
> Call-ID: eE6h at 192.168.100.32
> CSeq: 3 INVITE
> Contact: <sip:2001 at 192.168.100.50 <sip%3A2001 at 192.168.100.50>>
> User-Agent: TwinSIP Communicator
> Content-Type: application/sdp
> Content-Length: 99
> Proxy-Authorization: Digest username="2001", realm="asterisk",
> nonce="4e5f93f7", uri="192.168.100.32",
> response="39abd8d49d07c1cbb489b0fc467d2856", algorithm=MD5
>
>
> <------------->
> --- (11 headers 0 lines) ---
> Ignoring this INVITE request
> Retransmitting #2 (no NAT) to 192.168.100.50:5070:
> SIP/2.0 407 Proxy Authentication Required
> Via: SIP/2.0/UDP 192.168.100.50:5070;branch=z9hG4bK-eE6hF;rport=;received=
> 192.168.100.50
> From: <sip:2001 at 192.168.100.32 <sip%3A2001 at 192.168.100.32>>
> To: <sip:2000 at 192.168.100.32 <sip%3A2000 at 192.168.100.32>>;tag=as3887b859
> Call-ID: eE6h at 192.168.100.32
> CSeq: 3 INVITE
> User-Agent: Asterisk PBX
> Allow: INVITE, ACK, CANCEL, OPTIONS, BYE, REFER, SUBSCRIBE, NOTIFY
> Supported: replaces
> Proxy-Authenticate: Digest algorithm=MD5, realm="asterisk",
> nonce="4e5f93f7"
> Content-Length: 0
>
>
> ---
>
> <--- SIP read from 192.168.100.50:5070 --->
> INVITE sip:2000 at 192.168.100.32 <sip%3A2000 at 192.168.100.32> SIP/2.0
> Via: SIP/2.0/UDP 192.168.100.50:5070;branch=z9hG4bK-eE6hF;rport=
> From: <sip:2001 at 192.168.100.32 <sip%3A2001 at 192.168.100.32>>
> To: <sip:2000 at 192.168.100.32 <sip%3A2000 at 192.168.100.32>>;tag=as3887b859
> Call-ID: eE6h at 192.168.100.32
> CSeq: 3 INVITE
> Contact: <sip:2001 at 192.168.100.50 <sip%3A2001 at 192.168.100.50>>
> User-Agent: TwinSIP Communicator
> Content-Type: application/sdp
> Content-Length: 99
> Proxy-Authorization: Digest username="2001", realm="asterisk",
> nonce="4e5f93f7", uri="192.168.100.32",
> response="39abd8d49d07c1cbb489b0fc467d2856", algorithm=MD5
>
>
> <------------->
> --- (11 headers 0 lines) ---
> Ignoring this INVITE request
> Retransmitting #3 (no NAT) to 192.168.100.50:5070:
> SIP/2.0 407 Proxy Authentication Required
> Via: SIP/2.0/UDP 192.168.100.50:5070;branch=z9hG4bK-eE6hF;rport=;received=
> 192.168.100.50
> From: <sip:2001 at 192.168.100.32 <sip%3A2001 at 192.168.100.32>>
> To: <sip:2000 at 192.168.100.32 <sip%3A2000 at 192.168.100.32>>;tag=as3887b859
> Call-ID: eE6h at 192.168.100.32
> CSeq: 3 INVITE
> User-Agent: Asterisk PBX
> Allow: INVITE, ACK, CANCEL, OPTIONS, BYE, REFER, SUBSCRIBE, NOTIFY
> Supported: replaces
> Proxy-Authenticate: Digest algorithm=MD5, realm="asterisk",
> nonce="4e5f93f7"
> Content-Length: 0
>
>
> ---
>
> <--- SIP read from 192.168.100.50:5070 --->
> INVITE sip:2000 at 192.168.100.32 <sip%3A2000 at 192.168.100.32> SIP/2.0
> Via: SIP/2.0/UDP 192.168.100.50:5070;branch=z9hG4bK-eE6hF;rport=
> From: <sip:2001 at 192.168.100.32 <sip%3A2001 at 192.168.100.32>>
> To: <sip:2000 at 192.168.100.32 <sip%3A2000 at 192.168.100.32>>;tag=as3887b859
> Call-ID: eE6h at 192.168.100.32
> CSeq: 3 INVITE
> Contact: <sip:2001 at 192.168.100.50 <sip%3A2001 at 192.168.100.50>>
> User-Agent: TwinSIP Communicator
> Content-Type: application/sdp
> Content-Length: 99
> Proxy-Authorization: Digest username="2001", realm="asterisk",
> nonce="4e5f93f7", uri="192.168.100.32",
> response="39abd8d49d07c1cbb489b0fc467d2856", algorithm=MD5
>
>
> <------------->
> --- (11 headers 0 lines) ---
> Ignoring this INVITE request
> Retransmitting #4 (no NAT) to 192.168.100.50:5070:
> SIP/2.0 407 Proxy Authentication Required
> Via: SIP/2.0/UDP 192.168.100.50:5070;branch=z9hG4bK-eE6hF;rport=;received=
> 192.168.100.50
> From: <sip:2001 at 192.168.100.32 <sip%3A2001 at 192.168.100.32>>
> To: <sip:2000 at 192.168.100.32 <sip%3A2000 at 192.168.100.32>>;tag=as3887b859
> Call-ID: eE6h at 192.168.100.32
> CSeq: 3 INVITE
> User-Agent: Asterisk PBX
> Allow: INVITE, ACK, CANCEL, OPTIONS, BYE, REFER, SUBSCRIBE, NOTIFY
> Supported: replaces
> Proxy-Authenticate: Digest algorithm=MD5, realm="asterisk",
> nonce="4e5f93f7"
> Content-Length: 0
>
>
> ---
>
> <--- SIP read from 192.168.100.50:5070 --->
> INVITE sip:2000 at 192.168.100.32 <sip%3A2000 at 192.168.100.32> SIP/2.0
> Via: SIP/2.0/UDP 192.168.100.50:5070;branch=z9hG4bK-eE6hF;rport=
> From: <sip:2001 at 192.168.100.32 <sip%3A2001 at 192.168.100.32>>
> To: <sip:2000 at 192.168.100.32 <sip%3A2000 at 192.168.100.32>>;tag=as3887b859
> Call-ID: eE6h at 192.168.100.32
> CSeq: 3 INVITE
> Contact: <sip:2001 at 192.168.100.50 <sip%3A2001 at 192.168.100.50>>
> User-Agent: TwinSIP Communicator
> Content-Type: application/sdp
> Content-Length: 99
> Proxy-Authorization: Digest username="2001", realm="asterisk",
> nonce="4e5f93f7", uri="192.168.100.32",
> response="39abd8d49d07c1cbb489b0fc467d2856", algorithm=MD5
>
>
> <------------->
> --- (11 headers 0 lines) ---
> Ignoring this INVITE request
> Retransmitting #5 (no NAT) to 192.168.100.50:5070:
> SIP/2.0 407 Proxy Authentication Required
> Via: SIP/2.0/UDP 192.168.100.50:5070;branch=z9hG4bK-eE6hF;rport=;received=
> 192.168.100.50
> From: <sip:2001 at 192.168.100.32 <sip%3A2001 at 192.168.100.32>>
> To: <sip:2000 at 192.168.100.32 <sip%3A2000 at 192.168.100.32>>;tag=as3887b859
> Call-ID: eE6h at 192.168.100.32
> CSeq: 3 INVITE
> User-Agent: Asterisk PBX
> Allow: INVITE, ACK, CANCEL, OPTIONS, BYE, REFER, SUBSCRIBE, NOTIFY
> Supported: replaces
> Proxy-Authenticate: Digest algorithm=MD5, realm="asterisk",
> nonce="4e5f93f7"
> Content-Length: 0
>
>
> ---
>
> <--- SIP read from 192.168.100.50:5070 --->
> INVITE sip:2000 at 192.168.100.32 <sip%3A2000 at 192.168.100.32> SIP/2.0
> Via: SIP/2.0/UDP 192.168.100.50:5070;branch=z9hG4bK-eE6hF;rport=
> From: <sip:2001 at 192.168.100.32 <sip%3A2001 at 192.168.100.32>>
> To: <sip:2000 at 192.168.100.32 <sip%3A2000 at 192.168.100.32>>;tag=as3887b859
> Call-ID: eE6h at 192.168.100.32
> CSeq: 3 INVITE
> Contact: <sip:2001 at 192.168.100.50 <sip%3A2001 at 192.168.100.50>>
> User-Agent: TwinSIP Communicator
> Content-Type: application/sdp
> Content-Length: 99
> Proxy-Authorization: Digest username="2001", realm="asterisk",
> nonce="4e5f93f7", uri="192.168.100.32",
> response="39abd8d49d07c1cbb489b0fc467d2856", algorithm=MD5
>
>
> <------------->
> --- (11 headers 0 lines) ---
> Ignoring this INVITE request
> Retransmitting #6 (no NAT) to 192.168.100.50:5070:
> SIP/2.0 407 Proxy Authentication Required
> Via: SIP/2.0/UDP 192.168.100.50:5070;branch=z9hG4bK-eE6hF;rport=;received=
> 192.168.100.50
> From: <sip:2001 at 192.168.100.32 <sip%3A2001 at 192.168.100.32>>
> To: <sip:2000 at 192.168.100.32 <sip%3A2000 at 192.168.100.32>>;tag=as3887b859
> Call-ID: eE6h at 192.168.100.32
> CSeq: 3 INVITE
> User-Agent: Asterisk PBX
> Allow: INVITE, ACK, CANCEL, OPTIONS, BYE, REFER, SUBSCRIBE, NOTIFY
> Supported: replaces
> Proxy-Authenticate: Digest algorithm=MD5, realm="asterisk",
> nonce="4e5f93f7"
> Content-Length: 0
>
>
> ---
>
> <--- SIP read from 192.168.100.50:5070 --->
> INVITE sip:2000 at 192.168.100.32 <sip%3A2000 at 192.168.100.32> SIP/2.0
> Via: SIP/2.0/UDP 192.168.100.50:5070;branch=z9hG4bK-eE6hF;rport=
> From: <sip:2001 at 192.168.100.32 <sip%3A2001 at 192.168.100.32>>
> To: <sip:2000 at 192.168.100.32 <sip%3A2000 at 192.168.100.32>>;tag=as3887b859
> Call-ID: eE6h at 192.168.100.32
> CSeq: 3 INVITE
> Contact: <sip:2001 at 192.168.100.50 <sip%3A2001 at 192.168.100.50>>
> User-Agent: TwinSIP Communicator
> Content-Type: application/sdp
> Content-Length: 99
> Proxy-Authorization: Digest username="2001", realm="asterisk",
> nonce="4e5f93f7", uri="192.168.100.32",
> response="39abd8d49d07c1cbb489b0fc467d2856", algorithm=MD5
>
>
> <------------->
> --- (11 headers 0 lines) ---
> Ignoring this INVITE request
> [Apr 24 17:31:57] WARNING[5391]: chan_sip.c:1939 retrans_pkt: Maximum
> retries exceeded on transmission eE6h at 192.168.100.32 for seqno 3
> (Non-critical Response)
> Really destroying SIP dialog 'eE6h at 192.168.100.32' Method: INVITE
>
> End of INVITE-Part.
>
> Is anything wrong with the SIP-Messages? Or what can we do to solve this
> problem?
>
> Thanks in advance,
> Alex
> _______________________________________________
> 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/20080429/8b27ed6c/attachment-0002.html>


More information about the discussion mailing list