Please login or register to access secure site features.

Note: By continuing to use DevConnect Program Services you agree to our latest Registered Member Terms.

Sign in using DevConnect ID

Forgot password?

Trouble logging in?

Submit a ticket for Registration Support.

I have an SSO ID

?
sign in

Don't have a DevConnect or SSO ID ?

Create a DevConnect account or join the program.

register now
^
New DevConnect members must have forum permissions in order to post messages.
If the Reply and New Post buttons are not available to you, please request access using a General Support request ticket.
Forum Index » DMCC APIs » Call Barring   XML
 
Author Message
AbdulKA



Joined: 06/11/2013 06:10:44
Messages: 35
Offline

Hello,

we have a call recording application which uses Multi registration mode of recording with DMCC. we have a specific requirement in
which we need to block the monitored extension from making any more outgoing call . we require to block the extension
automatically or manually the DMCC / TSAPI monitored extension . Is it possible to bar the extension from making any more
outgoing call using any features in DMCC or TSAPI?

Thanks and Regards
Abdul Rasheed
MartinFlynn



Joined: 30/11/2009 05:00:18
Messages: 1792
Offline

I don't think there is a way bar an outgoing call before the far-end receives it. However, it is possible to stop a call just as the far-end begins to ring.

I think the way to do this would be to place a call control monitor on the station. Then, when the application receives a Delivered event it can Clear the Call if the call is outgoing.

One possible way to test that a call is outgoing is:

1. Is it originated on the monitored station? If the Delivered event was preceded by a Service Initiate event then it was originated by the station. Alternatively, you could use the Calling number in the Delivered event itself.

2. Is the call going over a trunk? For trunk calls, the Delivered event will include values in the Trunk Group and Trunk Member fields.

Martin
AbdulKA



Joined: 06/11/2013 06:10:44
Messages: 35
Offline

Thanks Martin.

we are ok to block the call after the far end rings. So this method seems to be fine. However it will consume 1 TSAPI license per monitored station. So i would like to know also if there is any other way to block programatically the outgoing calls from a particular extension? For example any configuration webservice API which can bring in some Class of restriction for the particular monitored extensions which will block the outgoing calls from that extension .

we were able to do that for Avaya IP office by changing the user to a new user rights group which bars the outgoing calls.


Thanks and Regards
Abdul Rasheed
MartinFlynn



Joined: 30/11/2009 05:00:18
Messages: 1792
Offline

The SMS API allows an application to change the configuration of Communication Manager. You should be able to use it to change the Class of Restriction (COR) of the station to one which does not allow outgoing calls.

It looks like the relevant COR parameter may be "Calling Party Restriction". Add a new COR which is the same as the normal station COR except this is set to, say, "Outgoing". You can then use SMS to change that station's COR.

A couple of things to note though:

1. This may not be the correct parameter to use but the description looks like it may be. There are other COR parameters which may be more suitable.
2. I am not sure if changing the COR will take effect immediately or if the station has to unregister/register first.

You will need to test these for yourself. You should find "Avaya Aura Communication Manager Screen Reference" useful.

Martin
AbdulKA



Joined: 06/11/2013 06:10:44
Messages: 35
Offline

Thanks Martin. Does the SMS API consume any licenses from AES ?

Best Regards
Abdul Rasheed
MartinFlynn



Joined: 30/11/2009 05:00:18
Messages: 1792
Offline

No licenses are needed for SMS. You can get more information on SMS at:
https://www.devconnectprogram.com/site/global/products_resources/avaya_aura_application_enablement_services/interfaces/sms_web_service/overview/index.gsp

Martin
JohnBiggs



Joined: 20/06/2005 14:06:52
Messages: 883
Location: Thornton, CO
Offline

A change to a station's COR will take effect on the next call operation (in this case the next call they place).
Note that a COR is assigned to a group of stations, so what you want to do is change the station's COR from A to B, where the only difference between core A and B is the setting that restricts outbound calls. When you want to allow outbound calls, change it from B back to A.

Note there is a difference between outbound TRUNK calls and outbound calls to internal stations. Depending on what level restriction you want different settings are necessary in the station's COR.
[WWW]
AbdulKA



Joined: 06/11/2013 06:10:44
Messages: 35
Offline

Thanks a lot John and Martin for your support.

Best Regards
Rasheed
chukiatdenkongpon



Joined: 07/11/2013 10:46:34
Messages: 93
Offline

Hi

I have questions about " it is possible to stop a call just as the far-end begins to ring. ".
- Do we have to use JTAPI API or DMCC API?
- Which method to stop a call?
Please advice

Best Regards,
Chukiat D.
JohnBiggs



Joined: 20/06/2005 14:06:52
Messages: 883
Location: Thornton, CO
Offline

It is best to open a new thread for a new topic. That way all users who monitor the forum see it. Posting into an existing thread gets the attention of only those who are monitoring the thread (far smaller group).

I can't answer without more information.

Are you monitoring the originating station and wish to kill a call it originated after it is placed, or are you monitoring the destination device and wish to reject a call it is receiving? you can do the first but not the second 'cleanly'. To clear the call from the destination you have to answer it and then drop it which you may not want to do.

How exacting do you want to be about knowing the far end rang at all? Is that a requirement?
[WWW]
 
 
Go to: