I am not sure how the customer has managed to make the flow so complex.
Are these two different clusters which we are talking about, is there an ICT trunk between, or do the clusters have an h323 gateway in between as it seems from the call flow, do correct me if i am wrong.
With out looking and the call manager traces and debugs, its very hard to say what will fix the issue.
But do let me know the following:
1. Call manager versions
2. MOH being used is unicast or multicast.
Had a similar issue once, and it was fixed by checking the MTP box on the gateway page.
Please try the same, reset the gateway from cucm page and see if it helps.
Thanks for taking the time to look at this and reply.
My customer should really have bought a basic TDM telephone system as this would have done what they want. CUCM doesnt really fit with the small comanies needs for call processing so I am having to find imaginative ways of getting the call structure the customer wants to work with CUCM.
No multiple clusters, no IP trunks just ISDN30 -> H323 voice gateway -> CUCM
Main DDi should only be able to have:
9 concurrent calls Mo -Fr 8am to 6pm
3 concurrent calls Mo -Fr 6pm to 8pm
2 concurrent calls Mo -Fr 8pm to 10pm
1 concurrent calls Mo -Fr 10pm to 8am
So to do this I need to use ToD partitions but these on there own wont restrict the amount of concurrent calls so the only way I can see of doing this is to create 4 translation patterns for the main DDi and translate to 4 different numbers that are sent back to the H323 gateway so they can be processed through defined dial-peers with the max-conn statement. Call then comes back to CUCM and is sent to its destination.
Main DDi comes in as 5090 so:
Mo-Fr 8am to 6pm translate to 4551; send to H323 gateway with dial-peer voip for 4551 with max-conn 9 and send back to CUCM. On CUCM another translation for 4551 which sends call to Hunt Group 1001
Mo-Fr 6pm to 8pm translate to 4552; send to H323 gateway with dial-peer voip for 4552 with max-conn 3 and send back to CUCM. On CUCM another translation for 4552 which sends call to Hunt Group 1001
I am going to configure CUCM gateway for MTP required and test again tomorrow so hopefully the hold functionality will work and if so I have a working solution. Messy, but works!
SIP traces provide key information in troubleshooting SIP Trunks, SIP
endpoints and other SIP related issues. Even though these traces are in
clear text, these texts can be gibberish unless you understand fully
what they mean. This document attempts to br...
Please find the attached HTML document, download and open it on your PC.
This provides an easy to use form where you simply answer a few
questions and it will render the proper jabber-config.xml file for you
to copy/paste. There is built in logic to verif...
CUCM Database Replication is an area in which Cisco customers and
partners have asked for more in-depth training in being able to properly
assess a replication problem and potentially resolve an issue without
involving TAC. This document discusses the bas...