10-16-2012 01:46 AM - edited 03-16-2019 01:42 PM
Hi everyone,
I've configure the Mobile Connect feature on a CUCM 8.6 and have a question regarding this particular case :
User B is logged on an IP Phone (EM) and has Mobile Connect activated.
I would like to know if this is normal behaviour and if you have any idea to avoid that the call to be sent to the user's mobile provider voicemail and continue to ring on the IP phone and then fwd to his Unity mailbox.
Thank you
James
Solved! Go to Solution.
10-16-2012 03:35 AM
This is normal behavior. If CUCM sees the remote destination call leg transition to a connected state after the Answer Too Soon timer but before the Answer Too Late timer it believes the user has answered the call. There is no way to tell whether it was the user or the carrier's voicemail that answered unfortunately.
CUCM 9.0 added a new option on the Remote Destination Policy called SNR Voicemail Policy. There are two settings: Timer Control and User Control. Timer control is the existing behavior; if the call is answered within the timer window the call is connected through. Timer Control is new and requires the user to press a DTMF digit to accept the call after answering it. Since carrier voicemail can't press DTMF digits the call would not be considered answered if the user pressed ignore.
In my case, when remote destination (Mobile Phone) refeuses a call, IP phone keeps ringing.
Not all cell phones take the same action when you ignore/refuse a call. Some simply treat that as a request to be silent while others actually forward the call to voicemail at that point. Those cell phones that continue to alert silently would allow the IP Phone to continue ringing until the CFNA timer expires.
Please remember to rate helpful responses and identify helpful or correct answers.
10-16-2012 03:20 AM
Hi James.
I've configured mobile connect on my CUCM cluster too.
In my case, when remote destination (Mobile Phone) refeuses a call, IP phone keeps ringing.
Can you post a brief your config?
HTH
Regards
Carlo
10-16-2012 03:35 AM
This is normal behavior. If CUCM sees the remote destination call leg transition to a connected state after the Answer Too Soon timer but before the Answer Too Late timer it believes the user has answered the call. There is no way to tell whether it was the user or the carrier's voicemail that answered unfortunately.
CUCM 9.0 added a new option on the Remote Destination Policy called SNR Voicemail Policy. There are two settings: Timer Control and User Control. Timer control is the existing behavior; if the call is answered within the timer window the call is connected through. Timer Control is new and requires the user to press a DTMF digit to accept the call after answering it. Since carrier voicemail can't press DTMF digits the call would not be considered answered if the user pressed ignore.
In my case, when remote destination (Mobile Phone) refeuses a call, IP phone keeps ringing.
Not all cell phones take the same action when you ignore/refuse a call. Some simply treat that as a request to be silent while others actually forward the call to voicemail at that point. Those cell phones that continue to alert silently would allow the IP Phone to continue ringing until the CFNA timer expires.
Please remember to rate helpful responses and identify helpful or correct answers.
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