If calls are leaving or entering CM via SIP trunks, then an EDP app can be written to do what you want. You'd use the CMApi (aka the EDP call and media control API) to intercept the call, query your database to find out how many credits they may have, then time the call and drop if they run out of credit. You can also play warning announcements on the call if they begin approaching their credit limit.

I'm afraid I can't answer that. Please raise a ticket through support.avaya.com.

I pointed you to the documentation that tells you how to map the DID. What other response are you waiting for?

Page 59 in the Collaboratory User Guide will show you where to modify the mapping of the DID number.

This guide is available from your in-lab web page at: http://10.130.240.77:8400

specifically:

http://10.130.240.77:8400/collaboratory_user_guide_3dot0.pdf

But, while you really need to work through support, I'll clear up a misconception. The number you report is an external one, not routable from within your Collaboratory. By default it gets mapped to an internal number that is routable. For your lab this number is 3002.

So, if you dial 3002 from any phone within the lab you will be connected to Scopia server and prompted to join a meeting for audio only.

DevConnect forums are not meant for reporting Collaboratory issues. Please open a ticket at support.avaya.com or send mail to your lab's single point of contact.

Worked with Bob directly. Problem was that project skeleton creates a calling-only service by default. Bob wanted a called service. The solution was to change the orig_ entries in the service's properties.xml file into term_ entries.