Ill give that a try.
Is it even possible for a no response treatment to be other than the attendant? Like an announcement service or menu service. In the documentation, it always has the attendant out as the no response option?
Whats starnge is, I will point the # key option to the same destination and it will work when I select the # key, but if I do no response I get the "transfering to an attendant" greeting. Even thou its the same destination as teh # key option.
While using the Thru-Dial block in Application Builder, I am unable to make any changes to the No Response field.
I can make the change, and save them. But no matter what change I make it always gives me the same treatment..
"Transferring to an attendant...one moment please"
I have tried to...
Having problems accessing satellite location mailboxes from the primary Call Pilot location. Can retrieve messages local from the satellite location but when physically at the prime location, it states the mailbox does not exist.
Same problem here. Configured the satellite location, the satellite ACDN's and updated the SDN table on the messaging server. Confirmed loc codes work between the sites.
However no message waiting indicator and the call pilot announces the mailbox user with the location code leading the user...
This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
By continuing to use this site, you are consenting to our use of cookies.