04-13-2010 09:38 AM - edited 03-15-2019 10:15 PM
04-16-2010 11:41 AM
I would check SIP port, IP addresses, Security Profile to make sure Protocol specified is correct (TCP,UDP or TLS)
and significant number of digits in SIP trunk,
PRI -- CUCM -- SIP -- IVR
Cn you upload CUCM traces so we can check
Include calling,called number, timestamps and call details
04-19-2010 12:57 PM
Hi gogasca,
Thank you for the reply.
The SIP trunks are fully functional with the exception of dialing out the PRI trunks.
This will be my first go around pulling trace files that are not TSP related traces. Can you provide a little info on what traces would be helpful and how to enable/capture them?
Thanx again...Frank
09-17-2010 01:34 PM
Hello Frank,
Can you kindly shed some light on the scenario as it's not that clear;
PRI----CM---SIP_TRUNK-----IVR
- the PRI's are located on a GW what is the connection between GW and CM ?
- you say calls from IVR fail; does the IVR initiate the call "the application" or is this an IVR part of a customer responce solution with agents that are initiating the calls via the trunk ?
- what is the codec used accross the complete scenario ?
- when the call fails what do u get ? ex; fast busy ?
By the way traces can be enabled and collected according to the following:
http://www.cisco.com/en/US/products/sw/voicesw/ps556/products_tech_note09186a0080094e89.shtml
Best Regards,
Mahmoud
09-20-2010 08:17 AM
Can you get these debugs for a failure:
debug isdn q931
debug voip ccapi inout
debug ccsip mess
Also post the output of 'sh run'. If the PRI and SIP gateways are different devices, please collect that information from both devices for the call.
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