Buy or Renew
Buy or Renew
cancel
Turn on suggestions
Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type.
Showing results for 
Search instead for 
Did you mean: 
cancel
Start a conversation
2793
Views
0
Helpful
9
Replies

CUCM SIP Trunk to Gateway not working Calls fail.

HeribertoVV
Level 1
Level 1

‎12-20-2016 03:15 PM - edited ‎03-17-2019 09:00 AM

Hello,

When I made any call to any route pattern that goes to a gateway SIP trunk I receive "The dialed number does not allow the call to be completed..." This behavior happens even with FAC or with no FAC nedeed calls. When the RP asks for FAC, I insert it and after I receive the same message.

I did'n receive any log in gateway when I debug ccapi inout or ccsip all.

2016/12/20 16:55:03.316|CC|SETUP|37794213|37794214|1039@SRV-CALLMANAGER-SUB|091718890|091718890
2016/12/20 16:55:03.345|CC|OFFERED|37794213|37794214|1039|091718890|091718890|SEP94D4692A27C5|Gateway_SIP_Trunk
2016/12/20 16:55:03.346|SIPT|37794214|TCP|OUT|172.20.214.10|5060|Gateway_SIP_Trunk|172.20.214.20|5060|2,100,14,1.1006^*^*|134206|56654300-8591b6c7-fa26-ad614ac@172.20.214.10|INVITE
2016/12/20 16:55:03.362|SIPT|37794214|TCP|IN|172.20.214.10|5060|Gateway_SIP_Trunk|172.20.214.20|5060|2,100,14,131.3^172.20.214.20^*|134207|56654300-8591b6c7-fa26-ad614ac@172.20.214.10|100 Trying
2016/12/20 16:55:03.366|SIPT|37794214|TCP|IN|172.20.214.10|5060|Gateway_SIP_Trunk|172.20.214.20|5060|2,100,14,131.4^172.20.214.20^*|134210|56654300-8591b6c7-fa26-ad614ac@172.20.214.10|404 Not Found
2016/12/20 16:55:03.366|SIPT|37794214|TCP|OUT|172.20.214.10|5060|Gateway_SIP_Trunk|172.20.214.20|5060|2,100,14,131.4^172.20.214.20^*|134211|56654300-8591b6c7-fa26-ad614ac@172.20.214.10|ACK
2016/12/20 16:55:03.386|SIPL|37794213|TCP|OUT|172.20.214.10|5061|SEP94D4692A27C5|172.20.214.49|50530|2,100,14,1.1008^*^*|134212|94d4692a-27c50014-45fa632b-1d9ef9dd@172.20.214.49|183 Session Progress
2016/12/20 16:55:04.449|SIPL|37794213|TCP|IN|172.20.214.10|5061|SEP94D4692A27C5|172.20.214.49|50530|2,100,18,41.250^172.20.214.49^*|134215|94d4692a-27c50014-45fa632b-1d9ef9dd@172.20.214.49|CANCEL
2016/12/20 16:55:04.449|SIPL|37794213|TCP|OUT|172.20.214.10|5061|SEP94D4692A27C5|172.20.214.49|50530|2,100,18,41.250^172.20.214.49^*|134216|94d4692a-27c50014-45fa632b-1d9ef9dd@172.20.214.49|200 OK
2016/12/20 16:55:04.450|SIPL|37794213|TCP|OUT|172.20.214.10|5061|SEP94D4692A27C5|172.20.214.49|50530|2,100,18,41.250^172.20.214.49^*|134217|94d4692a-27c50014-45fa632b-1d9ef9dd@172.20.214.49|487 Request Cancelled
2016/12/20 16:55:04.450|CC|RELEASE|37794213|37794214|1
2016/12/20 16:55:04.454|SIPL|37794213|TCP|IN|172.20.214.10|5061|SEP94D4692A27C5|172.20.214.49|50530|2,100,18,41.251^172.20.214.49^*|134218|94d4692a-27c50014-45fa632b-1d9ef9dd@172.20.214.49|ACK
2016/12/20 16:55:58.284|SIPL|0|TCP|IN|172.20.214.10|5061|SEP94D4692A27C5|172.20.214.49|50530|2,100,18,41.254^172.20.214.49^*|134238|94d4692a-27c50015-68781233-3d0c8c25@172.20.214.49|INVITE
2016/12/20 16:55:58.284|SIPL|0|TCP|OUT|172.20.214.10|5061|SEP94D4692A27C5|172.20.214.49|50530|2,100,18,41.254^172.20.214.49^*|134239|94d4692a-27c50015-68781233-3d0c8c25@172.20.214.49|100 Trying
2016/12/20 16:55:59.224|SIPL|37794216|TCP|OUT|172.20.214.10|5061|SEP94D4692A27C5|172.20.214.49|50530|2,100,18,41.258^172.20.214.49^*|134251|94d4692a-27c50015-68781233-3d0c8c25@172.20.214.49|500 Internal Server Error
2016/12/20 16:55:59.242|SIPL|37794216|TCP|IN|172.20.214.10|5061|SEP94D4692A27C5|172.20.214.49|50530|2,100,18,41.259^172.20.214.49^*|134254|94d4692a-27c50015-68781233-3d0c8c25@172.20.214.49|ACK
2016/12/20 16:55:59.242|CC|REJECT|37794216|37794217|1039@SRV-CALLMANAGER-SUB|9991|9991|0
2016/12/20 16:56:42.666|SIPL|0|TCP|IN|172.20.214.10|5061|SEP94D4692A27C5|172.20.214.49|50530|2,100,18,41.264^172.20.214.49^*|134282|94d4692a-27c50016-35e1b8b3-6adbfbb9@172.20.214.49|INVITE
2016/12/20 16:56:42.667|SIPL|0|TCP|OUT|172.20.214.10|5061|SEP94D4692A27C5|172.20.214.49|50530|2,100,18,41.264^172.20.214.49^*|134283|94d4692a-27c50016-35e1b8b3-6adbfbb9@172.20.214.49|100 Trying
2016/12/20 16:56:43.245|CC|SETUP|37794218|37794219|1039@SRV-CALLMANAGER-SUB|9999|9999
2016/12/20 16:56:43.249|CC|OFFERED|37794218|37794219|1039|9999|9999|SEP94D4692A27C5|Gateway_SIP_Trunk
2016/12/20 16:56:43.249|SIPT|37794219|TCP|OUT|172.20.214.10|5060|Gateway_SIP_Trunk|172.20.214.20|5060|2,100,14,1.1011^*^*|134295|92000d00-8591b72b-fa35-ad614ac@172.20.214.10|INVITE
2016/12/20 16:56:43.264|SIPT|37794219|TCP|IN|172.20.214.10|5060|Gateway_SIP_Trunk|172.20.214.20|5060|2,100,14,134.3^172.20.214.20^*|134299|92000d00-8591b72b-fa35-ad614ac@172.20.214.10|100 Trying
2016/12/20 16:56:43.264|SIPT|37794219|TCP|IN|172.20.214.10|5060|Gateway_SIP_Trunk|172.20.214.20|5060|2,100,14,134.3^172.20.214.20^*|134300|92000d00-8591b72b-fa35-ad614ac@172.20.214.10|404 Not Found
2016/12/20 16:56:43.265|SIPT|37794219|TCP|OUT|172.20.214.10|5060|Gateway_SIP_Trunk|172.20.214.20|5060|2,100,14,134.3^172.20.214.20^*|134301|92000d00-8591b72b-fa35-ad614ac@172.20.214.10|ACK
2016/12/20 16:56:43.279|SIPL|37794218|TCP|OUT|172.20.214.10|5061|SEP94D4692A27C5|172.20.214.49|50530|2,100,14,1.1013^*^*|134302|94d4692a-27c50016-35e1b8b3-6adbfbb9@172.20.214.49|183 Session Progress
2016/12/20 16:56:43.999|SIPL|37794218|TCP|IN|172.20.214.10|5061|SEP94D4692A27C5|172.20.214.49|50530|2,100,18,41.271^172.20.214.49^*|134305|94d4692a-27c50016-35e1b8b3-6adbfbb9@172.20.214.49|CANCEL
2016/12/20 16:56:43.999|SIPL|37794218|TCP|OUT|172.20.214.10|5061|SEP94D4692A27C5|172.20.214.49|50530|2,100,18,41.271^172.20.214.49^*|134306|94d4692a-27c50016-35e1b8b3-6adbfbb9@172.20.214.49|200 OK
2016/12/20 16:56:44.000|CC|RELEASE|37794218|37794219|1
2016/12/20 16:56:44.000|SIPL|37794218|TCP|OUT|172.20.214.10|5061|SEP94D4692A27C5|172.20.214.49|50530|2,100,18,41.271^172.20.214.49^*|134307|94d4692a-27c50016-35e1b8b3-6adbfbb9@172.20.214.49|487 Request Cancelled
2016/12/20 16:56:44.007|SIPL|37794218|TCP|IN|172.20.214.10|5061|SEP94D4692A27C5|172.20.214.49|50530|2,100,18,41.272^172.20.214.49^*|134308|94d4692a-27c50016-35e1b8b3-6adbfbb9@172.20.214.49|ACK
2016/12/20 16:56:44.987|SIPL|0|TCP|IN|172.20.214.10|5061|SEP94D4692A27C5|172.20.214.49|50530|2,100,18,41.275^172.20.214.49^*|134311|94d4692a-27c50017-705e2b41-458c0d8b@172.20.214.49|INVITE
2016/12/20 16:56:44.988|SIPL|0|TCP|OUT|172.20.214.10|5061|SEP94D4692A27C5|172.20.214.49|50530|2,100,18,41.275^172.20.214.49^*|134312|94d4692a-27c50017-705e2b41-458c0d8b@172.20.214.49|100 Trying
2016/12/20 16:56:45.915|CC|SETUP|37794221|37794222|1039@SRV-CALLMANAGER-SUB|9991|9991
2016/12/20 16:56:45.917|CC|OFFERED|37794221|37794222|1039|9991|9991|SEP94D4692A27C5|Gateway_SIP_Trunk
2016/12/20 16:56:45.917|SIPT|37794222|TCP|OUT|172.20.214.10|5060|Gateway_SIP_Trunk|172.20.214.20|5060|2,100,14,1.1016^*^*|134324|93313a00-8591b72d-fa37-ad614ac@172.20.214.10|INVITE
2016/12/20 16:56:45.931|SIPT|37794222|TCP|IN|172.20.214.10|5060|Gateway_SIP_Trunk|172.20.214.20|5060|2,100,14,134.4^172.20.214.20^*|134328|93313a00-8591b72d-fa37-ad614ac@172.20.214.10|100 Trying
2016/12/20 16:56:45.932|SIPT|37794222|TCP|IN|172.20.214.10|5060|Gateway_SIP_Trunk|172.20.214.20|5060|2,100,14,134.5^172.20.214.20^*|134329|93313a00-8591b72d-fa37-ad614ac@172.20.214.10|404 Not Found
2016/12/20 16:56:45.932|SIPT|37794222|TCP|OUT|172.20.214.10|5060|Gateway_SIP_Trunk|172.20.214.20|5060|2,100,14,134.5^172.20.214.20^*|134330|93313a00-8591b72d-fa37-ad614ac@172.20.214.10|ACK
2016/12/20 16:56:45.939|SIPL|37794221|TCP|OUT|172.20.214.10|5061|SEP94D4692A27C5|172.20.214.49|50530|2,100,14,1.1018^*^*|134331|94d4692a-27c50017-705e2b41-458c0d8b@172.20.214.49|183 Session Progress
2016/12/20 16:56:46.435|SIPL|37794221|TCP|IN|172.20.214.10|5061|SEP94D4692A27C5|172.20.214.49|50530|2,100,18,41.282^172.20.214.49^*|134334|94d4692a-27c50017-705e2b41-458c0d8b@172.20.214.49|CANCEL
2016/12/20 16:56:46.436|SIPL|37794221|TCP|OUT|172.20.214.10|5061|SEP94D4692A27C5|172.20.214.49|50530|2,100,18,41.282^172.20.214.49^*|134335|94d4692a-27c50017-705e2b41-458c0d8b@172.20.214.49|200 OK
2016/12/20 16:56:46.436|CC|RELEASE|37794221|37794222|1
2016/12/20 16:56:46.436|SIPL|37794221|TCP|OUT|172.20.214.10|5061|SEP94D4692A27C5|172.20.214.49|50530|2,100,18,41.282^172.20.214.49^*|134336|94d4692a-27c50017-705e2b41-458c0d8b@172.20.214.49|487 Request Cancelled
2016/12/20 16:56:46.444|SIPL|37794221|TCP|IN|172.20.214.10|5061|SEP94D4692A27C5|172.20.214.49|50530|2,100,18,41.283^172.20.214.49^*|134337|94d4692a-27c50017-705e2b41-458c0d8b@172.20.214.49|ACK
2016/12/20 16:56:50.974|SIPL|0|TCP|IN|172.20.214.10|5061|SEP94D4692A27C5|172.20.214.49|50530|2,100,18,41.286^172.20.214.49^*|134340|94d4692a-27c50018-265abfe9-00890f87@172.20.214.49|INVITE
2016/12/20 16:56:50.975|SIPL|0|TCP|OUT|172.20.214.10|5061|SEP94D4692A27C5|172.20.214.49|50530|2,100,18,41.286^172.20.214.49^*|134341|94d4692a-27c50018-265abfe9-00890f87@172.20.214.49|100 Trying
2016/12/20 16:56:55.544|CC|SETUP|37794224|37794225|1039@SRV-CALLMANAGER-SUB|091718890|091718890
2016/12/20 16:56:55.547|CC|OFFERED|37794224|37794225|1039|091718890|091718890|SEP94D4692A27C5|Gateway_SIP_Trunk
2016/12/20 16:56:55.548|SIPT|37794225|TCP|OUT|172.20.214.10|5060|Gateway_SIP_Trunk|172.20.214.20|5060|2,100,14,1.1021^*^*|134367|99271b00-8591b737-fa3c-ad614ac@172.20.214.10|INVITE
2016/12/20 16:56:55.563|SIPT|37794225|TCP|IN|172.20.214.10|5060|Gateway_SIP_Trunk|172.20.214.20|5060|2,100,14,134.6^172.20.214.20^*|134371|99271b00-8591b737-fa3c-ad614ac@172.20.214.10|100 Trying
2016/12/20 16:56:55.563|SIPT|37794225|TCP|IN|172.20.214.10|5060|Gateway_SIP_Trunk|172.20.214.20|5060|2,100,14,134.7^172.20.214.20^*|134372|99271b00-8591b737-fa3c-ad614ac@172.20.214.10|404 Not Found
2016/12/20 16:56:55.563|SIPT|37794225|TCP|OUT|172.20.214.10|5060|Gateway_SIP_Trunk|172.20.214.20|5060|2,100,14,134.7^172.20.214.20^*|134373|99271b00-8591b737-fa3c-ad614ac@172.20.214.10|ACK
2016/12/20 16:56:55.573|SIPL|37794224|TCP|OUT|172.20.214.10|5061|SEP94D4692A27C5|172.20.214.49|50530|2,100,14,1.1023^*^*|134374|94d4692a-27c50018-265abfe9-00890f87@172.20.214.49|183 Session Progress
2016/12/20 16:56:56.941|SIPL|37794224|TCP|IN|172.20.214.10|5061|SEP94D4692A27C5|172.20.214.49|50530|2,100,18,41.300^172.20.214.49^*|134377|94d4692a-27c50018-265abfe9-00890f87@172.20.214.49|CANCEL
2016/12/20 16:56:56.942|SIPL|37794224|TCP|OUT|172.20.214.10|5061|SEP94D4692A27C5|172.20.214.49|50530|2,100,18,41.300^172.20.214.49^*|134378|94d4692a-27c50018-265abfe9-00890f87@172.20.214.49|200 OK
2016/12/20 16:56:56.943|CC|RELEASE|37794224|37794225|1
2016/12/20 16:56:56.943|SIPL|37794224|TCP|OUT|172.20.214.10|5061|SEP94D4692A27C5|172.20.214.49|50530|2,100,18,41.300^172.20.214.49^*|134379|94d4692a-27c50018-265abfe9-00890f87@172.20.214.49|487 Request Cancelled
2016/12/20 16:56:56.948|SIPL|37794224|TCP|IN|172.20.214.10|5061|SEP94D4692A27C5|172.20.214.49|50530|2,100,18,41.301^172.20.214.49^*|134380|94d4692a-27c50018-265abfe9-00890f87@172.20.214.49|ACK

Any suggestion?

Labels:
0 Helpful
9 Replies 9

Dennis Mink
VIP Alumni
VIP Alumni

‎12-20-2016 04:44 PM

I am assuming therefore that the above log is from the cucm, which is sending an invite, as per below, to the gateway. the gateway eventually responds with a 404 not found, which is very likely caused by missing destination patter, or your CUBE not being registered with your ISP

Can you past show sip-ua register status, and debug dial-peer when you make an outbound call through your CUBE,also add the full config.

16:55:03.346|SIPT|37794214|TCP|OUT|172.20.214.10|5060|Gateway_SIP_Trunk|172.20.214.20|5060|2,100,14,1.1006^*^*|134206|56654300-8591b6c7-fa26-ad614ac@172.20.214.10|INVITE
Please remember to rate useful posts, by clicking on the stars below.

0 Helpful

HeribertoVV
Level 1
Level 1
In response to Dennis Mink

‎12-21-2016 11:32 AM

Hello,

This is my output:

GW-VOZ-FRISA#sh sip-ua register status 
Line peer expires(sec) reg survival P-Associ-URI
================================ ========== ============ === ======== ============

This is my sip-ua running:

sip-ua 
 registrar ipv4:172.20.214.9 expires 3600
 xfer target dial-peer

I can't see any log when I debug dialpeer, csim all, etc.

Thanks for your help.

0 Helpful

andresudt
Level 1
Level 1
In response to HeribertoVV

‎12-21-2016 05:07 PM

If you are connected to the Router via SSH or Telnet, you may need to enable Logging (Not sure in case you already did this, but just to cover your bases).

Router# terminal monitor

Router# show log //This one will show the logging configuration

In case term mon is running and you see console messages sent to you, you should be able to get a debug from the voice gateway.

-----------------------------------------

If the above is not the case, the call is not hitting the Voice Gateway and at this point the configuration on your SIP trunk could be pointing to the wrong IP

0 Helpful

HeribertoVV
Level 1
Level 1
In response to andresudt

‎12-22-2016 07:42 AM

Attached is my Trunk configuration. It is pointing to 172.20.214.20.

I tried any kind of debug (dialpeer, voip, ccsip, ccapi, voice), but I can't see anything when I make calls. Even when I use show log, I am not able to see any log (I see logs to other matters, but not to ones I wrote).

Preview file
79 KB
Preview file
74 KB
Preview file
102 KB
Preview file
108 KB
Preview file
93 KB
0 Helpful

Mohammed al Baqari
Level 11
Level 11

‎12-20-2016 06:44 PM

Agreed with Dennis. The destination IOS sending 404 error (Not found).

2016/12/20 16:56:43.264|SIPT|37794219|TCP|IN|172.20.214.10|5060|Gateway_SIP_Trunk|172.20.214.20|5060|2,100,14,134.3^172.20.214.20^*|134300|92000d00-8591b72b-fa35-ad614ac@172.20.214.10|404 Not Found

You need to make sure that you are looking at the right gateway/cube which has IP 172.20.214.10. Also, make sure that you debug ccsip mess with 'terminal monitor' enabled and logging monitor is set to debugging

If you post the config of the device, then this will help.

0 Helpful

HeribertoVV
Level 1
Level 1
In response to Mohammed al Baqari

‎12-21-2016 11:50 AM

My Gateway has the IP 172.20.214.20. Why CUCM is looking at 172.20.214.10 (this is my Subscriber).

Kind regards,

Heriberto

0 Helpful

Dennis Mink
VIP Alumni
VIP Alumni
In response to HeribertoVV

‎12-21-2016 02:37 PM

your trunk might be "registered" on your sub, primarily, that is why you see 172.20.214.10 as the source address.

If are sure you are looking at the correct gateway .20 and you are not seeing any SIP messages when you debug.

set up a SPAN port to that .20 and capture using wireshark the gateways input/output and filter using "sip".

if you are seeing the appropriate SIP signalling, then you should see output when you run debug ccsip messages

Please remember to rate useful posts, by clicking on the stars below.

0 Helpful

HeribertoVV
Level 1
Level 1
In response to Dennis Mink

‎12-21-2016 03:20 PM

Sorry Dennis, but I don't understand very well.

My SIP trunk is stablished to 172.20.214.20 and it appears as Full Service. Is my sip-ua configuration OK? 

This is my voice service voip config:

voice service voip
 dtmf-interworking rtp-nte
 allow-connections h323 to h323
 allow-connections h323 to sip
 allow-connections sip to h323
 allow-connections sip to sip
 no supplementary-service sip handle-replaces
 fax protocol t38 version 0 ls-redundancy 0 hs-redundancy 0 fallback none
 sip
 bind control source-interface GigabitEthernet0/0
 bind media source-interface GigabitEthernet0/0
 session transport tcp
 registrar server expires max 300 min 60
 early-offer forced
 midcall-signaling passthru

0 Helpful

Dennis Mink
VIP Alumni
VIP Alumni
In response to HeribertoVV

‎12-21-2016 07:19 PM

your sip-ua register status should look something like this:

Test_VGW#sh sip-ua register status
Line peer expires(sec) registered P-Associ-URI
================================ ========== ============ ========== ============
N3613321R -1 3 yes
yours doesnt show that
Please remember to rate useful posts, by clicking on the stars below.

0 Helpful
Customers Also Viewed These Support Documents