Scenario is this: DID extension dialed, goes to Mod Msg when busy or no answer. Caller App is employed to send calls to a VDN when called presses '0'. Call will route through the VDN and vector to another desk phone and will ring that phone and can be answered.
Problem: if that zero-out phone is busy, or on cover, the caller who pressed zero from the origination mailbox will experience simply RNA. It will not cover to that second phone's mailbox.
I read in this forum the issue in 2006 that Ken posted in response to someone: (pasted here for reference)
Currently, if calls are routed from a Vector to the QSIG link(s) connected to the MAS, the call will not pass the VDN as the called party ID. Applications requiring calls that are routed from Vectors to mailboxes on the MAS can be configured so as to route calls to phantom extensions (X-ports) configured to call-cover all-calls to the MAS hunt group.
But, I also understand that the above statement is no longer an issue with a patch and with subsequent loads.
Question: Is there a system limitation that prohibits a call to cover, route, then cover?
Desperate in the Desert....
Problem: if that zero-out phone is busy, or on cover, the caller who pressed zero from the origination mailbox will experience simply RNA. It will not cover to that second phone's mailbox.
I read in this forum the issue in 2006 that Ken posted in response to someone: (pasted here for reference)
Currently, if calls are routed from a Vector to the QSIG link(s) connected to the MAS, the call will not pass the VDN as the called party ID. Applications requiring calls that are routed from Vectors to mailboxes on the MAS can be configured so as to route calls to phantom extensions (X-ports) configured to call-cover all-calls to the MAS hunt group.
But, I also understand that the above statement is no longer an issue with a patch and with subsequent loads.
Question: Is there a system limitation that prohibits a call to cover, route, then cover?
Desperate in the Desert....