[cisco-voip] DID for Unity Pilot?

[Christopher M. Bomba]

What do you do if the incoming DID digits are already in there as the Unity Pilot #.  There is no CTI route point.  There is no CFA to VM.  It just goes to VM.  I watch the call on call viewer and it shows the right digits being dialed.  Below is the output from a PortStatusMonitor capture.


"1","2007/04/09","17:30:31","Appl","attemptsignin"
"1","2007/04/09","17:30:32","Conv","State - d:\commserver\localize\scripts\attemptsignin.cde!Dummy"
"1","2007/04/09","17:30:32","Conv","Event NULL"
"1","2007/04/09","17:30:32","Appl","phtransfer"
"1","2007/04/09","17:30:32","Conv","State - d:\commserver\localize\scripts\phtransfer.cde!LoadInfo"
"1","2007/04/09","17:30:32","Conv","Event is [TrueEvent]"
"1","2007/04/09","17:30:32","Appl","phgreeting"
"1","2007/04/09","17:30:32","Conv","State - d:\commserver\localize\scripts\phgreeting.cde!Root"
"1","2007/04/09","17:30:32","Conv","Event NULL"
"1","2007/04/09","17:30:32","Conv","State - d:\commserver\localize\scripts\phgreeting.cde!PlayGreeting"
"1","2007/04/09","17:30:32","Conv","Call answered if needed"
"1","2007/04/09","17:30:32","Disp","Playing greeting for Call Handler:  Opening Greeting"
"1","2007/04/09","17:30:36","Conv","Event is [HangupEvent]"
"1","2007/04/09","17:30:36","Conv","State - d:\commserver\localize\scripts\phgreeting.cde!DoHangup"
"1","2007/04/09","17:30:36","Conv","Event is [HangupEvent]"
"1","2007/04/09","17:30:36","Appl","Idle"
"1","2007/04/09","17:30:36","Conv","Idle"
"1","2007/04/09","17:30:36","Disp","Idle"



-----Original Message-----
From: "Matt Slaga \(US\)" <Matt.Slaga at us.didata.com>
Sent: Mon, April 9, 2007 9:34 am
To: Simon, Bill <bills at tns.its.psu.edu>, cbomba at s4nets.com
Cc: cisco-voip at puck.nether.net
Subject: RE: [cisco-voip] DID for Unity Pilot?

Create a CTI route point with the DID incoming digits.  Have the CTI RP
CFA to VM.

In Unity, create a "Forwarded Calls" routing rule.  Set the "forwarded
number" to the CTI RP DN.  Select the "Attempt to sign-in" as the
default handler.

Note- When you create a new routing rule, all calls will go to it until
you enter the forwarded number. 



-----Original Message-----
From: cisco-voip-bounces at puck.nether.net
[mailto:cisco-voip-bounces at puck.nether.net] On Behalf Of Simon, Bill
Sent: Friday, April 06, 2007 4:37 PM
To: cbomba at s4nets.com
Cc: cisco-voip at puck.nether.net
Subject: Re: [cisco-voip] DID for Unity Pilot?

We accomplish this for external users by setting up their external # 
(caller ID) as an alternate extension.  Unity sees the alternate 
extension calling in and instead of playing the AA goes to the sign-in.

Christopher M. Bomba wrote:
> I configured a DID for the Unity Pilot so the same number internally
will be the same number people call externally to retrieve their voice
mail.  I want to make it so that when an external user calls the DID it
goes into the Sign-In.  Of course internally it works fine.
> 
> I tried to set the number up as a call handler and use a blank
greeting with it transfering to "Attempt Sign-In" after greeting.
Doesn't work.  That senario works with another number but not the same
number as the pilot number.  
> 
> I then tried to create a direct call rule for the number and said
"Both" for call type and then send that to "Attempt Sign-In" and
"Sign-In" and neither worked.
> 
> Is anyone out there using a DID for the Unity Pilot number and also
using that same DID to have users call into voicemail and hit the
"Sign-In" prompt?
_______________________________________________
cisco-voip mailing list
cisco-voip at puck.nether.net
https://puck.nether.net/mailman/listinfo/cisco-voip
-----------------------------------------
Disclaimer:

This e-mail communication and any attachments may contain
confidential and privileged information and is for use by the
designated addressee(s) named above only.  If you are not the
intended addressee, you are hereby notified that you have received
this communication in error and that any use or reproduction of
this email or its contents is strictly prohibited and may be
unlawful.  If you have received this communication in error, please
notify us immediately by replying to this message and deleting it
from your computer. Thank you.