[cisco-voip] isdn channels full message

[Brian Meade]

More info-
https://supportforums.cisco.com/discussion/12204911/cucm-713-outbound-calls-multiple-gateways-using-route-list-route-group

On Tue, Jun 23, 2015 at 3:40 PM, Brian Meade <bmeade90 at vt.edu> wrote:

> Sorry, it sends unassigned/unallocated number when the dial-peers are down
> due to that so you have to change the keep routing on
> unassigned/unallocated number service parameter or run that command on the
> gateway,
>
> On Tue, Jun 23, 2015 at 3:34 PM, Brian Meade <bmeade90 at vt.edu> wrote:
>
>> Ryan,
>>
>> It's possible to do it but sometimes requires some reconfiguration.
>> H.323 gateways typically send back a user busy I believe when all of the
>> dial-peers run out of ports.  So you need to change CallManager service
>> parameter to keep routing on user busy or configure "no dial-peer
>> outbound status-check pots" on the gateway.
>>
>> Brian
>>
>> On Tue, Jun 23, 2015 at 3:27 PM, Ryan Huff <ryanhuff at outlook.com> wrote:
>>
>>> Wes,
>>>
>>> I tried something like this before with h.323 (full disclosure, it was
>>> ccm 8.0.3) and the behavior I experienced was that on the busy out of the
>>> first gateway (the primary), call manager did not the recall the call and
>>> try the next member in the group, it just busied on the first h.323 gateway
>>> (using top-down). Sort of like a release to switch rather than a supervised
>>> transfer.
>>>
>>> Do you think I had something mis-configured (timers ... etc) or
>>> something?
>>>
>>> I want to lab this up tonight, cause it will solve a problem of mine if
>>> it works :). Thanks!
>>>
>>> Thanks,
>>>
>>> Ryan (the forever student)
>>>
>>>
>>> -------- Original Message --------
>>> From: "Wes Sisk (wsisk)" <wsisk at cisco.com>
>>> Sent: Tuesday, June 23, 2015 11:47 AM
>>> To: abbas wali <abbaseo at gmail.com>
>>> Subject: Re: [cisco-voip] isdn channels full message
>>> CC: cisco-voip at puck.nether.net,Ryan Huff <ryanhuff at outlook.com>
>>>
>>> not tested, theoretically sound, YMMV. No guarantees, warranties, etc.
>>>
>>>  use a route group with top down hunting. your real gateways are the
>>> first entries.
>>> last entry is an h323 gateway. the destination IP is the local CM. This
>>> is essentially a loopback going out/in the IP interface.
>>> Use the CSS for that gateway to match translation patterns that
>>> overwrite the called party number to be the DN that forwards to Voicemail.
>>> Also use a different egress CSS for the TP.
>>> Setup your VMail system to answer based on that redirect number and
>>> deliver whatever message you want.
>>>
>>>  -w
>>>
>>>   On Jun 23, 2015, at 9:15 AM, Ryan Huff <ryanhuff at outlook.com> wrote:
>>>
>>>  Ahhhhh okay ....
>>>
>>> Well, an easy way would be MGCP Gateways and route groups (and just mux
>>> the timers to get quick failover). With H.323 however, that is a bit more
>>> tricky because CCM knows nothing about the gateway or PRI's state, so if
>>> you could do anything, it would have to be in the gateway.
>>>
>>> You can use hunt groups in an h.323 IOS gateway to do this with multiple
>>> PRI's; you may be able to do this by having one of the peers in the hunt
>>> group kick the call back into CCM to a destination that forwards to
>>> voicemail.
>>>
>>> Thanks,
>>>
>>> Ryan
>>>
>>>
>>>  ------------------------------
>>> From: abbaseo at gmail.com
>>> To: ryanhuff at outlook.com; cisco-voip at puck.nether.net
>>> Subject: RE: [cisco-voip] isdn channels full message
>>> Date: Tue, 23 Jun 2015 13:55:42 +0100
>>>
>>>  Hi just to add it to.
>>>
>>>
>>> We need it only for the outbound direction.
>>>
>>>
>>>  *From:* Ryan Huff [mailto:ryanhuff at outlook.com <ryanhuff at outlook.com>]
>>> *Sent:* 23 June 2015 13:51
>>> *To:* abbas wali; cisco-voip at puck.nether.net
>>> *Subject:* RE: [cisco-voip] isdn channels full message
>>>
>>>
>>>  I don't believe so, at least not on the CPE side.
>>>
>>> The presence of all channels being busy would indicate that there aren't
>>> any channels available for the next call (or the next call after all
>>> channels are busy) to ring through the PRI for you to forward to voicemail,
>>> even if there were a way for you to act upon channel utilization.
>>>
>>> If you are trying to use conditional routing based on full PRI capacity,
>>> you'd probably have to work with your carrier and see if they can forward
>>> upon full channel utilization (they have the capability to do that, but
>>> will they is the question). However, they wouldn't be able to forward
>>> through the utilized PRI in that scenario, they'd have to forward to an
>>> alternate number.
>>>
>>> Thanks,
>>>
>>> Ryan
>>>  ------------------------------
>>>  From: abbaseo at gmail.com
>>> To: cisco-voip at puck.nether.net
>>> Date: Tue, 23 Jun 2015 11:38:55 +0100
>>> Subject: [cisco-voip] isdn channels full message
>>>  Hi  folks,
>>>
>>>
>>> CUCM 9 and H323 gateways with ISDN channels to PSTN. We want to redirect
>>> to VM when all the channels are full.
>>>
>>>
>>> Can CUCM do it or Dpeer?
>>>
>>>
>>> Thanks
>>>
>>>
>>>
>>> _______________________________________________ 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
>>>
>>>
>>> _______________________________________________
>>> 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/20150623/de86876b/attachment.html>