01-03-2012 01:46 PM - edited 03-19-2019 04:11 AM
I am having troubles get the following scenario to work:
Cell Phone: 555-555-5555 cfw busy and cfw no answer to Unity Connection VM Pilot
Desk Phone: 1234 with Unity Connection mailbox and Alternate Extension listed as 555-555-5555
When the cell phone cfw kicks in it hits Unit Connection and you get "Hello, Cisco Unity Connection Voicemail System...." you are NOT forwarded to the correct mailbox for the alternate extension.
What is the proper way to configure this?
I want the cell phone and the desk phone to share the same mailbox, but not using Single Number Reach. Either number should be able to be called individually and when cfw condition kicks in on the cell phone, it should go to the correct Unity Connection mailbox.
Any help would be appreciated.
Thanks,
Nate
01-03-2012 01:59 PM
Check debug isdn q931.
If telco doesn't send the calls as a forwaded one, and that is no relayed to Unity, Unity cannot know the condition and activate VM.
01-04-2012 06:29 AM
Hi Nate,
I would try this Tool from the excellent suite of Unity Tools to have a look
at the call flow to see what # is being passed to Unity Connection on the
forwarded call from 555-555-5555. You may need to set up a Forwarded Call
Routing Rule in Connection
http://www.ciscounitytools.com/Applications/CxN/PortStatusMonitorCUC7x/PortStatusMonitorCUC7x.html
Cheers!
Rob
Please remember to tag your threads and help support "Teachers without Borders"
https://supportforums.cisco.com/community/netpro/idea-center/communityhelpingcommunity
01-04-2012 12:02 PM
I want cfw busy and cfw no answer from cell to be answered by correct unity connection mailbox (shared with desk DN)
Remote Port Status Monitor Output:
01:38:30, New Call, CalledId=2950, RedirectingId=, Origin=16, Reason=1, CallGuid=C2E8E7D7DD6B4AF0A41F00417BB6E5F1, CallerName=, LastRedirectingId=, LastRedirectingReason=1024, PortDisplayName=CM_CUCMBE-1-001,[Origin=Unknown],[Reason=Direct]
01:38:31, AttemptSignIn
01:38:31, State - AttemptSignIn.cde!Dummy
01:38:31, Event is [NULL]
01:38:31, PHTransfer
01:38:31, State - PHTransfer.cde!LoadInfo
01:38:31, Event is [TrueEvent]
01:38:31, PHGreeting
01:38:31, State - PHGreeting.cde!PlayGreeting
01:38:31, Call answered if needed
01:38:31, Playing greeting for Call Handler: Opening Greeting
01:38:36, Event is [HangupEvent]
01:38:36, State - PHGreeting.cde!DoHangup
01:38:36, Event is [HangupEvent]
01:38:36, Idle
Also Included RTMT Screen shot:
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