I am trying to use the CURRI interface to change the Calling Name of a caller.
the problem that I am facing is that CUCM doesn't connect to the application server.
in log: |AppInfo |HttpManager - received routing req transactionID(16777229) for ECC profile [b26ca2f1-f7f2-6122-a3f0-ead0e3891d16], find handler in INACTIVE or with INVALID URI, send routing rej
I don't see any traffic going or coming to/from the http server...
--------------------------------------------------------------------------------------------
What is the URI you configured in the ECCP Profile?
--------------------------------------------------------------------------------------------
http://10.10.1.116/
--------------------------------------------------------------------------------------------
I have seen strangeness at times with getting the URI to trigger correctly in a couple of cases (and some of this is dependent upon the version of Unified CM). There's a couple of things I do to try and make sure I don't run into problems.
First is how you name the URI. Keep it simple, and add the port, even if it's the standard port:
“http://10.10.1.116:80/routingrequest”
Second is, there are some defects in pre-10.x versions of Unified CM that if you change the URI on an existing ECCP, the system fails to reload the updated settings. You can work around this in two ways. One is to create a new ECCP with the updated information and then change the trigger point to use the updated ECCP (if you have a lot of trigger points this doesn't work well). Two is to 'restart' the Call Manager service on Unified CM. You shouldn't have to reboot the entire server, just restart the service.
--------------------------------------------------------------------------------------------
I changed the URI per your example with port and path and it works.
Comments
0 comments
Please sign in to leave a comment.