Unable To Register SIP device

David Trad · ‎08-12-2009

HI Community,

I am having troubles registering a SIP device to our system, we are conducting a LAB test on a SIP/VoIP payphone, i understand that Generic SIP devices are not supported by Cisco, however there might some people in here that have managed to do it before.

Basically this is what i have setup:

voice register global
mode cme
source-address 10.100.4.253 port 5060
timeouts interdigit 5

max-dn 5
max-pool 5
authenticate register
authenticate realm domain.local
timezone 47
date-format D/M/Y
dialplan-pattern 1 33201... extension-length 3
voicemail 550

tftp-path flash:

file text
create profile

voice register dn 1
number 300
allow watch
name PayPhone
label 300

voice register pool 1
id mac 0001.A806.12EC
number 1 dn 1
dtmf-relay sip-notify
username payphone password 1234
codec g711ulaw

However i get these errors when it tries to register:

Aug 13 06:07:41.158: //-1/xxxxxxxxxxxx/SIP/Msg/ccsipDisplayMsg:
Sent:
SIP/2.0 100 Trying
Date: Thu, 13 Aug 2009 06:07:41 GMT
From: "payphone" <sip:payphone@XX.XXX.XXX.XXX>;tag=4fb174cb
Content-Length: 0
To: "payphone" <sip:payphone@XX.XXX.XXX.XXX>
Call-ID: 04cf6cef4df8c160065fad9e737f6356@XXX.XX.XXX.XX
Via: SIP/2.0/UDP XXX.XX.XXX.XX:5060;branch=z9hG4bKa4aeebcd8f
Server: Cisco-SIPGateway/IOS-12.x
CSeq: 1 REGISTER

Aug 13 06:07:41.158: //-1/xxxxxxxxxxxx/SIP/Msg/ccsipDisplayMsg:
Sent:
SIP/2.0 400 Bad Request - 'Invalid IP Address'
Date: Thu, 13 Aug 2009 06:07:41 GMT
From: "payphone" <sip:payphone@XX.XXX.XXX.XXX>;tag=4fb174cb
Content-Length: 0
To: "payphone" <sip:payphone@XX.XXX.XXX.XXX>;tag=1CADDC88-B5
Call-ID: 04cf6cef4df8c160065fad9e737f6356@XXX.XX.XXX.XX
Via: SIP/2.0/UDP XXX.XX.XXX.XX:5060;branch=z9hG4bKa4aeebcd8f
Server: Cisco-SIPGateway/IOS-12.x
CSeq: 1 REGISTER

I am fairly certain this could be setup, however i have hit every brick wall, i am not sure if i am missing something real small here, or if the device that is trying to talk to the Cisco is not capable of doing so (I dount this but it is possible i guess).

Any advice would be greatly appreciated.

Cheers,

David.

Cheers, David Trad. **When you rate a persons post, you are indicating a thank you or that it helped, but at the same time you are also helping to maintain the community spirit - You don't have to rate posts and you wont be looked down upon :) *

Steven DiStefano · ‎08-13-2009

I connected a 3951 SIP phone to a UC500 a few weeks ago and had to do a bunch of manual steps. WHile this phone is 'supported' and has a Cisco Phone load (so may not be the same scenario) perhaps there is something in here that may help?

https://www.myciscocommunity.com/servlet/JiveServlet/previewBody/7244-102-4-11796/Adding_39xx_SIP_to_UC520.pdf

Steve

Saurabh Verma · ‎08-13-2009

Can you capture the output of "debug ccsip all"? I would like to see how's the UC 500 handling the registration requests from the device. Please note that this output will be verbose, so you might want to disable "logging console" and enable "logging buffer 1024000". Perform a "clear logg" from exec mode and then power cycle your SIP device.

-Saurabh

David Trad · ‎08-13-2009

Hi Saurabh,

Can you capture the output of "debug ccsip all"?

Yep Sure can :)

I believe the following is what you are after, and yes i found something suspect there which you might be able to clarify for me (Bold and in Red).

Aug 13 22:23:35.354: //-1/xxxxxxxxxxxx/SIP/Info/ccsip_new_msg_preprocessor: Checking Invite Dialog
Aug 13 22:23:35.354: //-1/xxxxxxxxxxxx/SIP/Info/sipSPIFindRegisterCcb: *****CCB NOT found in UAS Request table. ccb=0x00000000
Aug 13 22:23:35.354: //-1/xxxxxxxxxxxx/SIP/Info/sipSPIAddContextToTable: Added context(0x686CD9F8) with key=[1295201] to table
Aug 13 22:23:35.354: //-1/xxxxxxxxxxxx/SIP/Transport/sipSPIUpdateResponseInfo: Dialog Transaction Address 210.66.154.11,Port 5060, Transport 1, SentBy Port 5060
Aug 13 22:23:35.358: //-1/C687BF19A109/SIP/State/sipSPIChangeState: 0x686CD9F8 : State change from (STATE_NONE, SUBSTATE_NONE)  to (STATE_IDLE, SUBSTATE_NONE)
Aug 13 22:23:35.358: //-1/xxxxxxxxxxxx/SIP/Transport/sipSPIUpdateResponseInfo: Dialog Transaction Address 210.66.154.11,Port 5060, Transport 1, SentBy Port 5060
Aug 13 22:23:35.358: //-1/xxxxxxxxxxxx/SIP/Info/sipSPISetDateHeader: Converting TimeZone aest to SIP default timezone = GMT
Aug 13 22:23:35.358: //-1/xxxxxxxxxxxx/SIP/Transport/sipSPIUpdateResponseInfo: Dialog Transaction Address 210.66.154.11,Port 5060, Transport 1, SentBy Port 5060
Aug 13 22:23:35.358: //-1/C687BF19A109/SIP/Transport/sipSPISendResponse: Sending INFO Response to the transport layer
Aug 13 22:23:35.358: //-1/C687BF19A109/SIP/Transport/sipSPITransportSendMessage: msg=0x67AEB99C, addr=210.66.154.11, port=5060, sentBy_port=5060, is_req=0, transport=1, switch=0, callBack=0x00000000
Aug 13 22:23:35.358: //-1/C687BF19A109/SIP/Transport/sipSPITransportSendMessage: Proceedable for sending msg immediately
Aug 13 22:23:35.358: //-1/C687BF19A109/SIP/Transport/sipTransportLogicSendMsg: switch transport is 0
Aug 13 22:23:35.358: //-1/xxxxxxxxxxxx/SIP/Transport/sipTransportPostSendMessage: Posting send for msg=0x67AEB99C, addr=210.66.154.11, port=5060, connId=0 for UDP
Aug 13 22:23:35.362: //-1/xxxxxxxxxxxx/SIP/Error/sipSPI_validate_own_ip_addr: ReqLine IP addr does not match with host IP addr
Aug 13 22:23:35.362: //-1/C687BF19A109/SIP/Transport/sipSPISendResponse: Sending INFO Response to the transport layer
Aug 13 22:23:35.362: //-1/C687BF19A109/SIP/Transport/sipSPITransportSendMessage: msg=0x67982874, addr=210.66.154.11, port=5060, sentBy_port=5060, is_req=0, transport=1, switch=0, callBack=0x6130B5D4
Aug 13 22:23:35.362: //-1/C687BF19A109/SIP/Transport/sipSPITransportSendMessage: Proceedable for sending msg immediately
Aug 13 22:23:35.362: //-1/C687BF19A109/SIP/Transport/sipTransportLogicSendMsg: switch transport is 0
Aug 13 22:23:35.362: //-1/xxxxxxxxxxxx/SIP/Transport/sipTransportPostSendMessage: Posting send for msg=0x67982874, addr=210.66.154.11, port=5060, connId=0 for UDP
Aug 13 22:23:35.362: //-1/C687BF19A109/SIP/State/sipSPIChangeState: 0x686CD9F8 : State change from (STATE_IDLE, SUBSTATE_NONE)  to (STATE_IDLE, SUBSTATE_NONE)
Aug 13 22:23:35.362: //-1/xxxxxxxxxxxx/SIP/Msg/ccsipDisplayMsg:

I am sure it is something simple, and if anything something to do with the way i have configured the system for outside access, unless i need to do something on the 877, but our CCIE guy allready worked through all the NAT's and Firewall rules, i would think he would be the one to get things right.

Cheers,

David.

Cheers, David Trad. **When you rate a persons post, you are indicating a thank you or that it helped, but at the same time you are also helping to maintain the community spirit - You don't have to rate posts and you wont be looked down upon :) *

Steven Smith · ‎08-13-2009

This sounds like it is coming from outside the firewall. It also looks like the IP address are not matching either at the IP layer or inside the packet. Could you PM me the debug ccsip messages without the IP's marked out?

David Trad · ‎08-13-2009

Hi Steven,

It has been done.

Cheers,

David.

Cheers, David Trad. **When you rate a persons post, you are indicating a thank you or that it helped, but at the same time you are also helping to maintain the community spirit - You don't have to rate posts and you wont be looked down upon :) *

Saurabh Verma · ‎08-13-2009

Hi David,

Are you sure that the debugs that you attached were for the device registration? For some reason I thought this was for an incoming invite from a SIP trunk. Can you capture the debugs when the SIP device tries to REGISTER with the UC 520? You will notice a SIP REGISTER message in the debug.

-Saurabh

Steven Smith · ‎08-13-2009

You might want to look here for a reference.

https://supportforums.cisco.com/docs/DOC-9465

What do you have under voice service voip?