[Asterisk-Users] cisco 7960 registration fails

miguel saravia msasterisk at gmail.com
Tue Jan 3 05:46:32 MST 2006


What is your firmware version? I have a few problems with the release 7.5

Miguel

Ben Fitzgerald wrote:

>Hi,
>
>Apologies for hitting the list with such a long mail on my first post!
>Having seen the archives this seems like a list that likes debugging
>output. If I have left any information out please let me know.
>
>I have recently begun using asterisk on debian.
>
>ben at deb-tv$ /usr/sbin/asterisk -V
>Asterisk 1.0.7-BRIstuffed-0.2.0-RC7k
>
>ben at deb-tv$ dpkg -l asterisk
>Desired=Unknown/Install/Remove/Purge/Hold
>|
>Status=Not/Installed/Config-files/Unpacked/Failed-config/Half-installed
>|/ Err?=(none)/Hold/Reinst-required/X=both-problems (Status,Err:
>uppercase=bad)
>||/ Name                Version             Description
>+++-===================-===================-==========================
>ii  asterisk            1.0.7.dfsg.1-2      Private Branch Exchange (PBX)
>
>I have an odd problem that may be known as I saw one similar posting.
>
>I have the following config on my cisco 7940:
>
>line1_name : "localuser"
>line1_authname : "localuser"
>line1_password : "localpass"
>line1_shortname : "asterisk"
>line1_displayname : "myphone"
>
>Then in sip.conf:
>
>[localuser]
>type=friend
>username=localuser
>secret=localpass
>auth=md5
>host=dynamic
>dtmfmode=rfc2833
>nat=no
>allow=all
>canreinvite=no
>
>Phone IP: 192.168.1.50.
>
>I startup asterisk and connect to the console, and set:
>
>sip debug ip 192.168.1.50
>set verbose 255
>set debug 255
>
>The console output is as follows:
>
>########## Start asterisk debug output ###############
>Sip read:
>REGISTER sip:192.168.1.4 SIP/2.0
>Via: SIP/2.0/UDP 192.168.1.50:5060;branch=z9hG4bK4b1f5669
>From: sip:localuser at 192.168.1.4
>To: sip:localuser at 192.168.1.4
>Call-ID: 000dbc04-87bf0002-101be50b-1dd1a73e at 192.168.1.50
>Date: Mon, 02 Jan 2006 21:11:05 GMT
>CSeq: 646 REGISTER
>User-Agent: CSCO/7
>Contact: <sip:localuser at 192.168.1.50:5060>
>Content-Length: 0
>Expires: 3600
>
>
>11 headers, 0 lines
>Jan  2 21:11:05 DEBUG[6128]: chan_sip.c:2355 sip_alloc: Allocating new SIP call for 000dbc04-87bf0002-101be50b-1dd1a73e at 192.168.1.50
>Using latest request as basis request
>Sending to 192.168.1.50 : 5060 (non-NAT)
>Transmitting (no NAT):
>SIP/2.0 100 Trying
>Via: SIP/2.0/UDP 192.168.1.50:5060;branch=z9hG4bK4b1f5669
>From: sip:localuser at 192.168.1.4
>To: sip:localuser at 192.168.1.4;tag=as01aba5cf
>Call-ID: 000dbc04-87bf0002-101be50b-1dd1a73e at 192.168.1.50
>CSeq: 646 REGISTER
>User-Agent: Asterisk PBX
>Allow: INVITE, ACK, CANCEL, OPTIONS, BYE, REFER
>Contact: <sip:localuser at 192.168.1.4>
>Content-Length: 0
>
>
> to 192.168.1.50:5060
>Transmitting (no NAT):
>SIP/2.0 401 Unauthorized
>Via: SIP/2.0/UDP 192.168.1.50:5060;branch=z9hG4bK4b1f5669
>From: sip:localuser at 192.168.1.4
>To: sip:localuser at 192.168.1.4;tag=as01aba5cf
>Call-ID: 000dbc04-87bf0002-101be50b-1dd1a73e at 192.168.1.50
>CSeq: 646 REGISTER
>User-Agent: Asterisk PBX
>Allow: INVITE, ACK, CANCEL, OPTIONS, BYE, REFER
>Contact: <sip:localuser at 192.168.1.4>
>WWW-Authenticate: Digest realm="mail.bfitzgerald.co.uk", nonce="773ad211"
>Content-Length: 0
>
>
> to 192.168.1.50:5060
>Scheduling destruction of call '000dbc04-87bf0002-101be50b-1dd1a73e at 192.168.1.50' in 15000 ms
>Urgent handler
>
>
>Sip read:
>REGISTER sip:192.168.1.4 SIP/2.0
>Via: SIP/2.0/UDP 192.168.1.50:5060;branch=z9hG4bK1f807b05
>From: sip:localuser at 192.168.1.4
>To: sip:localuser at 192.168.1.4
>Call-ID: 000dbc04-87bf0002-101be50b-1dd1a73e at 192.168.1.50
>Date: Mon, 02 Jan 2006 21:11:06 GMT
>CSeq: 647 REGISTER
>User-Agent: CSCO/7
>Contact: <sip:localuser at 192.168.1.50:5060>
>Authorization: Digest username="localuser",realm="mail.bfitzgerald.co.uk",uri="sip:192.168.1.4",response="56cf80cc6dc37af4e3f6e036cb45a7bd",nonce="773ad211",algorithm=md5
>Content-Length: 0
>Expires: 3600
>
>
>12 headers, 0 lines
>Using latest request as basis request
>Sending to 192.168.1.50 : 5060 (non-NAT)
>Transmitting (no NAT):
>SIP/2.0 100 Trying
>Via: SIP/2.0/UDP 192.168.1.50:5060;branch=z9hG4bK1f807b05
>From: sip:localuser at 192.168.1.4
>To: sip:localuser at 192.168.1.4;tag=as01aba5cf
>Call-ID: 000dbc04-87bf0002-101be50b-1dd1a73e at 192.168.1.50
>CSeq: 647 REGISTER
>User-Agent: Asterisk PBX
>Allow: INVITE, ACK, CANCEL, OPTIONS, BYE, REFER
>Contact: <sip:localuser at 192.168.1.4>
>Content-Length: 0
>
>
> to 192.168.1.50:5060
>Urgent handler
>
>*
>########## End asterisk debug output ###############
>
>The tethereal capture on my asterisk server is as below:
>
>39.943108  192.168.1.4 -> 192.168.1.50 SIP Status: 100 Trying    (1 bindings)
>39.943335  192.168.1.4 -> 192.168.1.50 SIP Status: 401 Unauthorized    (1 bindings)
>40.184716 192.168.1.50 -> 192.168.1.4  SIP Request: REGISTER sip:192.168.1.4
>40.185768  192.168.1.4 -> 192.168.1.50 SIP Status: 100 Trying    (1 bindings)
>59.999521  192.168.1.1 -> Broadcast    ARP Who has 192.168.1.50?  Tell 192.168.1.1
>
>The main problem is I cannot get my 7940 to register. But in attempting
>to debug this I have seen another problem.
>
>Asterisk stops outputting to the console after the above output. Even
>when subsequent REGISTER requests are seen by tethereal I do not get any
>more asterisk console messages. This makes me wonder if the debian
>distro package is correct. Surely this is a problem with the package?
>
>The phone starts to register but doesn't quite manage it:
>
>SIP Phone> sh reg
>
>LINE REGISTRATION TABLE
>Proxy Registration: ENABLED, state: IDLE
>line  APR  state          timer       expires     proxy:port
>----  ---  -------------  ----------  ---------- -----------------
>1     11x  REGISTERING    3600        204         192.168.1.4:5060
>
>Then falls back to trying to register:
>
>SIP Phone> sh reg
>
>LINE REGISTRATION TABLE
>Proxy Registration: ENABLED, state: IDLE
>line  APR  state          timer       expires     proxy:port
>----  ---  -------------  ----------  ---------- -----------------
>1     .1x  IDLE           60          50          192.168.1.4:5060
>
>
>Any help you can offer is greatly appreciated.
>
>Many thanks,
>
>Ben.
>
>
>  
>




More information about the asterisk-users mailing list