01-13-2015 08:44 AM - edited 03-17-2019 01:34 AM
Solved! Go to Solution.
01-14-2015 12:32 AM
So what is your call flow?
Cucm>>>sip>>>cube>>>sip>>>itsp?
Or do you have a direct sip trunk between cucm and itsp
01-13-2015 08:56 AM
Can you describe what's involved in your solution. What is the call flow?
01-13-2015 11:48 PM
I should of mentioned that we changed Service Providers. We also are trying to establish a SIP on out network as well.
01-14-2015 12:32 AM
So what is your call flow?
Cucm>>>sip>>>cube>>>sip>>>itsp?
Or do you have a direct sip trunk between cucm and itsp
01-14-2015 10:33 AM
Sorry hit the wrong button.
It goes CUCM>>>sip>>>cube>>>sip>>>sp mpls router>>>sip>>>itsp..
There is a Cisco 2921 VG router in between the redundant core switches and the SP MPLS router. The 2921 VG router has three GE ports.
I believe I need to configure SIP-UA with disable early media 180 on that 2921 VG router.
01-14-2015 11:37 AM
Why have you come to such a dramatic conclusion?
Please send a debug ccsip message from the cube. Include the calling and called number. Also send your sh run
01-16-2015 01:19 AM
After looking at the configurations and finding out this a piece was missing.
The old call flow was like this: Old SP Cube router had two Gig-E ports
CUCM>>>sip>>>Cube>>>sip>>>itsp
New Service Provider router didn't provide two Gig-E ports.
New Call Flow.
CUCM>>>sip>>>VG router>>>sip>>>SP mpls router>>>sip>>>itsp.
The VG router is only passing traffic and providing an two Gig-E connection to each core switch. SP MPLS router is configured to handle all SIP traffic (All voice voices, dial-peers, etc.).
I don't have copy of the SP router
01-16-2015 01:19 AM
Tony,
Okay so your new voice gateway is just doing ip routing to the SP MPLS router. Your cucm sip trunk is pointing to the MPLS gateway ip address.
In this case there are two options to troubleshoot this.
1. CUCM collect traces
2. Contact Service provider since you do not have access to their gateway.
If you can collect cucm traces, then we may be able to see what is going on.
01-16-2015 01:45 AM
Are you asking if my CUCM SIP trunk is pointing to SP MPLS gateway IP address?
I will do collect the trace from the CUCM tomorrow.
I am waiting for the configuration from the SP MPLS router.
01-16-2015 01:48 AM
Yes. In this scenario, your cucm sip trunk has to be pointing to the MPLS gateway ip. Is it not?
01-16-2015 02:30 PM
Yes, my CUCM SIP trunk is pointing the the MPLS gateway IP address.
01-17-2015 07:21 AM
Here is the text file from my collect trace..
01-17-2015 07:21 AM
After looking at the trace files. I get this error.
400 bad request - malformed cc-diversion + cc-redirect links
Currently the header is set to PAI.
01-17-2015 08:12 AM
The diversion header is not set properly. It looks like your service provider has configured a wrong sip profile on the diversion header. Its missing a closing ">"
This is what is in the sip header...
Diversion: <sip:9512146397@smartvoice.telepacific.com
This is what it needs to be
Diversion: <sip:9512146397@smartvoice.telepacific.com>
You need to contact them and bring this to their attention
01-17-2015 08:30 AM
Should the header be set to default or PAI?
Thank you again
Discover and save your favorite ideas. Come back to expert answers, step-by-step guides, recent topics, and more.
New here? Get started with these tips. How to use Community New member guide