[cisco-voip] Outbound Call Routing Timers

[Ryan Ratliff]

> PS have you guys seen the bug with Mobility and 9.1(1)a with +E.164 DNs? The mobility softkey doesn't work. Apparently fixed in an earlier ES but not til version 10 for a general release. 

This is CSCud88503 if you hit it and need the ES.  It will also appear in any 9.1(1)SU that posts.

-Ryan

On Mar 29, 2013, at 4:16 AM, Dana Tong <Dana_Tong at bridgepoint.com.au> wrote:

Thanks guys,  

T310 was the timer to change on the H323 gateway, however the real problem was that I was not receiving Q931 progress and connect messages. I spoke to the guy who looks after the other PBX and it looks like he's fixed something on his side. I am now seeing progress and connect messages. I will dial the timers back to default and test again on Tuesday morning. 

Thanks all. 

PS have you guys seen the bug with Mobility and 9.1(1)a with +E.164 DNs? The mobility softkey doesn't work. Apparently fixed in an earlier ES but not til version 10 for a general release. 

Regards,
Dana Tong

On 29/03/2013, at 3:45 PM, "Erick B." <erickbee at gmail.com> wrote:

> What issues are you experiencing?
> 
> If the PRIs are working fine, and all channels are in use it could be the Stop Routing on User Busy flag or unallocated Number flag coming into play, or something else.
> 
> Also, I had a client with a remote site that was having WAN troubles and Call Manager could not establish a TCP connection to the remote gateway most of the time so the calls went out the second gateway in the route group. The CM traces clearly showed the TCP connection failed to establish to the first gateway. 
> 
> As Wes said, look through the SDI and possibly SDL traces to find cause of your problem. 
> 
> 
> 
> On Thu, Mar 28, 2013 at 12:42 PM, Wes Sisk <wsisk at cisco.com> wrote:
> There are several timers that could potentially be expiring and causing the hunting. Most are under h.323 or isdn/q931. Careful review of CM SDI and SDL traces will reveal the exact condition causing the hunting - it could be something other than a timer.
> 
> -wes
> 
> On Mar 27, 2013, at 9:43 PM, Dana Tong <Dana_Tong at bridgepoint.com.au> wrote:
> 
> Hi all,
>  
> I have a H323 Gateway with PRI connections to multiple providers.
>  
> I have a CUCM Route List with two route groups configured Top-down.
> I can see calls hunting to the first PRI and then hunting to the second PRI ok.
>  
> What I would like to do is extend the timer of the call setup to the first PRI before it tries to route to the second PRI.
>  
> Does anyone know what timer this is? Would it be in the UCM Service Parameters for “clusterwide parameters – H323”?
>  
> Cheers
> Dana
>  
> _______________________________________________
> 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/20130401/64289af1/attachment.html>