Splitting Attendant Consoles

[Lynx77]

Hi All,

We need to assign a group of attendants for specific extensions and routes.
We did that using LDN or Console Group in Multitenant feature.

The incoming calls are terminated to the correct console. However, each console can access any RDB when making outgoing calls. We are not able to use NCOS (no more alternatives are available - all the NCOS values are already used).
Currently, we managed this by letting some consoles use AC1+SPN and others use AC2+SPN and ths use the same NCOS/FRL options.

We tried multi-customer scenario. However, we could not make inter-customers calls.

Is there anyway to:

1 - Allow inter-customers calls?
2 - Apply the Route to Console Group policy on both incoming and outgoing calls?

Thanks.

 

[johnpoole]

rdb to tennant.. ld 93, allows or denies each tennant to each rdb.. ncos is not a workable option, tgar/targ can be used but ld 93 is cleaner..

to use targ/tgar assign targ 0 1 2 3 4 6 7, to one route, only users tgar 5 can use it (very old school)

john poole
bellsouth business
columbia,sc

 

[Lynx77]

Hi John,

Thanks for your reply.

I used RDB to tenant and it worked on normal extension.

I need to restrict Attendant Console access to a route. Consoles do not have Tenant but they belong to a Console Group which works fine on incoming calls i.e.:
Route X allowed to access Group 0 will ring only the consoles belonging to group 0.
However, consoles belonging to group 1 will also be able to make calls using the same route X although Route to Console group 1 is denied which will only affect incoming calls.

Hope the scenario is clearer now.
For normal extensions: Incoming and Outgoing calls are ok.
For Consoles: Incoming OK. We need to restrict consoles from making outbound calls using unauthorized routes (no more NCOS are available)

On the other hand, anyway to make calls between 2 customers without using PRI/DSC or any other physical connections ?? This will resolve our issue.

Thanks.