[cisco-voip] h.323 gq with PRI destination out of order (27)) !!!

[Wes Sisk]

Hmm,
I suspect you could remap the ISDN cause codes.  Use and commands have 
been discussed on this list before.  A little googling will likely prove 
fruitful.

/Wes

On Monday, July 06, 2009 6:57:07 AM, Djokic Sinisa <sdjokic at mds.rs> wrote:
>
>  
>
> hi group..
>
>  
>
> does anybody knows how to solve this one i'm going to describe..
>
>  
>
>  
>
> we have h.323 gateways with E1 PRI..
>
>  
>
> so, when isdn PRI is down ( link or whatever problem it may occur ), 
> customer had a problem since no re-route is happening ( no redundant 
> route group in route list is triggered )..
>
>  
>
> in order to provide backup for this and solve this issue we changed 
> service parameter in CCM :
>
>  
>
> *Stop Routing on Unallocated Number Flag* * 
> <javascript:%20openHelpWindow('vendorconfighelp.asp?instance=xmldi://cisco.com/serviceParameters/0&title=Cisco+CallManager+Parameters+Help&showAll=Yes#StopRoutingOnUnallocatedNumberFlag');>**
>
>  
>
> from true to false..
>
>  
>
> and after that backup ( second route group in route list ) is working 
> just fine..
>
>  
>
>  
>
> but the new problem happened in the following situation..
>
>  
>
> if TELCO is having problem with certain PSTN numbers ( for example 
> some home or bussines line is out of order ), when IP telephony user 
> from CCM tries to call that number in PSTN..
>
> the call goes arround through every single route group in route list 
> and eventually  it doesn't succeed since called number is out of order..
>
>  
>
> so, in h.323 gw with PRI logs we have " destination out of order (27)) 
> " for that specific call, and i suppose it is turned back to 
> callmanager as " unallocated number " and based on it's service 
> paramter it doesn't stop routing..
>
>  
>
>  
>
> to summarize this long writting, is there a way to overcome this 
> issue, to be able to re-route a call when ISDN service is down, but 
> not to do it when particular subscriber on PSTN is down..
>
> since, i that case, call will just bounce and user would have to wait 
> a lot of time to get "busy signal "..
>
>  
>
>  
>
>  
>
> thanx..
>
>  
>
>  
>
> regards..
>
>  
>
>  
>
>  
>
> **Sinisa Djokic**
>
> System Engineer
> CCNP,CCDA,CQS-CWLDS,CS-CIPTDS,CS-CIPCCES Cisco Certified
>
>  
>
> 	
>
>  
>
> 	
>
> MDS Informaticki inzenjering
> Bul. Arsenija Carnojevica 170
> 11070 Novi Beograd, Serbia
> Tel: +381 11 2015 200, 2015 273
> Fax: +381 11 3194 954
> www.mds.rs <http://www.mds.rs>
> sdjokic at mds.rs <mailto:sdjokic at mds.rs>
>
>  
>
> ------------------------------------------------------------------------
>
> _______________________________________________
> 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/20090706/4bfe5ef4/attachment.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: image/gif
Size: 3522 bytes
Desc: not available
URL: <https://puck.nether.net/pipermail/cisco-voip/attachments/20090706/4bfe5ef4/attachment.gif>