I'm trying to better understand and troubleshoot my CUCM environment. I have CUCM 11.5, a CUBE router and an ITSP SIP provider as my connection to the PSTN.
I have outbound calls working, internal numbers can call and voice calls work fine, however I cannot get incoming calls to work.
I believe my CUBE router is forwarding calls to CUCM because when I do debug voice ccapi inout the output shows the correct inbound and outbound dialpeers being matched.
So I believe my cube is telling me it is forwarding the calls correctly but when I call from my mobile (cell) phone inwards the phone rings and eventually goes to the the SIP providers voicemail.
Are there any commands I can run on the CUCM to troubleshoot this? To see if CUCM is receiving the call? And then if it is receiving the call, why its not connecting it?
Great it worked out , Outbound proxy command is used to route SIP Messages to the outbound proxy . You can even use outbound proxy on individual dial-peers.
you need to pull the CCM traces in order to verify this ..other than you can take debugs on CUBE router where you can have pretty much good idea about the call issue however for detail you need to see the CCM traces in order to find out actual root cause.
From CUCM, try using RTMT > Session Trace > Real- Time and see if you can find your incoming call or not. You can also run real time trace from CLI but this will be complex due to amount of messages.
From CUBE using debug ccsip messages command will help you to judge if CUCM received the message or not. In case CUCM receives the message from CUBE will send a response. If you see a response from CUCM then it received the message from CUBE else not.
Please attach ccsip debug output from CUBE Router, we can find out reason why call got disconnected from it, which will set us in direction for troubleshooting the issue.
Attached is the show ccsip messages command. I've sanitised it, removing the calling mobile phone number and replacing it with 07000111222 and also the SIP number which I've renamed to 01000111222.
That is interesting, because I assumed this message didn't matter. Currently the CUBE is setup with a SIP-UA with the relevant details for the SIP trunk provider so the CUBE router authenticates with the ITSP provider and it can place calls.
The number 201 is an internal number which I'm trying to get all external calls forwarded to. I assumed the 201 number wouldn't need to be configured to authenticate with the service provider because that's what the CUBE was doing?
I currently don't have any message digest setup on the CUCM (that i know of :) ) and the realm configured is between the CUBE and the ITSP as part of their setup instructions.
Should I need to configure message digest on CUCM to authenticate the SIP provider? Or should I need to configure the realm on CUCM? I assumed the CUBE handled both of these elements.
A CUBE has two parts: The SIP connection to the provider and the SIP connection to the CUCM. BOTH connections have to be configured correctly.
For example when an IP phone makes a call, the CUCM sends an INVITE to the CUBE, the CUBE (depending on the CUBE configuration) can modify this INVITE and then sends an INVITE to the provider. Normally you must do some number normalization, most providers (if not all) want to see E164 numbers.
The same when you receive a call from the provider, the CUBE receives an INVITE from the provider and the CUBE sends an INVITE to the CUCM
One of your call legs might not be correctly configured (number, codec, etc)
The 201 jabber client is also in location hub_none, see attached.
Regarding location bandwidth, I've configured region bandwidth but I don't think I've configured location bandwidth. I'm looking now, where is this configured?
I've just noticed the location in my device pool was set to "none" rather than hub_none. I've now changed it, it hasn't appeared to have made a difference but I just wanted to update you.
I assume the device pool location should also be set to hub_none?
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:
