cancel
Showing results for 
Search instead for 
Did you mean: 
cancel
6878
Views
55
Helpful
6
Replies

Cisco IP Phone 7941G not register

INEM
Level 1
Level 1

Hi guys,

I need some help, I'm not able to register my phone 7941G in asterisk version 1.8.13.1 , my SEPXXXX.cnf.xml file contains the following code :

 

http://pastebin.com/GJ4V2nQb

 

I boot the phone with the sequence 123456789 * 0 # and it loads all the files from the TFTP , then I access to the phone URL and he introduced the following error:

 

WRN 21:20:37.396743 JVM: Thread-3|cip.l10n.NetworkLocaleProperty:? - Unable to process LocaleProperty 'device.settings.config.localization.networklocale'
NOT 21:20:38.863523 JVM: Thread-3|cip.sipcc.c:  - initializeLinePlane(): Mgmt Interface is in Service now..
NOT 21:20:39.153626 tftpClient: tftp request rcv'd from /usr/tmp/tftp, srcFile = dialplan.xml, dstFile = /usr/cache/DP817620086 
NOT 21:20:39.156587 tftpClient: auth server - tftpList[0] = 172.16.0.11 
NOT 21:20:39.157382 tftpClient: look up server - 0 
WRN 21:20:39.160269 SECD: WARN:lookupCTL: ** no CTL, assume TFTP 172.16.0.11 NONSECURE
NOT 21:20:39.164441 tftpClient: secVal = 0xa 
NOT 21:20:39.165288 tftpClient: 172.16.0.11 is a NONsecure server 
NOT 21:20:39.166034 tftpClient: temp retval = SRVR_NONSECURE, keep looking 
NOT 21:20:39.166747 tftpClient: retval = 10 
NOT 21:20:39.167478 tftpClient: Secure file requested 
NOT 21:20:39.168184 tftpClient: Non secure file approved  -- dialplan.xml  
NOT 21:20:39.183457 TFTP: [17]:Requesting dialplan.xml from 172.16.0.11 
NOT 21:20:39.194703 TFTP: [17]:Finished --> rcvd 90 bytes 
ERR 21:21:11.100842 JVM: %REG auth failed: ack timer
ERR 21:21:43.125804 JVM: %REG auth failed: ack timer
ERR 21:22:15.135824 JVM: %REG auth failed: ack timer
ERR 21:22:47.150861 JVM: %REG auth failed: ack timer
ERR 21:23:19.160881 JVM: %REG auth failed: ack timer
ERR 21:23:51.165921 JVM: %REG auth failed: ack timer
ERR 21:24:23.170825 JVM: %REG auth failed: ack timer
ERR 21:24:55.170916 JVM: %REG auth failed: ack timer
ERR 21:25:27.181088 JVM: %REG auth failed: ack timer
ERR 21:25:59.190840 JVM: %REG auth failed: ack timer
ERR 21:26:31.200874 JVM: %REG auth failed: ack timer
ERR 21:27:03.210801 JVM: %REG auth failed: ack timer

 

The phones are only to be used internally with private IPs , I do not need NAT to make calls out of my internal network

I can register a zoiper phone and x-lite and talk in the asterisk, but this hardphone not, why is wrong?


Thanks in advance

1 Accepted Solution

Accepted Solutions

Hi Carlos,

I'm not Asterisk guy but from the wireshark traces, I can say that at SIP level phone is getting registered successfully. However if you have noticed, Asterisk is sending OPTION message to phone and phone is not responding to that message. That could be the reason why status is showing UNREACHABLE. Other phones (9001) which are registered might responding with 200 OK against OPTION message. I think you should see in Asterisk if there is any option to disable OPTION ping support.

Thanks

Vivek

View solution in original post

6 Replies 6

Wilson Samuel
Level 7
Level 7

Looks like the Phone is trying to authenticate against the server and is failing.

I havent worked on Asterisk at all so not sure how it behaves or configured, however on CME (Callmanager Express) I have to use the DN / Extension number as the username and password could be anything.

At the same time, try disabling the authentication on the server if at all it is possible.

HTH

Hi Wilson,

 

I disabled the authentication in the sip.conf file with command: 

allowguest=yes

 

And in the SEP.XXX.cnf.xml i remove the password too.

 

And than the Cisco phone apper in the Asterisk with the following error:

 

The SIP phone is the extention 9002 that said in your status UNREACHABLE, who fix this?

NOTE: mydoc.pdf is a wireshark capture, please see!!!

 

I´m close to solve my problem...

Thanks in advance

Hi Carlos,

I'm not Asterisk guy but from the wireshark traces, I can say that at SIP level phone is getting registered successfully. However if you have noticed, Asterisk is sending OPTION message to phone and phone is not responding to that message. That could be the reason why status is showing UNREACHABLE. Other phones (9001) which are registered might responding with 200 OK against OPTION message. I think you should see in Asterisk if there is any option to disable OPTION ping support.

Thanks

Vivek

I tried to figure out in Asterisk and qualify=no will disable the OPTION support in Asterisk.

Reference:

http://www.voip-info.org/wiki/view/Asterisk+sip+qualify

Thanks

Vivek

Hi Vivek,

 

The problem is options, i change the sip.conf in asterisk, and the phone work, basically I removed all the options and add only the essential in [general] and the phone work.

 

I think this is a good choice, because now i can add more options and see the registation happening.

  • [general]
  • context=default
  • port=5060 
  • bindaddr=0.0.0.0 
  • allowguest=yes

 

Hi Carlos,

 

Did you configure the XML of IP Phone to reaches the IP of Astersk?

 

http://www.voip-info.org/wiki/view/Asterisk+phone+cisco+79x1+xml+configuration+files+for+SIP#sthash.Naw2l7GE.dpuf

 

Best regards,

Daniel Sobrinho

Daniel Sobrinho