[cisco-voip] Unity Transferring to an external number

[Cristobal Priego]

you also want to make sure that the CSS assigned to the VM ports can reach
the route patterns

2011/6/17 Paul <asobihoudai at yahoo.com>

> For you to allow Unity Connection to transfer to certain numbers, you have
> to edit your restriction tables. E.g., if you want Unity Connection to be
> able to dial 123456789, you will have to add that number into your
> restriction tables explicitly. Oddly, even with the addition of an explicit
> number I had to make another System Call Handler to force Connection to
> transfer to my specified number. This specific number is then explicitly
> configured in CCM as a destination Connection can reach and send out the
> desired PSTN trunk unless the CSS you have configured for Connection will
> already send it out the right trunk group...it wasn't in my case hence the
> explicit route pattern.
>
> Hence, option N points towards another call handler of which its sole
> purpose is to just transfer to an external destination. It works but I'd
> rather do it from within one System Call Handler...oh well.
>
>
> ------------------------------
> *From:* "O'Brien, Neil" <nobrien at datapac.com>
>
> *To:* cisco-voip at puck.nether.net
> *Sent:* Friday, June 17, 2011 1:34 AM
>
> *Subject:* [cisco-voip] Unity Transferring to an external number
>
> Hi,
> I won't go into the whys but I have Unity Connection 8.5 and I need a call
> handler (an option 2 off an auto attendant) to transfer the call to an
> external number if option 2 is selected.  I continue to get "Sorry, this
> number did not answer"
> I've tried a few things that haven't worked:
>
>    - Under Caller Input of the main call handler, configure option 2 to
>    transfer to an alternate extension which I put in the external number
>    - Configure another call handler and configure the transfer rules
>    settings here to go to the external number and set option 2 to go to this
>    call handler.
>
> I didn't expect the above to work because the voicemail ports do not have a
> CSS that allows them to call external numbers.  So I confgured a translation
> pattern with a DN in the CSS that the voicemail ports are able to reach and
> translated it to the external number but it still doesn't work.  Thinking
> that the Call handler monitors it in some way (even though i've set it to
> release to switch) I set up a CTI Route Point with CFA to the external
> number and still the same problem.
> The CSS of the TP is allowed call the number and if  I dial the TP
> independent of the CH it works fine.
> I’ve already posted over at the Cisco Support Forum as well but not much
> joy there either.
> I’d appreciate some pointers if you can think of anything??
> Thanks,
> Neil
>
>
>
>
>
> _______________________________________________
> 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
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://puck.nether.net/pipermail/cisco-voip/attachments/20110617/e7b9269b/attachment.html>