Cisco 8831 not registered on a PBX asterisk

[Adrian Montoya Ruiz]

Hello to all the community,

I have a cisco 8831 (http://www.cisco.com/c/en/us/products/collateral/collaboration-endpoints/unified-ip-phone-8800-series/data_sheet_c78-726887.html ) With firmware version sip8831.10-3-1SR2-2 who need to be connected to a PBX Asterisk but is not registering in the PBX. I configured the XML data file with the extent, the password  and the IP address of the PBX Asterisk and now it seems the phone 8831 can download its configuration file and even have web access but it just does not register.

I attached the XML files and displays on the phone.

PS: A test I did was with a phone 8961, this phone is registered in the same PBX, I configured the data of the phone 8831 and is recorded smoothly, after that I used the XML file of the 8961 on the 8831 but result was the same.

I hope you can help me.

[Leo Laohoo]

<transportLayerProtocol>4</transportLayerProtocol>

This option is invalid.   Try "0" and make the SIP extension support for UDP.  

NOTE:  There are a lot of "junk" with the configuration file.

[Adrian Montoya Ruiz]

Hi Leo and tanks for you time,

I made the change in the transport layer to 0 and the phone 8831 continue with the label "phone no register", and in the SIP extension is working with TCP.

And in another hand I watch this on the debug screen

[00:00:57, 01/01/00] SEPAC44F212F9E3 192.168.15.16/24 192.168.15.254 CP-8831 0.0.0.0 1 0 1 1 0 0 4095 70.36.100.21 0 946686136831946728059341 14 Sent:REGISTER sip:70.36.100.21 SIP/2.0 Cseq:110 REGISTER CallId:ac44f212-f9e3000b-07666ae8-7944e036@192.168.15.16

 But still not working.

PS: I attach the new logs and the xml file , I tryed to remove the junk the best I could

[Leo Laohoo]

I made the change in the transport layer to 0 and the phone 8831 continue with the label "phone no register", and in the SIP extension is working with TCP.

TCP?  That's not recommendation I've made.   Asterisk should extension should be "UDP".

[Adrian Montoya Ruiz]

I made a mistake, the asterisk is working with UDP and int the logs I found this:

1681 ERR 00:04:43.429847 Jan  1 00:04:43 JAVA: Thread-11|JniJSesssionApi:isThisFailureFromNewCause - old unregReason =14 newUnregReason=14 unregReason ignored

The unregister reasons have cause 14 which corresponds to CM_CLOSED_TCP so CallManager closing the TCP socket.

but I don't know what's that mean.

[Amit Sharawat]

From the logs, Definitely a network issue between the phone and the server:

4386 ERR 12:04:58.364481 Jan 1 12:04:58 JAVA: SIP : sip_tcp_channel_send : socket error=111

4387 ERR 12:04:58.364727 Jan 1 12:04:58 JAVA: Thread-12|JniJSesssionApi:isThisFailureFromNewCause - old unregReason =14 newUnregReason=14 unregReason ignored

4388 WRN 12:04:58.364970 Jan 1 12:04:58 JAVA: Thread-12|cip.sipcc.SipEnhancedAlarmInfo:propertyChanged - name=device.status.lastresetcause2 value=465

4389 NOT 12:04:58.778502 Jan 1 12:04:58 JAVA: SIPCC-SIP_TCP_MSG: sip_tcp_purge_entry: Socket fd: 51 closed for connid 0 with address: 1, remote port: 1176790037

4390 ERR 12:04:58.778841 Jan 1 12:04:58 JAVA: SIPCC-SIP_TCP_MSG: sip_tcp_createconnfailed_to_spi: send a SIP_TMR_REG_RETRYmessage so this cucm ip:70.36.100.21 can be put in fallback list

4391 ERR 12:04:58.779104 Jan 1 12:04:58 JAVA: SIPCC-SYS_CALL: sip_tcp_channel_send: Error: sipSocketSend failed: errno = 120

[Adrian Montoya Ruiz]

Hi Amit and thanks for you time,
The first what I done was to change the transport layer and after to upload the xml file on the phone, the mistakes never come to appear again in the logs, but I noticed this new mistakes:

1288 NOT 00:00:57.732653 Jan  1 00:00:57 JAVA: SIPCC-SIP_REG_STATE: 1/51, sip_reg_sm_process_event: SIP_REG_STATE_IDLE <- E_SIP_REG_REG_REQ

1289 NOT 00:00:57.732888 Jan  1 00:00:57 JAVA: ccsip_messaging: sipSPIAddContactHeader: CFGID_DEVICE_NAME = SEPAC44F212F9E3

1290 NOT 00:00:57.733136 Jan  1 00:00:57 JAVA: SIPCC-SIP_MSG_SEND: ccsip_dump_send_msg_info: <70.36.100.21:5060>:REGISTE: <sip:15113@70.36.100.21> :101 REGISTER::ac44f212-f9e30002-235c0b66-1b541eb5@192.168.15.16

PS: I attach the new logs and the xml file.