cancel
Showing results for 
Search instead for 
Did you mean: 
cancel
2059
Views
8
Helpful
5
Replies

CME & 3rd party SIP (Cyberdata Intercom)

danielblock1
Level 1
Level 1

I'm trying to get a Cyberdata Intercom to work with a UC520. I followed the instructions at: http://supportwiki.cisco.com/wiki/images/5/58/Cyberdata_uc500_Doorphone_external_last-v3.pdf. I can get it to make calls and everything seemingly works as expected, however it is not registering. This is what I'm getting when it trys to register:

Jan 15 21:21:28.062: //-1/xxxxxxxxxxxx/SIP/Msg/ccsipDisplayMsg:

Received:

REGISTER sip:10.1.1.1:5060 SIP/2.0

Via: SIP/2.0/UDP 192.168.10.16:5060;rport;branch=z9hG4bK1986204771

From: <sip:407@10.1.1.1>;tag=714839302

To: <sip:407@10.1.1.1>

Call-ID: 1592243375@192.168.10.16

CSeq: 2 REGISTER

Contact: <sip:407@192.168.10.16:5060>

Max-Forwards: 5

User-Agent: CyberData Intercom

Expires: 3600

Content-Length: 0

Jan 15 21:21:28.062: //-1/xxxxxxxxxxxx/SIP/Error/ccsip_reg_search_call_id_table: No entry found in sipCallID Table

Jan 15 21:21:28.062: //-1/xxxxxxxxxxxx/SIP/Error/sipSPI_validate_own_ip_addr: Re qLine IP addr does not match with host IP addr

Jan 15 21:21:28.062: //196/4E2404168187/SIP/Error/ccsip_spi_register_incoming_re gistration: Registration Authorization failed with authorization header=

Jan 15 21:21:28.066: //-1/xxxxxxxxxxxx/SIP/Msg/ccsipDisplayMsg:

Sent:

SIP/2.0 100 Trying

Via: SIP/2.0/UDP 192.168.10.16:5060;rport;branch=z9hG4bK1986204771

From: <sip:407@10.1.1.1>;tag=714839302

To: <sip:407@10.1.1.1>

Date: Thu, 15 Jan 2009 21:21:28 GMT

Call-ID: 1592243375@192.168.10.16

Server: Cisco-SIPGateway/IOS-12.x

CSeq: 2 REGISTER

Content-Length: 0

Jan 15 21:21:28.066: //-1/xxxxxxxxxxxx/SIP/Msg/ccsipDisplayMsg:

Sent:

SIP/2.0 401 Unauthorized

Via: SIP/2.0/UDP 192.168.10.16:5060;rport;branch=z9hG4bK1986204771

From: <sip:407@10.1.1.1>;tag=714839302

To: <sip:407@10.1.1.1>;tag=4C617B0-1A7E

Date: Thu, 15 Jan 2009 21:21:28 GMT

Call-ID: 1592243375@192.168.10.16

Server: Cisco-SIPGateway/IOS-12.x

CSeq: 2 REGISTER

WWW-Authenticate: Digest realm="",nonce="05A495BC007A3591",algorithm=MD5,qop="au th"

Content-Length: 0

This is my config:

voice register global

mode cme

source-address 10.1.1.1 port 5060

max-dn 1

max-pool 1

authenticate register

!

voice register dn 1

number 407

no-reg

!

voice register pool 1

id mac 0020.F735.02A1

number 1 dn 1

dtmf-relay rtp-nte

username 407 password ext407

codec g711ulaw

no vad

!

Any help would be appreciated. Thanks

5 Replies 5

paolo bevilacqua
Hall of Fame
Hall of Fame

The device wants to register with same ip as CME ?!?

Hmm.. I'm not sure what that is about.. Maybe it is NAT'ng.

I changed the IP of the device to 10.1.1.5. Set up the port it is plugged into to be on the Voice VLAN. Same thing:

Received:

REGISTER sip:10.1.1.1:5060 SIP/2.0

Via: SIP/2.0/UDP 10.1.1.5:5060;rport;branch=z9hG4bK1411286857

From: <407>;tag=385332712

To: <407>

Call-ID: 335855849@10.1.1.5

CSeq: 1 REGISTER

Contact: <407>

Max-Forwards: 5

User-Agent: CyberData Intercom

Expires: 3600

Content-Length: 0

Jan 15 22:34:04.470: //-1/xxxxxxxxxxxx/SIP/Error/ccsip_reg_search_call_id_table: No entry found in sipCallID Table

Jan 15 22:34:04.470: //-1/xxxxxxxxxxxx/SIP/Error/sipSPI_validate_own_ip_addr: ReqLine IP addr does not match with host IP addr

Jan 15 22:34:04.470: //227/72C276DF81AE/SIP/Error/ccsip_spi_register_incoming_registration: Registration Authorization failed with authorization header=

Jan 15 22:34:04.470: //-1/xxxxxxxxxxxx/SIP/Msg/ccsipDisplayMsg:

Sent:

SIP/2.0 100 Trying

Via: SIP/2.0/UDP 10.1.1.5:5060;rport;branch=z9hG4bK1411286857

From: <407>;tag=385332712

To: <407>

Date: Thu, 15 Jan 2009 22:34:04 GMT

Call-ID: 335855849@10.1.1.5

Server: Cisco-SIPGateway/IOS-12.x

CSeq: 1 REGISTER

Content-Length: 0

Jan 15 22:34:04.470: //-1/xxxxxxxxxxxx/SIP/Msg/ccsipDisplayMsg:

Sent:

SIP/2.0 401 Unauthorized

Via: SIP/2.0/UDP 10.1.1.5:5060;rport;branch=z9hG4bK1411286857

From: <407>;tag=385332712

To: <407>;tag=50890E8-7F7

Date: Thu, 15 Jan 2009 22:34:04 GMT

Call-ID: 335855849@10.1.1.5

Server: Cisco-SIPGateway/IOS-12.x

CSeq: 1 REGISTER

A couple of things to be aware of:

-SIP CME will only allow devices to register without authentication on the same subnet

-If the device is on a different subnet, you must put a 'username password ' on the voice register pool configuration.

-SIP CME doesn't officially support 3rd party devices, but a majority of devices will work anyways

-Paolo is actually incorrect on the IP address. The Via header will be used to direct the SIP packets, and this is normal behavior.

Here is a registration example for a 3951:

Received:

REGISTER sip:172.18.110.80 SIP/2.0

From: <1020>;tag=6oEvX1-gy

To: <1020>

Call-ID: EP0-lG4QesZjBD@172.18.110.80

CSeq: 187 REGISTER

Via: SIP/2.0/UDP 14.50.233.55:5060;branch=z9hG4bKwokBD-MA5lTcsJ1

Contact: <1020>;+sip.instance="";+u.sip!model.ccm.cisco.com="412"

Max-Forwards: 70

Authorization: Digest username="a",realm="",uri="sip:172.18.110.80",response="ea67ab428023c52b7d9329b2a401d2f1",algorithm=MD5,nonce="4667E6D30003ED8E",qop=auth,cnonce="94de76c0",nc=000000aa

User-Agent: Cisco-CP3951/8.1

Expires: 0

Supported: 100rel, replaces, norefersub, X-cisco-callinfo, X-cisco-service-control

Content-Length: 0

Sent:

SIP/2.0 100 Trying

Date: Fri, 16 Jan 2009 00:09:45 GMT

From: <1020>;tag=6oEvX1-gy

Content-Length: 0

To: <1020>

Call-ID: EP0-lG4QesZjBD@172.18.110.80

Via: SIP/2.0/UDP 14.50.233.55:5060;branch=z9hG4bKwokBD-MA5lTcsJ1

Server: Cisco-SIPGateway/IOS-12.x

CSeq: 187 REGISTER

Sent:

SIP/2.0 200 OK

Date: Fri, 16 Jan 2009 00:09:45 GMT

From: <1020>;tag=6oEvX1-gy

Content-Length: 0

To: <1020>;tag=244640CC-8FE

Contact: <1020>;expires=0

Expires: 0

Call-ID: EP0-lG4QesZjBD@172.18.110.80

Via: SIP/2.0/UDP 14.50.233.55:5060;branch=z9hG4bKwokBD-MA5lTcsJ1

Server: Cisco-SIPGateway/IOS-12.x

CSeq: 187 REGISTER

hth,

nick

I got it to work! I added the realm paramater to voice global and it works great now. Thanks!

Nick is correct, I was confused. After the unauthorized message, an authenticating phone is supposed to try again again with the credentials. So the error messassages are actually misleading in this case.

Getting Started

Find answers to your questions by entering keywords or phrases in the Search bar above. New here? Use these resources to familiarize yourself with the community: