cancel
Showing results for 
Search instead for 
Did you mean: 
cancel
Announcements

Welcome to the Cisco Small Business Community

Have a question? Click on a topic board below to get started in the community.

3823
Views
0
Helpful
13
Replies
david.macias
VIP Engager

UC520 SIP Trunk using sipgate.com behind home router?

I've been beating my head over this and can't figure out what could be wrong.  Hope someone can help me out.  Here's the network layout:

Internet - Cable Modem - 192.168.1.1 Wireless Router - 192.168.1.2 UC520 192.168.10.1

I can't get calls in or out and I'm not sure if it's the wireless router or the UC520 configuration.  I've attached the config and here's the output the registration status:

UC520#sh sip-ua register status
Line                             peer       expires(sec) registered P-Associ-URI
================================ ========== ============ ========== ============
<account number>             -1         210          yes
<phone number>                20010      35           no

I am not 100% sure why my account would show registered but not the phone number.  Heck, I'm not sure if my number is supposed to show up in the registration.

Here's the output of show sip messages:

UC520#debug ccsip messages
SIP Call messages tracing is enabled
UC520#
UC520#
UC520#
UC520#
UC520#
000454: Feb 25 15:05:09.695: //-1/xxxxxxxxxxxx/SIP/Msg/ccsipDisplayMsg:
Received:
INVITE sip:1170789e2@192.168.1.2:5060 SIP/2.0
Record-Route: <sip:204.155.28.10;lr=on;ftag=as6b398925>
Record-Route: <sip:172.30.20.1;lr>
Record-Route: <sip:204.155.28.10;lr=on;ftag=as6b398925>
Via: SIP/2.0/UDP 204.155.28.10:5060;branch=z9hG4bK1cf.ff868943.0
Via: SIP/2.0/UDP 172.30.20.1;branch=z9hG4bK1cf.ff868943.0
Via: SIP/2.0/UDP 204.155.28.10:5060;received=204.155.28.20;branch=z9hG4bK60069ae4
Via: SIP/2.0/UDP 204.155.29.58:5060;received=204.155.29.58;branch=z9hG4bK60069ae4;rport=5060
Max-Forwards: 67
From: "0005" <sip:0005@sipgate.com>;tag=as6b398925
To: <sip:1170789e2@sipgate.com>
Contact: <sip:0005@204.155.29.58>
Call-ID: 74c70c1026cf73137075ca6255d3ad3c@sipgate.com
CSeq: 103 INVITE
Allow: INVITE, ACK, CANCEL, OPTIONS, BYE, REFER, SUBSCRIBE, NOTIFY, INFO
Supported: replaces, timer
X-C2D: c2d-a
Content-Type: application/sdp
Content-Length: 468

v=0
o=root 1798661698 1798661699 IN IP4 204.155.29.58
s=sipgate VoIP GW
c=IN IP4 204.155.29.50
t=0 0
m=audio 42452 RTP/AVP 8 0 3 97 18 112 101
a=rtpmap:8 PCMA/8000
a=rtpmap:0 PCMU/8000
a=rtpmap:3 GSM/8000
a=rtpmap:97 iLBC/8000
a=fmtp:97 mode=30
a=rtpmap:18 G729/8000
a=fmtp:18 annexb=no
a=rtpmap:112 G726-32/8000
a=rtpmap:101 telephone-event/8000
a=fmtp:101 0-16
a=silenceSupp:off - - - -
a=ptime:20
a=sendrecv
a=direction:active
a=nortpproxy:yes

000455: Feb 25 15:05:09.703: //-1/xxxxxxxxxxxx/SIP/Msg/ccsipDisplayMsg:
Sent:
SIP/2.0 500 Internal Server Error
Via: SIP/2.0/UDP 204.155.28.10:5060;branch=z9hG4bK1cf.ff868943.0,SIP/2.0/UDP 172.30.20.1;branch=z9hG4bK1cf.ff868943.0,SIP/2.0/UDP 204.155.28.10:5060;received=204.155.28.20;branch=z9hG4bK60069ae4,SIP/2.0/UDP 204.155.29.58:5060;received=204.155.29.58;branch=z9hG4bK60069ae4;rport=5060
From: "0005" <sip:0005@sipgate.com>;tag=as6b398925
To: <sip:1170789e2@sipgate.com>;tag=3901798-1E80
Date: Fri, 25 Feb 2011 15:05:09 GMT
Call-ID: 74c70c1026cf73137075ca6255d3ad3c@sipgate.com
CSeq: 103 INVITE
Allow-Events: telephone-event
Reason: Q.850;cause=63
Server: Cisco-SIPGateway/IOS-12.x
Content-Length: 0


000456: Feb 25 15:05:09.795: //-1/xxxxxxxxxxxx/SIP/Msg/ccsipDisplayMsg:
Received:
ACK sip:1170789e2@192.168.1.2:5060 SIP/2.0
Via: SIP/2.0/UDP 204.155.28.10:5060;branch=z9hG4bK1cf.ff868943.0
Via: SIP/2.0/UDP 172.30.20.1;branch=z9hG4bK1cf.ff868943.0
From: "0005" <sip:0005@sipgate.com>;tag=as6b398925
Call-ID: 74c70c1026cf73137075ca6255d3ad3c@sipgate.com
To: <sip:1170789e2@sipgate.com>;tag=3901798-1E80
CSeq: 103 ACK
Max-Forwards: 69
Content-Length: 0
X-hint: rr-enforced

I think one of my problems is that the SIP header has my internat address, but I'm not 100% sure.  Anyone have any ideas?

Thank you.

13 REPLIES 13
Darren DeCroock
Enthusiast

Since you are getting a "500 Internal Server Error", I would think that the UC520 is blocking the incoming call.  As a test, I would try removing the access list to see if this will allow calls to work.

Config t

voice source-group CCA_SIP_SOURCE_GROUP_EXTERNAL
  no access-list 3

If it starts working after that, I would put the access-list back in, and get it configured correctly to allow incoming calls from your provider.

Thank you,

Darren

Darren,

Change the ACL seemed to have made a difference, but still no calls, here's the latest sip debug:

000482: Feb 25 17:31:35.707: //-1/xxxxxxxxxxxx/SIP/Msg/ccsipDisplayMsg:
Received:
...
000483: Feb 25 17:31:37.955: //-1/xxxxxxxxxxxx/SIP/Msg/ccsipDisplayMsg:
Received:
INVITE sip:1170789e2@192.168.1.2:5060 SIP/2.0
Record-Route: <204.155.28.10>
Record-Route: <172.30.20.1>
Record-Route: <204.155.28.10>
Via: SIP/2.0/UDP 204.155.28.10:5060;branch=z9hG4bK98f2.e8f80ca3.0
Via: SIP/2.0/UDP 172.30.20.1;branch=z9hG4bK98f2.e8f80ca3.0
Via: SIP/2.0/UDP 204.155.28.10:5060;received=204.155.28.20;branch=z9hG4bK5c434b8c
Via: SIP/2.0/UDP 204.155.29.54:5060;received=204.155.29.54;branch=z9hG4bK5c434b8c;rport=5060
Max-Forwards: 67
From: "0005" <>0005@sipgate.com>;tag=as3a86841b
To: <>1170789e2@sipgate.com>
Contact: <0005>
Call-ID: 5978cf351d57f1894f5014d3593803c3@sipgate.com
CSeq: 103 INVITE
Allow: INVITE, ACK, CANCEL, OPTIONS, BYE, REFER, SUBSCRIBE, NOTIFY, INFO
Supported: replaces, timer
X-C2D: c2d-a
Content-Type: application/sdp
Content-Length: 466

v=0
o=root 974762952 974762953 IN IP4 204.155.29.54
s=sipgate VoIP GW
c=IN IP4 204.155.29.50
t=0 0
m=audio 44070 RTP/AVP 8 0 3 97 18 112 101
a=rtpmap:8 PCMA/8000
a=rtpmap:0 PCMU/8000
a=rtpmap:3 GSM/8000
a=rtpmap:97 iLBC/8000
a=fmtp:97 mode=30
a=rtpmap:18 G729/8000
a=fmtp:18 annexb=no
a=rtpmap:112 G726-32/8000
a=rtpmap:101 telephone-event/8000
a=fmtp:101 0-16
a=silenceSupp:off - - - -
a=ptime:20
a=sendrecv
a=direction:active
a=nortpproxy:yes

000484: Feb 25 17:31:37.971: //445/EF15E540808C/SIP/Msg/ccsipDisplayMsg:
Sent:
SIP/2.0 100 Trying
Via: SIP/2.0/UDP 204.155.28.10:5060;branch=z9hG4bK98f2.e8f80ca3.0,SIP/2.0/UDP 172.30.20.1;branch=z9hG4bK98f2.e8f80ca3.0,SIP/2.0/UDP 204.155.28.10:5060;received=204.155.28.20;branch=z9hG4bK5c434b8c,SIP/2.0/UDP 204.155.29.54:5060;received=204.155.29.54;branch=z9hG4bK5c434b8c;rport=5060
From: "0005" <>0005@sipgate.com>;tag=as3a86841b
To: <>1170789e2@sipgate.com>
Date: Fri, 25 Feb 2011 17:31:37 GMT
Call-ID: 5978cf351d57f1894f5014d3593803c3@sipgate.com
CSeq: 103 INVITE
Allow-Events: telephone-event
Server: Cisco-SIPGateway/IOS-12.x
Content-Length: 0


000485: Feb 25 17:31:37.971: //445/EF15E540808C/SIP/Msg/ccsipDisplayMsg:
Sent:
SIP/2.0 484 Address Incomplete
Via: SIP/2.0/UDP 204.155.28.10:5060;branch=z9hG4bK98f2.e8f80ca3.0,SIP/2.0/UDP 172.30.20.1;branch=z9hG4bK98f2.e8f80ca3.0,SIP/2.0/UDP 204.155.28.10:5060;received=204.155.28.20;branch=z9hG4bK5c434b8c,SIP/2.0/UDP 204.155.29.54:5060;received=204.155.29.54;branch=z9hG4bK5c434b8c;rport=5060
From: "0005" <>0005@sipgate.com>;tag=as3a86841b
To: <>1170789e2@sipgate.com>;tag=41630C4-111B
Date: Fri, 25 Feb 2011 17:31:37 GMT
Call-ID: 5978cf351d57f1894f5014d3593803c3@sipgate.com
CSeq: 103 INVITE
Allow-Events: telephone-event
Server: Cisco-SIPGateway/IOS-12.x
Reason: Q.850;cause=28
Content-Length: 0


000486: Feb 25 17:31:38.071: //445/EF15E540808C/SIP/Msg/ccsipDisplayMsg:
Sent:
SIP/2.0 484 Address Incomplete
Via: SIP/2.0/UDP 204.155.28.10:5060;branch=z9hG4bK98f2.e8f80ca3.0,SIP/2.0/UDP 172.30.20.1;branch=z9hG4bK98f2.e8f80ca3.0,SIP/2.0/UDP 204.155.28.10:5060;received=204.155.28.20;branch=z9hG4bK5c434b8c,SIP/2.0/UDP 204.155.29.54:5060;received=204.155.29.54;branch=z9hG4bK5c434b8c;rport=5060
From: "0005" <>0005@sipgate.com>;tag=as3a86841b
To: <>1170789e2@sipgate.com>;tag=41630C4-111B
Date: Fri, 25 Feb 2011 17:31:37 GMT
Call-ID: 5978cf351d57f1894f5014d3593803c3@sipgate.com
CSeq: 103 INVITE
Allow-Events: telephone-event
Server: Cisco-SIPGateway/IOS-12.x
Reason: Q.850;cause=28
Content-Length: 0


000487: Feb 25 17:31:38.071: //-1/xxxxxxxxxxxx/SIP/Msg/ccsipDisplayMsg:
Received:
ACK sip:1170789e2@192.168.1.2:5060 SIP/2.0
Via: SIP/2.0/UDP 204.155.28.10:5060;branch=z9hG4bK98f2.e8f80ca3.0
Via: SIP/2.0/UDP 172.30.20.1;branch=z9hG4bK98f2.e8f80ca3.0
From: "0005" <>0005@sipgate.com>;tag=as3a86841b
Call-ID: 5978cf351d57f1894f5014d3593803c3@sipgate.com
To: <>1170789e2@sipgate.com>;tag=41630C4-111B
CSeq: 103 ACK
Max-Forwards: 69
Content-Length: 0
X-hint: rr-enforced


000488: Feb 25 17:31:38.167: //-1/xxxxxxxxxxxx/SIP/Msg/ccsipDisplayMsg:
Received:
ACK sip:1170789e2@192.168.1.2:5060 SIP/2.0
Via: SIP/2.0/UDP 204.155.28.10:5060;branch=z9hG4bK98f2.e8f80ca3.0
Via: SIP/2.0/UDP 172.30.20.1;branch=z9hG4bK98f2.e8f80ca3.0
From: "0005" <>0005@sipgate.com>;tag=as3a86841b
Call-ID: 5978cf351d57f1894f5014d3593803c3@sipgate.com
To: <>1170789e2@sipgate.com>;tag=41630C4-111B
CSeq: 103 ACK
Max-Forwards: 69
Content-Length: 0
X-hint: rr-enforced

Any thoughts on this?

david

Quite a few things going on here by the quick look at your config....

Why are you naming your internal domain to your providers? sipgate.com

Anyway in your voice service voip, change the localhost dns:blahblah to be your internal domain, and change the outbound-proxy to be ipv4:ip.of.sipgate

In the sip-ua did you setup your credentials they sent you?

I will look further at the config when I have a few.

Are you doing this via CLI or CCA?

Cheers

Bob

OK Looked further try IP rather than DNS

registrar dns:sipgate.com expires 3600

registrar ipv4:x.x.x.x

same thing with the realm and SIP server

Why are you naming your internal domain to your providers?

Removed this as I don't have an internal domain.

In the sip-ua did you setup your credentials they sent you?

Yes.

In the sip-ua did you setup your credentials they sent you?

Mainly CCA, but it depends on what changes I need to make.

Made the changes you requested removed sipgate.com and used the IP 204.155.28.10 instead, however now I don't get any messages when making a test call doing the ccsip messages debug.  However I do see this:

Sent:
REGISTER sip:204.155.28.10:5060 SIP/2.0
Via: SIP/2.0/UDP 192.168.1.2:5060;branch=z9hG4bKC3815EC
From: <>@204.155.28.10>;tag=C31D538-2174
To: <>@204.155.28.10>
Date: Mon, 28 Feb 2011 04:00:18 GMT
Call-ID: 69A569E4-422411E0-804ADAD8-6B0D59AC
User-Agent: Cisco-SIPGateway/IOS-12.x
Max-Forwards: 70
Timestamp: 1298865618
CSeq: 10 REGISTER
Contact: <>@192.168.1.2:5060>
Expires:  3600
Supported: path
Content-Length: 0


000094: Feb 28 04:00:18.905: //1583/000000000000/SIP/Msg/ccsipDisplayMsg:
Received:
SIP/2.0 401 Unauthorized
Via: SIP/2.0/UDP 192.168.1.2:5060;rport=63239;received=75.118.188.162;branch=z9hG4bKC3815EC
From: <>@204.155.28.10>;tag=C31D538-2174
To: <>@204.155.28.10>;tag=ddf9a9f0de4595ec12441b9d8d3ee250.ca01
Call-ID: 69A569E4-422411E0-804ADAD8-6B0D59AC
CSeq: 10 REGISTER
WWW-Authenticate: Digest realm="sipgate.com", nonce="4d6b1bbf0b5a2c6c5ac9342bca4968ce319d54bc"
Content-Length: 0


000095: Feb 28 04:00:18.909: //-1/xxxxxxxxxxxx/SIP/Msg/ccsipDisplayMsg:
Sent:
REGISTER sip:204.155.28.10:5060 SIP/2.0
Via: SIP/2.0/UDP 192.168.1.2:5060;branch=z9hG4bKC39251F
From: <>@204.155.28.10>;tag=C31D538-2174
To: <>@204.155.28.10>
Date: Mon, 28 Feb 2011 04:00:18 GMT
Call-ID: 69A569E4-422411E0-804ADAD8-6B0D59AC
User-Agent: Cisco-SIPGateway/IOS-12.x
Max-Forwards: 70
Timestamp: 1298865618
CSeq: 11 REGISTER
Contact: <>@192.168.1.2:5060>
Expires: 3600
Authorization: Digest username="1170789e2",realm="sipgate.com",uri="sip:204.155.28.10:5060",response="de57c83ba00ccec317aae8cf69b97634",nonce="4d6b1bbf0b5a2c6c5ac9342bca4968ce319d54bc",algorithm=md5
Content-Length: 0


000096: Feb 28 04:00:19.001: //1583/000000000000/SIP/Msg/ccsipDisplayMsg:
Received:
SIP/2.0 403 Forbidden (check user field)
Via: SIP/2.0/UDP 192.168.1.2:5060;rport=63239;received=75.118.188.162;branch=z9hG4bKC39251F
From: <>@204.155.28.10>;tag=C31D538-2174
To: <>@204.155.28.10>;tag=ddf9a9f0de4595ec12441b9d8d3ee250.c2ef
Call-ID: 69A569E4-422411E0-804ADAD8-6B0D59AC
CSeq: 11 REGISTER
Content-Length: 0

Any other ideas?  By the way, I appreciate the help.

david

Hi David,

Is it possible you can post the following up so i can take a look at it please:

* SIP-UA Config with the removal of sensative data or replaced with "X's"

* Your Voice Translation-Profile that you have configured for your SIP trunk

* Your DN configured for the SIP trunk (Remove the sensitive data part of the DN I.E the SIP trunks username)

Do you have the dial-peers for the SIP trunk configured properly as well?

There are quite a few things that can go wrong with sip trunks, but generally they are quite easy to sort out, make sure that you do not need to do any port forwarding on your router of port 5060 and point it to the UC-500, this is often an overlooked issue.

Also I suspect that it is able to contact the provider otherwise you wouldn't get back some of the error you have shown here, however there you may need to be prepared to remove the entire ACL so you have no firewall, re-test it and if the issue does not continue to happen then we know for certain the UC is restricting is flow.

Will wait for your answer, with a little patience we can resolve this problem for you

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 :) *

It looks like the username/password is failing, confirm you have the correct information and so does your ITSP for your connection.

Your cable modem is it a router/modem or straight modem?

Brian

I've copied and pasted my username and password straight from the sipgate.com.

My modem is a modem, behind it I have a wireless router.

david

David,

I've removed the ACLs as well as the port  forwarding, I'm now getting a tad bit different errors which in my  uneducated mind seems more promissing.  Here's the registration output:

show sip-ua register status
Line                             peer       expires(sec) registered P-Associ-URI
================================ ========== ============ ========== ============
          -1         255          yes

shoe ccsip messages:


UC520#
000378: Feb 28 13:35:45.999: //-1/xxxxxxxxxxxx/SIP/Msg/ccsipDisplayMsg:
Received:
...
000379: Feb 28 13:35:47.595: //-1/xxxxxxxxxxxx/SIP/Msg/ccsipDisplayMsg:
Received:
INVITE sip:@192.168.1.2:5060 SIP/2.0
Record-Route: <204.155.28.10>
Record-Route: <172.30.20.1>
Record-Route: <204.155.28.10>
Via: SIP/2.0/UDP 204.155.28.10:5060;branch=z9hG4bKa2e3.9b1a9922.0
Via: SIP/2.0/UDP 172.30.20.1;branch=z9hG4bKa2e3.9b1a9922.0
Via: SIP/2.0/UDP 204.155.28.10:5060;received=204.155.28.20;branch=z9hG4bK00e6ae88
Via: SIP/2.0/UDP 204.155.29.58:5060;received=204.155.29.58;branch=z9hG4bK00e6ae88;rport=5060
Max-Forwards: 67
From: "0005" <>0005@sipgate.com>;tag=as6d2f038a
To: <>@sipgate.com>
Contact: <0005>
Call-ID: 06156b400e652e5e604fbf42003ad276@sipgate.com
CSeq: 103 INVITE
Allow: INVITE, ACK, CANCEL, OPTIONS, BYE, REFER, SUBSCRIBE, NOTIFY, INFO
Supported: replaces, timer
X-C2D: c2d-a
Content-Type: application/sdp
Content-Length: 466

v=0
o=root 144641615 144641616 IN IP4 204.155.29.58
s=sipgate VoIP GW
c=IN IP4 204.155.29.55
t=0 0
m=audio 62624 RTP/AVP 8 0 3 97 18 112 101
a=rtpmap:8 PCMA/8000
a=rtpmap:0 PCMU/8000
a=rtpmap:3 GSM/8000
a=rtpmap:97 iLBC/8000
a=fmtp:97 mode=30
a=rtpmap:18 G729/8000
a=fmtp:18 annexb=no
a=rtpmap:112 G726-32/8000
a=rtpmap:101 telephone-event/8000
a=fmtp:101 0-16
a=silenceSupp:off - - - -
a=ptime:20
a=sendrecv
a=direction:active
a=nortpproxy:yes

000380: Feb 28 13:35:47.611: //1677/7C0D98CC8067/SIP/Msg/ccsipDisplayMsg:
Sent:
SIP/2.0 100 Trying
Via: SIP/2.0/UDP  204.155.28.10:5060;branch=z9hG4bKa2e3.9b1a9922.0,SIP/2.0/UDP  172.30.20.1;branch=z9hG4bKa2e3.9b1a9922.0,SIP/2.0/UDP  204.155.28.10:5060;received=204.155.28.20;branch=z9hG4bK00e6ae88,SIP/2.0/UDP   204.155.29.58:5060;received=204.155.29.58;branch=z9hG4bK00e6ae88;rport=5060
From: "0005" <>0005@sipgate.com>;tag=as6d2f038a
To: <>@sipgate.com>
Date: Mon, 28 Feb 2011 13:35:47 GMT
Call-ID: 06156b400e652e5e604fbf42003ad276@sipgate.com
CSeq: 103 INVITE
Allow-Events: telephone-event
Server: Cisco-SIPGateway/IOS-12.x
Content-Length: 0


000381: Feb 28 13:35:47.611: //1677/7C0D98CC8067/SIP/Msg/ccsipDisplayMsg:
Sent:
SIP/2.0 484 Address Incomplete
Via: SIP/2.0/UDP  204.155.28.10:5060;branch=z9hG4bKa2e3.9b1a9922.0,SIP/2.0/UDP  172.30.20.1;branch=z9hG4bKa2e3.9b1a9922.0,SIP/2.0/UDP  204.155.28.10:5060;received=204.155.28.20;branch=z9hG4bK00e6ae88,SIP/2.0/UDP   204.155.29.58:5060;received=204.155.29.58;branch=z9hG4bK00e6ae88;rport=5060
From: "0005" <>0005@sipgate.com>;tag=as6d2f038a
To: <>@sipgate.com>;tag=E40B35C-22C7
Date: Mon, 28 Feb 2011 13:35:47 GMT
Call-ID: 06156b400e652e5e604fbf42003ad276@sipgate.com
CSeq: 103 INVITE
Allow-Events: telephone-event
Server: Cisco-SIPGateway/IOS-12.x
Reason: Q.850;cause=28
Content-Length: 0


000382: Feb 28 13:35:47.711: //1677/7C0D98CC8067/SIP/Msg/ccsipDisplayMsg:
Sent:
SIP/2.0 484 Address Incomplete
Via: SIP/2.0/UDP  204.155.28.10:5060;branch=z9hG4bKa2e3.9b1a9922.0,SIP/2.0/UDP  172.30.20.1;branch=z9hG4bKa2e3.9b1a9922.0,SIP/2.0/UDP  204.155.28.10:5060;received=204.155.28.20;branch=z9hG4bK00e6ae88,SIP/2.0/UDP   204.155.29.58:5060;received=204.155.29.58;branch=z9hG4bK00e6ae88;rport=5060
From: "0005" <>0005@sipgate.com>;tag=as6d2f038a
To: <>@sipgate.com>;tag=E40B35C-22C7
Date: Mon, 28 Feb 2011 13:35:47 GMT
Call-ID: 06156b400e652e5e604fbf42003ad276@sipgate.com
CSeq: 103 INVITE
Allow-Events: telephone-event
Server: Cisco-SIPGateway/IOS-12.x
Reason: Q.850;cause=28
Content-Length: 0


000383: Feb 28 13:35:47.711: //-1/xxxxxxxxxxxx/SIP/Msg/ccsipDisplayMsg:
Received:
ACK sip:@192.168.1.2:5060 SIP/2.0
Via: SIP/2.0/UDP 204.155.28.10:5060;branch=z9hG4bKa2e3.9b1a9922.0
Via: SIP/2.0/UDP 172.30.20.1;branch=z9hG4bKa2e3.9b1a9922.0
From: "0005" <>0005@sipgate.com>;tag=as6d2f038a
Call-ID: 06156b400e652e5e604fbf42003ad276@sipgate.com
To: <>@sipgate.com>;tag=E40B35C-22C7
CSeq: 103 ACK
Max-Forwards: 69
Content-Length: 0
X-hint: rr-enforced


000384: Feb 28 13:35:47.803: //-1/xxxxxxxxxxxx/SIP/Msg/ccsipDisplayMsg:
Received:
ACK sip:@192.168.1.2:5060 SIP/2.0
Via: SIP/2.0/UDP 204.155.28.10:5060;branch=z9hG4bKa2e3.9b1a9922.0
Via: SIP/2.0/UDP 172.30.20.1;branch=z9hG4bKa2e3.9b1a9922.0
From: "0005" <>0005@sipgate.com>;tag=as6d2f038a
Call-ID: 06156b400e652e5e604fbf42003ad276@sipgate.com
To: <>@sipgate.com>;tag=E40B35C-22C7
CSeq: 103 ACK
Max-Forwards: 69
Content-Length: 0
X-hint: rr-enforced

* SIP-UA Config with the removal of sensative data or replaced with "X's"

sip-ua
  credentials username password 7 realm sipgate.com
  authentication username password 7
  no remote-party-id
  retry invite 2
  retry register 10
  timers connect 100
  registrar dns:sipgate.com expires 3600
  sip-server dns:sipgate.com
  host-registrar

* Your Voice Translation-Profile that you have configured for your SIP trunk

I'm not sure if this is what you're looking for, but I hope it is:

David,

I've removed the ACLs as well as the port  forwarding, I'm now getting a tad bit different errors which in my  uneducated mind seems more promissing.  Here's the registration output:

show sip-ua register status
Line                             peer       expires(sec) registered P-Associ-URI
================================ ========== ============ ========== ============
          -1         255          yes

shoe ccsip messages:


UC520#
000378: Feb 28 13:35:45.999: //-1/xxxxxxxxxxxx/SIP/Msg/ccsipDisplayMsg:
Received:
...
000379: Feb 28 13:35:47.595: //-1/xxxxxxxxxxxx/SIP/Msg/ccsipDisplayMsg:
Received:
INVITE sip:@192.168.1.2:5060 SIP/2.0
Record-Route: <204.155.28.10>
Record-Route: <172.30.20.1>
Record-Route: <204.155.28.10>
Via: SIP/2.0/UDP 204.155.28.10:5060;branch=z9hG4bKa2e3.9b1a9922.0
Via: SIP/2.0/UDP 172.30.20.1;branch=z9hG4bKa2e3.9b1a9922.0
Via: SIP/2.0/UDP 204.155.28.10:5060;received=204.155.28.20;branch=z9hG4bK00e6ae88
Via: SIP/2.0/UDP 204.155.29.58:5060;received=204.155.29.58;branch=z9hG4bK00e6ae88;rport=5060
Max-Forwards: 67
From: "0005" <>0005@sipgate.com>;tag=as6d2f038a
To: <>@sipgate.com>
Contact: <0005>
Call-ID: 06156b400e652e5e604fbf42003ad276@sipgate.com
CSeq: 103 INVITE
Allow: INVITE, ACK, CANCEL, OPTIONS, BYE, REFER, SUBSCRIBE, NOTIFY, INFO
Supported: replaces, timer
X-C2D: c2d-a
Content-Type: application/sdp
Content-Length: 466

v=0
o=root 144641615 144641616 IN IP4 204.155.29.58
s=sipgate VoIP GW
c=IN IP4 204.155.29.55
t=0 0
m=audio 62624 RTP/AVP 8 0 3 97 18 112 101
a=rtpmap:8 PCMA/8000
a=rtpmap:0 PCMU/8000
a=rtpmap:3 GSM/8000
a=rtpmap:97 iLBC/8000
a=fmtp:97 mode=30
a=rtpmap:18 G729/8000
a=fmtp:18 annexb=no
a=rtpmap:112 G726-32/8000
a=rtpmap:101 telephone-event/8000
a=fmtp:101 0-16
a=silenceSupp:off - - - -
a=ptime:20
a=sendrecv
a=direction:active
a=nortpproxy:yes

000380: Feb 28 13:35:47.611: //1677/7C0D98CC8067/SIP/Msg/ccsipDisplayMsg:
Sent:
SIP/2.0 100 Trying
Via: SIP/2.0/UDP  204.155.28.10:5060;branch=z9hG4bKa2e3.9b1a9922.0,SIP/2.0/UDP  172.30.20.1;branch=z9hG4bKa2e3.9b1a9922.0,SIP/2.0/UDP  204.155.28.10:5060;received=204.155.28.20;branch=z9hG4bK00e6ae88,SIP/2.0/UDP   204.155.29.58:5060;received=204.155.29.58;branch=z9hG4bK00e6ae88;rport=5060
From: "0005" <>0005@sipgate.com>;tag=as6d2f038a
To: <>@sipgate.com>
Date: Mon, 28 Feb 2011 13:35:47 GMT
Call-ID: 06156b400e652e5e604fbf42003ad276@sipgate.com
CSeq: 103 INVITE
Allow-Events: telephone-event
Server: Cisco-SIPGateway/IOS-12.x
Content-Length: 0


000381: Feb 28 13:35:47.611: //1677/7C0D98CC8067/SIP/Msg/ccsipDisplayMsg:
Sent:
SIP/2.0 484 Address Incomplete
Via: SIP/2.0/UDP  204.155.28.10:5060;branch=z9hG4bKa2e3.9b1a9922.0,SIP/2.0/UDP  172.30.20.1;branch=z9hG4bKa2e3.9b1a9922.0,SIP/2.0/UDP  204.155.28.10:5060;received=204.155.28.20;branch=z9hG4bK00e6ae88,SIP/2.0/UDP   204.155.29.58:5060;received=204.155.29.58;branch=z9hG4bK00e6ae88;rport=5060
From: "0005" <>0005@sipgate.com>;tag=as6d2f038a
To: <>@sipgate.com>;tag=E40B35C-22C7
Date: Mon, 28 Feb 2011 13:35:47 GMT
Call-ID: 06156b400e652e5e604fbf42003ad276@sipgate.com
CSeq: 103 INVITE
Allow-Events: telephone-event
Server: Cisco-SIPGateway/IOS-12.x
Reason: Q.850;cause=28
Content-Length: 0


000382: Feb 28 13:35:47.711: //1677/7C0D98CC8067/SIP/Msg/ccsipDisplayMsg:
Sent:
SIP/2.0 484 Address Incomplete
Via: SIP/2.0/UDP  204.155.28.10:5060;branch=z9hG4bKa2e3.9b1a9922.0,SIP/2.0/UDP  172.30.20.1;branch=z9hG4bKa2e3.9b1a9922.0,SIP/2.0/UDP  204.155.28.10:5060;received=204.155.28.20;branch=z9hG4bK00e6ae88,SIP/2.0/UDP   204.155.29.58:5060;received=204.155.29.58;branch=z9hG4bK00e6ae88;rport=5060
From: "0005" <>0005@sipgate.com>;tag=as6d2f038a
To: <>@sipgate.com>;tag=E40B35C-22C7
Date: Mon, 28 Feb 2011 13:35:47 GMT
Call-ID: 06156b400e652e5e604fbf42003ad276@sipgate.com
CSeq: 103 INVITE
Allow-Events: telephone-event
Server: Cisco-SIPGateway/IOS-12.x
Reason: Q.850;cause=28
Content-Length: 0


000383: Feb 28 13:35:47.711: //-1/xxxxxxxxxxxx/SIP/Msg/ccsipDisplayMsg:
Received:
ACK sip:@192.168.1.2:5060 SIP/2.0
Via: SIP/2.0/UDP 204.155.28.10:5060;branch=z9hG4bKa2e3.9b1a9922.0
Via: SIP/2.0/UDP 172.30.20.1;branch=z9hG4bKa2e3.9b1a9922.0
From: "0005" <>0005@sipgate.com>;tag=as6d2f038a
Call-ID: 06156b400e652e5e604fbf42003ad276@sipgate.com
To: <>@sipgate.com>;tag=E40B35C-22C7
CSeq: 103 ACK
Max-Forwards: 69
Content-Length: 0
X-hint: rr-enforced


000384: Feb 28 13:35:47.803: //-1/xxxxxxxxxxxx/SIP/Msg/ccsipDisplayMsg:
Received:
ACK sip:@192.168.1.2:5060 SIP/2.0
Via: SIP/2.0/UDP 204.155.28.10:5060;branch=z9hG4bKa2e3.9b1a9922.0
Via: SIP/2.0/UDP 172.30.20.1;branch=z9hG4bKa2e3.9b1a9922.0
From: "0005" <>0005@sipgate.com>;tag=as6d2f038a
Call-ID: 06156b400e652e5e604fbf42003ad276@sipgate.com
To: <>@sipgate.com>;tag=E40B35C-22C7
CSeq: 103 ACK
Max-Forwards: 69
Content-Length: 0
X-hint: rr-enforced

* SIP-UA Config with the removal of sensative data or replaced with "X's"

sip-ua
  credentials username password 7 realm sipgate.com
  authentication username password 7
  no remote-party-id
  retry invite 2
  retry register 10
  timers connect 100
  registrar dns:sipgate.com expires 3600
  sip-server dns:sipgate.com
  host-registrar

* Your Voice Translation-Profile that you have configured for your SIP trunk

I'm hoping this is what you're looking for.

voice translation-profile SIP_Incoming
  translate called 411
!
voice translation-profile SIP_Passthrough
  translate called 412

dial-peer voice 3000 voip
  description SIP
  translation-profile incoming SIP_Called_4
  session protocol sipv2
  session target sip-server
  incoming called-number
  voice-class codec 1 
  voice-class sip dtmf-relay force rtp-nte
  dtmf-relay rtp-nte
  ip qos dscp cs5 media
  ip qos dscp cs4 signaling
  no vad
!

* Your DN configured for the SIP trunk (Remove the sensitive data part of the DN I.E the SIP trunks username)

ephone-dn  52
  number
  description SIP Main Number registration
  preference 10
!
!
ephone-dn  53  dual-line
  number 2000 secondary no-reg both
  pickup-group 1
  label 2000
  description David Macias
  name David Macias
  call-forward busy 3099
  call-forward noan 3099 timeout 20

Keep in mind Sipgate has a letter in it's username.  Sipgate requires outbound calls to be placed using the username and not your phone number.  This might become a real pain because voice translation patterns do not have a place for letters. 

I was able to receive calls with Sipgate but I wasn't able to place calls after I registered because of the letter in the username.

I am not a SIP expert so I am interested in seeing what your outcome is.

Hi David,

I have a concern with this "SIP/2.0 484 Address Incomplete" this is a client failure response error message, which means the issues is local and not at SIPGATES end.

I need to know if you are willing to post your entire confguration in a txt file, the system appears to be registering but this could be clarified with the "sh sip reg stat" comman, if it is registering and you are getting the client side error, then we need to look at the configuration a bit deeper.

NOTE: A quick google search shows me that that quite a few people have some basic fundamental issues with getting sipgate to work on a Cisco system, i will continue narrowing down on why and see if we can get around it.

Your config would help a lot.

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 :) *

Yes, I'm afraid this might not be possible since I've not been able to find a single working example, but only one way to find out for myself.  I've attached my running config.  Thank you for everyone's help.

david

Hi David,

I compared your config to over 5 working ones I have here without going overboard, one thing I found consistent is a dial-peer missing on your txt config (Or I was just too blind and didn't see it).

dial-peer voice 1002 voip

corlist outgoing call-local

description ** star code to SIP trunk (Generic SIP Trunk Provider) **

preference 1

destination-pattern *..

voice-class codec 1

voice-class sip dtmf-relay force rtp-nte

session protocol sipv2

session target dns:sip00.mynetfone.com.au <----------------------- This is the SIP provider here locally

dtmf-relay rtp-nte

ip qos dscp cs5 media

ip qos dscp cs4 signaling

You have the standard Dial-Peer in there which is right, but it is missing one similar to this, now my SIP trunk setup skills are a little rusty as it has been a while since I have done one, but I can point out that your config is almost identical to one I would create...

Short of my setting up a SIPGATE account and lab testing it up, I am not sure I can help you any further, I have Google any known CME issues with SIPGATE and many people have issues with them even on the ISR's (2800/2900 series) CME systems as well, and that is using standard sip-ua configuration.

Your SIP is registering which indicates it is talking to the server and the reg request is being accepted, the problem you have is the outbound call, i just hope it turns out to just be a simple config issue, maybe SIPGATE are just fussy, but i would highly encourage you to contact them and ask them for a sample CME config, then contact SMB support and see if they can assist you with getting this configured on a CLI level to ensure it remains CCA compliant.

I will continue to look over your running-config, if something sticks out to me I will post again.

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 :) *