Got a curious problem. FIrst let me say that my UCM instance has an error that I can't seem to divine the solution to: Though all services seem to work, I get an error regarding the Cisco Messaging Service being down. I didn't think this to be critical due to the fact that in one of the examples, I noticed that the service was not active. If this is a critical service to CURRI, then... However, I doubt it...
Here is what is happening:
- Translation Patter Trigger
- UCM 9.1
- Translation pattern defines 4 digit dialing to 7 digit DN
- RTMT shows active connections to the route server. Route server logs show periodic connection attempts from UCM
- Browser from another node can reach and post to route server
Attached you will find two PNG images from RTMT:
Capture1.png shows the External Call Control performance graphs. Capture2.png shows the Connection-to-PDPServer graphs.
It seems I have connections to the route server from the UCM perspective, but all the calls experience the Failure treatment.
Any ideas?
My ECC timeout is set to 5000.
Upon further review, I found out the following:
- The exact same setup works on a trial UCM 10.0
- I looked at a posting titled "Application not invoked on Incoming call" and it seems my 9.1 node has that issue. When I dialed a number that does not exist, the translation pattern trigger point was exercised.
- the 10.x node has the same "Cisco Messaging Interface" critical service down issue.
-------------------------------------------------------------------------------------------------------------
First, the easy answer. CMI should generally be disabled unless you are doing SMDI integration to a 3rd-party voicemail system. It will generally be down if you are running a virtual server because it cannot access the appropriate serial interface. Just deactivate it.
From your description, it sounds like you're running into a defect that keeps coming up. If you modify an existing ECC-Profile, it does not generate the proper reloading of the profile, so responses from your server get ignored by CUCM. You can verify this is happening by 'restarting' the Cisco CallManager service. After you restart, the responses should be handled properly by Unified CM.
Comments
0 comments
Please sign in to leave a comment.