Cisco Unified Routing Rules XML Interface

« Back to Routing Rules API Questions

Could not receive Call Routing Request on .NET Web Application ?

Combination View Flat View Tree View
Threads [ Previous | Next ]
Hi,
 
I¿m just trying to play with External Call Control Profile (ECCP).
I set up an ECCP that points a .NET Web application running on IIS (HTTP / 80) and then assigned it to a Translation Pattern.
I think this application meets the prerequisites:
·         HTTP 1.1 for persistent connection
·         Support thread pool for multiple persistent connections
·         Support HTTP KeepAlive header
·         Support HTTP POST
·         Ready to parse XACML Call Routing request and push response
However, no request arrives at destination¿
 
First I installed Wireshark on my Web server and saw that nothing came from CUCM.
Then I picked up SDI and SDL traces from CUCM. Below what I found:
>> ConnectionFailureToPDP - A connection request from Unified CM to the policy decision point failed Policy Decision Point:http://10.0.50.5/TestCURRI/Default.aspx <strong style="mso-bidi-font-weight: normal;"><em style="mso-bidi-font-style: normal;">The cause of the connection failure:Invalid URI is specified in the External Call Control profile
 
So I tried several URL syntaxes that give me all the same failed result:
·         http://10.0.50.5/TestCURRI/Default.aspx
·         http://10.0.50.5:80/TestCURRI/Default.aspx
·         http://10.0.50.5/TestCURRI/
·         http://10.0.50.5:80/TestCURRI/
·         http://10.0.50.5/TestCURRI
·         http://10.0.50.5:80/TestCURRI
·         ¿
 
Does anyone have an idea to solve this problem?
 
Regards

had the same problem...
 
1) try changing the IP of your webserver to one without a 0
2) wait for next update-release where the issue should be fixed

Hi Julien,

Stefan's comment is right, but let me provide a little more detail.

There's a bit of IP-address screening code in the release that is overzealous about checking the validity of IP addresses. (This is already fixed in development branches and should be a part of subsequent maintenance releases.)

If the second, third, or fourth octet in the Web Server is 0, CUCM considers the address invalid (i.e., 10.0.x.x, 10.x.0.x, 10.x.x.0). Best we can tell, this was a flawed attempt to screen out network addresses and, unfortunately, it slipped through QA since the servers they tested against didn't happen to have zeroes in the appropriate positions.

Is it possible for you to renumber the IP address of your PDP?

Chris Pearce
Cisco Distinguished Engineer

Hi Chris & Stefan,

Thank you both for your reply.
It works by changing the WebServer IP address in 10.10.10.35 (instead of 10.0.50.5).
I get the "keep-alive" and my first "HTML/XML POST" from CUCM.
Now I have to parse this Call Routing Request and return a well formatted response.

Bye.

Hi
 
I addedd a  .Net based Web Service i.e. (Service.asmx) but it is not getting invoked on my web server and also my web server address does not contain '0' in its IP Address.
 
But when I tried with Default.aspx page it is getting invoked but i m always receiving a "Head" request if i get a call on the configured Translation Pattern.
 
Please reply for my both of the queries.
 
 
Regards
 

Hi,

The fact that you are getting a HEAD request implies that UCM is able to forge the connection to your server. Cisco UC Manager uses periodic HEAD requests as a keep-alive mechanism to ensure that the server is present. Could the HEAD request be confusing your server?

Chris Pearce
Cisco Distinguished Engineer

Chris,

Do you have the Bug ID for this issue?