08-09-2002 08:31 AM - edited 03-12-2019 08:17 PM
using unity 2.4, is there a fix for 5 digit extensions? any five digit extension or loginID cannot call another phone whose coverage path points to unity. when it tries to cover to VM, it bounces out and rings the attendant.
08-09-2002 10:59 AM
Not sure what the issue is here, but it's not Unity related... you might try the IP Telephony forum if you're talking about a CM forwarding issue or another. Unity has no restrictions on 5 digit IDs (in 2.4 you can run from 3 to 10 digits by default)
08-09-2002 11:27 AM
You mention the word coverage path which makes me think you are integrating Unity with an Avaya switch using dtmf integration, it is possible that when the call covers to VM, Unity is missing the first part of the dtmf packett, and the first digit it gets is a "0" which causes the call to be transfered to the operator.
I could go on but first confirm this is your integration, and then open the integration monitor on Unity to see what digits you are getting.
Discover and save your favorite ideas. Come back to expert answers, step-by-step guides, recent topics, and more.
New here? Get started with these tips. How to use Community New member guide