Recently upgraded a 406V2 to 5.0.
They have no Twinning/Mobility licenses but they have multiple virtual users who's extensions are simply call forwarded unconditionally to their cell phones.
Seemed to work fine with 3.2(69).
Now no matter how the call is originated, DID, internal or transfer there is no audible ringback from the CO.
There is only silence until the cell phone user answers or
their mobile voicemail answers.
Settings and attempted fixes.
-Turned off MOH
-Used multiple destination numbers to eliminate carriers.
-No Answer time is set for 30.
-Users VM disabled
-If you call cell # directly from IPO the ringback tone is present.
Interesting enough if I turn on User\Announcements using only 1st announcement and Post Announcement Tone set to ringing it works great except the default 1st queing announcement is not approriate. Ironicly if I set up Queued start point for the user in VM pro it will not work.
I know someone will be unable to refrain from telling me that this is what Mobility Licenses are for. But please don't waste you're time. The customer has already been informed and quoted even though they have a valid point. "If it worked before the upgrade it should work now"
Please reply if you have run into this.
Thanks
Mike
They have no Twinning/Mobility licenses but they have multiple virtual users who's extensions are simply call forwarded unconditionally to their cell phones.
Seemed to work fine with 3.2(69).
Now no matter how the call is originated, DID, internal or transfer there is no audible ringback from the CO.
There is only silence until the cell phone user answers or
their mobile voicemail answers.
Settings and attempted fixes.
-Turned off MOH
-Used multiple destination numbers to eliminate carriers.
-No Answer time is set for 30.
-Users VM disabled
-If you call cell # directly from IPO the ringback tone is present.
Interesting enough if I turn on User\Announcements using only 1st announcement and Post Announcement Tone set to ringing it works great except the default 1st queing announcement is not approriate. Ironicly if I set up Queued start point for the user in VM pro it will not work.
I know someone will be unable to refrain from telling me that this is what Mobility Licenses are for. But please don't waste you're time. The customer has already been informed and quoted even though they have a valid point. "If it worked before the upgrade it should work now"
Please reply if you have run into this.
Thanks
Mike