<div dir="ltr">Ryan,<div><br></div><div>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 "<span style="color:rgb(51,51,51);font-family:Arial,sans-serif;font-size:16px;line-height:20px">no dial-peer outbound status-check pots" on the gateway.</span></div><div><span style="color:rgb(51,51,51);font-family:Arial,sans-serif;font-size:16px;line-height:20px"><br></span></div><div><span style="color:rgb(51,51,51);font-family:Arial,sans-serif;font-size:16px;line-height:20px">Brian</span></div></div><div class="gmail_extra"><br><div class="gmail_quote">On Tue, Jun 23, 2015 at 3:27 PM, Ryan Huff <span dir="ltr"><<a href="mailto:ryanhuff@outlook.com" target="_blank">ryanhuff@outlook.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><p dir="ltr">Wes,</p>
<p dir="ltr">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.</p>
<p dir="ltr">Do you think I had something mis-configured (timers ... etc) or something?</p>
<p dir="ltr">I want to lab this up tonight, cause it will solve a problem of mine if it works :). Thanks!</p>
<p dir="ltr">Thanks,</p>
<p dir="ltr">Ryan (the forever student)</p><div class="HOEnZb"><div class="h5">
<br><br>-------- Original Message --------<br>From: "Wes Sisk (wsisk)" <<a href="mailto:wsisk@cisco.com" target="_blank">wsisk@cisco.com</a>><br>Sent: Tuesday, June 23, 2015 11:47 AM<br>To: abbas wali <<a href="mailto:abbaseo@gmail.com" target="_blank">abbaseo@gmail.com</a>><br>Subject: Re: [cisco-voip] isdn channels full message<br>CC: <a href="mailto:cisco-voip@puck.nether.net" target="_blank">cisco-voip@puck.nether.net</a>,Ryan Huff <<a href="mailto:ryanhuff@outlook.com" target="_blank">ryanhuff@outlook.com</a>><br><br>
not tested, theoretically sound, YMMV. No guarantees, warranties, etc.
<div><br>
</div>
<div>use a route group with top down hunting. your real gateways are the first entries.</div>
<div>last entry is an h323 gateway. the destination IP is the local CM. This is essentially a loopback going out/in the IP interface.</div>
<div>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.</div>
<div>Setup your VMail system to answer based on that redirect number and deliver whatever message you want.</div>
<div><br>
</div>
<div>-w</div>
<div><br>
</div>
<div>
<div>
<div>On Jun 23, 2015, at 9:15 AM, Ryan Huff <<a href="mailto:ryanhuff@outlook.com" target="_blank">ryanhuff@outlook.com</a>> wrote:</div>
<br>
<div>
<div style="font-size:12pt;font-family:Calibri;font-style:normal;font-variant:normal;font-weight:normal;letter-spacing:normal;line-height:normal;text-align:start;text-indent:0px;text-transform:none;white-space:normal;word-spacing:0px">
<div dir="ltr">Ahhhhh okay ....<br>
<br>
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.<br>
<br>
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.<br>
<br>
Thanks,<br>
<br>
Ryan<br>
<br>
<br>
<div>
<hr>
From: <a href="mailto:abbaseo@gmail.com" target="_blank">abbaseo@gmail.com</a><br>
To: <a href="mailto:ryanhuff@outlook.com" target="_blank">ryanhuff@outlook.com</a>; <a href="mailto:cisco-voip@puck.nether.net" target="_blank">
cisco-voip@puck.nether.net</a><br>
Subject: RE: [cisco-voip] isdn channels full message<br>
Date: Tue, 23 Jun 2015 13:55:42 +0100<br>
<br>
<div>
<div style="margin:0px;padding:0px"><span style="font-size:11pt;font-family:Calibri,sans-serif;color:rgb(31,73,125)">Hi just to add it to.</span></div>
<p style="margin:0px;padding:0px"><span style="font-size:11pt;font-family:Calibri,sans-serif;color:rgb(31,73,125)"> </span></p>
<div style="margin:0px;padding:0px"><span style="font-size:11pt;font-family:Calibri,sans-serif;color:rgb(31,73,125)">We need it only for the outbound direction.</span></div>
<p style="margin:0px;padding:0px"><span style="font-size:11pt;font-family:Calibri,sans-serif;color:rgb(31,73,125)"> </span></p>
<div>
<div style="border-style:solid none none;border-top-color:rgb(225,225,225);border-top-width:1pt;padding:3pt 0cm 0cm">
<div style="margin:0px;padding:0px"><b><span lang="EN-US" style="font-size:11pt;font-family:Calibri,sans-serif">From:</span></b><span lang="EN-US" style="font-size:11pt;font-family:Calibri,sans-serif"><span> </span>Ryan
Huff [<a href="mailto:ryanhuff@outlook.com" target="_blank">mailto:ryanhuff@outlook.com</a>]<span> </span><br>
<b>Sent:</b><span> </span>23 June 2015 13:51<br>
<b>To:</b><span> </span>abbas wali; <a href="mailto:cisco-voip@puck.nether.net" target="_blank">
cisco-voip@puck.nether.net</a><br>
<b>Subject:</b><span> </span>RE: [cisco-voip] isdn channels full message</span></div>
</div>
</div>
<p style="margin:0px;padding:0px"> </p>
<div>
<div style="margin:0px;padding:0px"><span style="font-family:Calibri,sans-serif">I don't believe so, at least not on the CPE side.<span> </span><br>
<br>
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.<br>
<br>
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.<br>
<br>
Thanks,<br>
<br>
Ryan</span></div>
<div>
<div align="center" style="text-align:center"><span style="font-family:Calibri,sans-serif">
<hr align="center" size="2" width="100%">
</span></div>
<div style="margin:0px;padding:0px"><span style="font-family:Calibri,sans-serif">From:<span> </span><a href="mailto:abbaseo@gmail.com" target="_blank">abbaseo@gmail.com</a><br>
To:<span> </span><a href="mailto:cisco-voip@puck.nether.net" target="_blank">cisco-voip@puck.nether.net</a><br>
Date: Tue, 23 Jun 2015 11:38:55 +0100<br>
Subject: [cisco-voip] isdn channels full message</span></div>
<div>
<div style="margin:0px;padding:0px"><span style="font-family:Calibri,sans-serif">Hi folks,</span></div>
<p style="margin:0px;padding:0px"><span style="font-family:Calibri,sans-serif"> </span></p>
<div style="margin:0px;padding:0px"><span style="font-family:Calibri,sans-serif">CUCM 9 and H323 gateways with ISDN channels to PSTN. We want to redirect to VM when all the channels are full.</span></div>
<p style="margin:0px;padding:0px"><span style="font-family:Calibri,sans-serif"> </span></p>
<div style="margin:0px;padding:0px"><span style="font-family:Calibri,sans-serif">Can CUCM do it or Dpeer?</span></div>
<p style="margin:0px;padding:0px"><span style="font-family:Calibri,sans-serif"> </span></p>
<div style="margin:0px;padding:0px"><span style="font-family:Calibri,sans-serif">Thanks</span></div>
<p style="margin:0px;padding:0px"><span style="font-family:Calibri,sans-serif"> </span></p>
</div>
<div style="margin:0px;padding:0px"><span style="font-family:Calibri,sans-serif"><br>
_______________________________________________ cisco-voip mailing list<span> </span><a href="mailto:cisco-voip@puck.nether.net" target="_blank">cisco-voip@puck.nether.net</a><a href="https://puck.nether.net/mailman/listinfo/cisco-voip" target="_blank">https://puck.nether.net/mailman/listinfo/cisco-voip</a></span></div>
</div>
</div>
</div>
</div>
</div>
_______________________________________________<br>
cisco-voip mailing list<br>
<a href="mailto:cisco-voip@puck.nether.net" target="_blank">cisco-voip@puck.nether.net</a><br>
<a href="https://puck.nether.net/mailman/listinfo/cisco-voip" target="_blank">https://puck.nether.net/mailman/listinfo/cisco-voip</a></div>
</div>
</div>
<br>
</div>
</div></div><br>_______________________________________________<br>
cisco-voip mailing list<br>
<a href="mailto:cisco-voip@puck.nether.net">cisco-voip@puck.nether.net</a><br>
<a href="https://puck.nether.net/mailman/listinfo/cisco-voip" rel="noreferrer" target="_blank">https://puck.nether.net/mailman/listinfo/cisco-voip</a><br>
<br></blockquote></div><br></div>