AnsweredAssumed Answered

ECCP does not connect to CURRI Web Server

Question asked by louisvandyk on Apr 8, 2016
Latest reply on Apr 19, 2016 by louisvandyk

Hi

 

I am running CUCM 11.0.  I've installed Centos 7 which is running Python 2.7 in order to run the samplePolicyApp.py I downloaded from the CURRI DevNet page.

 

I have created the External Call Control Profile, and for the Web Service I entered:   http://192.168.100.25:6162

 

Then I added this ECCP to a DN of a test user on CUCM.  I also added it to a Translation Pattern on CUCM.

 

When a call is placed to either, nothing is reported on the Python screen, and the call behaves according to the status of "Call Treatment on Failures".  In other words, it succeeds if I ALLOW, and it fails if select BLOCK.

 

On the Centos Server I am running the command:   python ./samplePolicyApp.py 192.168.100.25 6162 http

 

I get the resulting:

HTTP://HOST_NAME:PORT http :// 192.168.100.25 : 6162

Fri Apr  8 16:15:55 2016 HTTP CURRI Server Started - 192.168.100.25:6162

 

If I use a normal web browser to open the page I get the resulting:

This is a test.

You accessed path: /

 

So the Python side seems good.  On the Centos server I ran tcpdump.  I noticed that the CUCM *NEVER* connects to the Centos/Python server.

 

I created another ECCP and assigned that to the DN (while the Python server was running) but that made no difference.  Also, if I use lsof or netstat to view active connections, there are none except for my SSH session.

 

Where do I go from here?  And Thanks!

Outcomes