[cisco-voip] Sending Digits from a Script to a Unity Mailbox

[Pat Hayes]

Here are a few potentially useful Unity bits, that might have been
helpful 2 hours ago and/or if Jim hadn't already found a way to do
everything from a script :-)

1. The transfer prompt from Unity is "please wait while I transfer
your call". If you want to get rid of that, there is a checkbox on the
call transfer rule page for whatever call handler or subscriber you
are transferring to (something like 'do not play prompt while
transferring'). This hasn't always been there, it was added somewhere
around 4.2(1) or 5.0(1).

2. Rather than finding a way to send digits to Unity after connecting,
you can just use a call routing rule. Set up a dummy dn in CUCM and
CFA it to Unity. Add a forwarding routing rule that matches that dummy
DN and has an action of "Attempt transfer to" and point it to your
call handler/subscriber. Now any call sent to that DN will immediately
follow the transfer rule for that object.

That's a bit of a hack, though. Handling everything from the script is
a lot cleaner.

On Thu, Oct 1, 2009 at 3:04 PM, Wes Sisk <wsisk at cisco.com> wrote:
> Can you give the complete text of the message? I suspect that message is
> Unity's native message.  In that case we'd need to get the attention of some
> unity folks on the list.
>
> If it is that, is there any option in the consult trasnfer step to delay
> completion of transfer?  The age old trick is to use commas for delay but
> your scripting environent or script interpreter may not implement that.
>
> /Wes
>
> On Thursday, October 01, 2009 2:53:51 PM, Jim Reed <jreed at swiftnews.com>
> wrote:
>
> Well, crap, that was easy.  Thanks, Wes, for putting me on the right track.
>  Used the call consult transfer.  Put the Unity mailbox extension in the
> Destination field and the desired Caller Input digit in the Output Digits
> field and it works like a champ.  Now for the follow-up question — worth 100
> points (for what I don’t know).  Any way to suppress the annoying
> “Transferring Call” message as it transfers the call from IPCC to Unity?
>
> Again, Thanks Wes for heading me in the right direction.
> --
> Jim Reed
> Technology Wrangler
> Swift Communications, Inc.
> 970-683-5646 (Direct)
> 775-772-7666 (Cell)
>
> Quando omni flunkus moritati
> "When all else fails, play dead"
>         Red Green - President: Possum Lodge
>         (Thanks for this one, Bill W.)
>
>
>
> On 10/1/09 11:36 AM, "Jim Reed" <jreed at swiftnews.com> wrote:
>
> I want to transfer callers to an outside line that requires a long distance
> code.  The long distance code requires a two (2) or three (2) second pause
> between the dialing of the number and the request for the long distance
> code.  I can do this in Unity 5.x with the Alternate Contact Number option
> under Caller Input.  Something that neither Call Manager or IPCC seem to be
> able to do.  For instance, I can put in the digit string
> 917757727666,,,9009# for the Alternate Contact Number and assign it to Key
> 1.  I have tested this manually and it works every time.  I would like this
> to be transparent to the calling party and would be able to use a single
> Unity mailbox for up to nine (9) or ten (10) different people and let the
> IPCC script decide which digit to pass to the mailbox based on the calling
> number coming into the script.  So, the flow would be something like this:
>
> Caller calls a DID or is transferred to that extension.
> Extension is set to call forward all to an IPCC route point
> Calling number is evaluated by IPCC in a series of IF statements to
> determine which digit to pass to Unity
> Caller is transferred to Unity based on the evaluation of the IF statements
> IPCC then sends the correct digit for Caller Input which then forwards the
> caller to the appropriate external number
>
> Let me know if additional info is needed.  Thank You...
> --
> Jim Reed
> Technology Wrangler
> Swift Communications, Inc.
> 970-683-5646 (Direct)
> 775-772-7666 (Cell)
>
> Quando omni flunkus moritati
> "When all else fails, play dead"
>         Red Green - President: Possum Lodge
>         (Thanks for this one, Bill W.)
>
>
>
> On 10/1/09 11:27 AM, "Wes Sisk" <wsisk at cisco.com> wrote:
>
> How about a little more insight on what products, call flows, and functions
> you are using?
>
> In general:
>
> Consult Transfer:
> answer inbound call
> initiate transfer
> (once this call goes into connected state it is technically possible to pass
> DTMF to the destination)
> complete transfer
> at this point the transferring party is completely out the call flow and
> cannot pass DTMF to anyone
>
> Blind Transfer:
> Answer inbound call
> initiate transfer and specify destination
> In this scenario there is no opportunity to pass DTMF to the destination
>
> /Wes
>
> On Thursday, October 01, 2009 12:33:40 PM, Jim Reed <jreed at swiftnews.com>
> <mailto:jreed at swiftnews.com>  wrote:
>
> Sending Digits from a Script to a Unity Mailbox Okay, all you geniuses out
> there -- and you know who you are -- here is what I am wondering if one can
> do.
>
> I know I can transfer a caller from a script directly to a Unity mailbox,
> call handler, etc.  What I would like to do is wait two (2) seconds and send
> a digit to that mailbox, call handler, etc., from the script just as if the
> caller had pressed a digit for caller input.  Can this be done or if once
> the initial transfer is done is there no longer any communication possible
> between the script and Unity?
>
> Thank You...
>  --
> Jim Reed
> Technology Wrangler
> Swift Communications, Inc.
> 970-683-5646 (Direct)
> 775-772-7666 (Cell)
>
> Quando omni flunkus moritati
> "When all else fails, play dead"
>         Red Green - President: Possum Lodge
>         (Thanks for this one, Bill W.)
>
>
>
>
>
> _______________________________________________
> cisco-voip mailing list
> cisco-voip at puck.nether.net
> https://puck.nether.net/mailman/listinfo/cisco-voip
>
>
>
>
>
>
>
>
>
> _______________________________________________
> cisco-voip mailing list
> cisco-voip at puck.nether.net
> https://puck.nether.net/mailman/listinfo/cisco-voip
>
>