soft console. Night service / coverage path query

[ph0neman]

I have a S8700 on the main site running CM rls4. On the remote site I have an LSP. Both of these sites have their own attendants. And must not share calls ! The remote site has its own PRI and the attendant on the remote site must take calls on this PRI only.

I set up two VDN, each with their own vectors. Each queuing calls to the sepearate Attendants. The problem is that when the attendant on the remote site goes in to night service that the calls still come through to her. Night service has now been negated.

Can I set up a coverage path for an attendant ? Or is my method wrong ? How else could i have sepearted the calls from the attnendant.

thanks,
Irish Avaya

 

[imdue]

Tenant partitioning. Are you using that?

 

[ph0neman]

imdue. No i'm not. Is Tenant partitioning not like creating sepearte databases on the system. Will I then have to add all the phones on the remote site in to the second partition that I create ?

thanks for the prompt reply.
Irish Avaya

 

[imdue]

Yes. We have a similar setup where an S8300 is an LSP off of the main site w/an S8710. The S8300 is site 4 and the primary local is site 1 - create a tenant for your secondary site and set all of the users and console w/that tenant #. The S8300 was recently given a console to aid w/crisis alert (long story). The consoles do not receive calls for each other's site. Only issue we have had so far is the console in tenant #1 is also receiving the crisis alerts from tenant #4. Supposedly it should not do that. Hunt groups in that partition will have to be #'d w/the appropriate tenant # also. Originally we were using a vector there before the console was installed, now we do not....created an LDN instead for the main # - all works fine.

 

[ph0neman]

Thanks again for the prompt and relevant reply !!

Last question ? do the trunks etc on the remote site have to be added to that Tenant Partition ? will that then allow both Attendants to have their own Night service numbers and have you set it so that users on both sites can dial 0 and contact their relevant attendant ?

Was it much work ?

thanks again
Irish Avaya

 

[imdue]

One other note-ours is an Enterprise setup. Yes, the remote site has it's own trunk group set up in their partition. Users at each site can call their own operator by dialing "0". I have a hunt group for each site for Night service (set up in each partition) that points to that site's voicemail. I did not set all of this up initially...a software specialist did...but I have learned a lot lately about it after dealing w/the console install. If you need to see some screen shots, I can send you those if you want to include your email address.