cancel
Showing results for 
Search instead for 
Did you mean: 
cancel
3317
Views
0
Helpful
5
Replies

CUBE will not register with SIP Provider-Debugs show nothing

Dennis Topo Jr
Level 1
Level 1

Hello all...

I’m new to voice and I’m interested in learning more. My main problem is, after much reading and tweaking, I still cannot get my CUBE gateway to register with my sip provider. I have a fully functioning Asterisk box behind a nat router here at my home office- works perfect...but I wanted to be a glutton for punishment and try to do it the Cisco way )....with CUBE and CUCM. Here’s my setup:

*CUBE on a GNS3 router 3725 running  3700 Software (C3725-ADVENTERPRISEK9_IVS-M), Version 12.4(25b)

Single interface mapped to my PC nic via GNS3- 192.168.0.11    IP routing disabled

*CUCM 8.6.2 running in VMWare player- 192.168.0.5

*Cisco\Linksys NAT router- 192.168.0.1 with appropriate ports forwarded to the CUBE

*Callwithus SIP account- separate account from my Asterisk setup

*IP Communicator softphone on PC- registered with CUCM

Connectivity is fine between all involved- can ping and resolve- I enabled debug ccsip all- and nothing so far- no activity\connection in.

Do I need to set up the trunk from the CUBE to CUCM to “trigger” the registration? I did try that as well, but not sure it’s done correctly. Or maybe this is not possible using GNS3??- I did not read anything definitive either way. Appreciate any help guys...

Here’s my CUBE config:

! No configuration change since last restart

! NVRAM config last updated at 14:51:27 UTC Sat Jul 13 2013

!

version 12.4

service timestamps debug datetime msec

service timestamps log datetime msec

no service password-encryption

!

hostname cube-1

!

boot-start-marker

boot-end-marker

!

no aaa new-model

memory-size iomem 5

no ip routing

no ip cef

!

ip domain name dtech.local

ip name-server 192.168.0.6

ip name-server 192.168.0.1

ip auth-proxy max-nodata-conns 3

ip admission max-nodata-conns 3

!

voice service voip

allow-connections h323 to h323

allow-connections h323 to sip

allow-connections sip to h323

allow-connections sip to sip

h323

sip

!

interface FastEthernet0/0

ip address 192.168.0.11 255.255.255.0

no ip redirects

no ip route-cache

duplex auto

speed auto

!

interface FastEthernet0/1

ip address 192.168.0.10 255.255.255.0

no ip route-cache

shutdown

duplex auto

speed auto

!

ip default-gateway 192.168.0.1

ip forward-protocol nd

!

!

no ip http server

no ip http secure-server

control-plane

!

mgcp behavior g729-variants static-pt

!

dial-peer voice 1 voip

description Out to CallWithUs

destination-pattern .T

session protocol sipv2

session target dns:sip.callwithus.com

incoming called-number .

dtmf-relay rtp-nte

codec g711ulaw

no vad

!

dial-peer voice 200 voip

description To CUCM

destination-pattern .T

session protocol sipv2

session target ipv4:192.168.0.5

dtmf-relay rtp-nte

codec g711ulaw

!

sip-ua

authentication username 1234 password 4321 realm sip.callwithus.com

retry invite 3

retry register 3

retry subscribe 3

registrar dns:sip.callwithus.com expires 180

sip-server dns:sip.callwithus.com

!

gatekeeper

shutdown

!

line con 0

exec-timeout 0 0

privilege level 15

logging synchronous

line aux 0

exec-timeout 0 0

privilege level 15

logging synchronous

line vty 0 4

login

!

ntp clock-period 17179859

ntp server 192.5.41.40

!

end

5 Replies 5

brmeade
Level 4
Level 4

Does the gateway successfully resolve the IP for sip.callwithus.com?  Look at doing some DNS debugs.  An A-record probably isn't enough.  You need an SRV record for that host as well.

Brian.....it does resolve. I'm able to ping sip.callwithus.com from the gateway and the correct IP is returned. I would still need a srv record for the host on my DNS server?

Ok... well..at least I got some debug activity now-- I added the credential line to sip-ua as such:

sip-ua

credentials username 450 password 1111 realm callwithus.com

authentication username 450 password 1111

retry invite 3

retry register 3

retry subscribe 3

registrar dns:sip.callwithus.com expires 180

sip-server dns:sip.callwithus.com

Now getting an Unauthorized return: Any ideas anybody?

SIP/2.0 401 Unauthorized

Via: SIP/2.0/UDP  192.168.0.11:5060;branch=z9hG4bK52631;rport=59987;received=68.194.127.35

From: "450" <>450@sip.callwithus.com>;tag=3CB5C-8B8

To: "450" <>450@sip.callwithus.com>;tag=05fa965d41f3adc51e16f9a7acf1c273.be8d

Call-ID: 1E8ADCD1-2BDE11D6-8002C0B2-8CF6ED57

CSeq: 6 REGISTER

WWW-Authenticate: Digest realm="sip.callwithus.com", nonce="UeSdLlHknAKCjHV4OP0/M1ZFJrp5W8YZ"

Server: CWU SIP GW

Content-Length: 0

Try realm sip.callwithus.com in "credentials".

I tried that Paulo...thanks...but no go. I've tried so many combinations in the sip-ua. Took the credentials line out- tried with and without the "sip".callwithus.com- added the no remote-party-id.

The current sip-ua and register and recieve debugs are below if anybody else wants to take a stab. This should not be so hard! Fustrating! Anybody deal with setting up a trunk for callwithus.com ??  Thanks again all

*****************************************************************************************************************

sip-ua

credentials username 169 password 1111 realm sip.callwithus.com

authentication username 169 password 1111

no remote-party-id

retry invite 2

retry register 10

timers connect 100

registrar dns:sip.callwithus.com expires 120

sip-server dns:sip.callwithus.com

REGISTER sip:sip.callwithus.com:5060 SIP/2.0

Via: SIP/2.0/UDP  192.168.0.11:5060;branch=z9hG4bKFBBC

From: "169" <>169@sip.callwithus.com>;tag=B8DBC-1C13

To: "169" <>169@sip.callwithus.com>

Date: Tue, 16 Jul 2013 20:53:33 GMT

Call-ID: 1E681327-2BDE11D6-80028CB2-3561462B

User-Agent: Cisco-SIPGateway/IOS-12.x

Max-Forwards: 70

Timestamp: 1374008013

CSeq: 16 REGISTER

Contact: <169770968>

Expires: 180

Authorization: Digest username="169",realm="sip.callwithus.com",uri="sip:sip.callwithus.com:5060",response="1467693bb958235d7eeffa30354a5a4c",nonce="UeWz+VHlss0t7jKwQ1GLMOlGkuqdVCWa",algorithm=md5

Content-Length: 0

Jul 16 20:53:33.720: //-1/xxxxxxxxxxxx/SIP/Info/HandleUdpSocketReads: Msg enqueued for SPI with IP addr: 204.74.213.5:5060

Jul 16 20:53:33.724: //-1/xxxxxxxxxxxx/SIP/Transport/sipTransportProcessNWNewConnMsg: context=0x658CBBA8

Jul 16 20:53:33.732: //-1/xxxxxxxxxxxx/SIP/Msg/ccsipDisplayMsg:

Received:

SIP/2.0 401 Unauthorized

Via: SIP/2.0/UDP  192.168.0.11:5060;branch=z9hG4bKFBBC;rport=52764;received=68.194.127.35

From: "169" <>169@sip.callwithus.com>;tag=B8DBC-1C13

To: "169" <>169@sip.callwithus.com>;tag=05fa965d41f3adc51e16f9a7acf1c273.bf2c

Call-ID: 1E681327-2BDE11D6-80028CB2-3561462B

CSeq: 16 REGISTER

WWW-Authenticate: Digest realm="sip.callwithus.com", nonce="UeWz+VHlss0t7jKwQ1GLMOlGkuqdVCWa"

Server: CWU SIP GW

Content-Length: 0