Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations wOOdy-Soft on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

Select ARS entry after receipt of Q.931 disconnect code ?

Status
Not open for further replies.

SharpieX11

Technical User
Jun 16, 2009
3
GB
We use the traditional method of T1/E1 PRI between PBX and Cisco router for our ACM locations and are able to use the Look Ahead Routing feature in conjunction with our MPLS WAN.

However, I'm trying to re-create LAR or get the IPO 500 4.2 (20) to take action (use ARS) upon receipt of the Q.931 error code is sees when the MPLS is down.

I have calls to our sister site running over the T1/E1 pri (PBX->E1 PRI->Cisco WAN router->MPLS->Cisco WAN router->T1 PRI->ACM) without any problems and if I create a physical disconnect (pull the cable between PBX and WAN router) the IPO will use ARS and send the call over the PSTN.

However, when I shutdown the outside MPLS interface, the IPO is still seeing the trunks between PBX and the inside physical interface of the WAN router up and idle all the time so, sends the call to these trunks......then the Q.931 error code is sent back and the user hears the error tone at the telset.

Can you configure the IPO to act upon receipt of this Q.931 error code ?

I can set on the Cisco WAN router any Q.931 error code to be returned to the IPO but can the PBX act upon it ?

Thanks

 
How ARS treats the different ISDN cause codes is in the Manager manual:
Basically 3 groups: 1) The route is not working so see if there is another route to the destination. 2) The destination is not available regardless of route so stop trying. 3) Anything else - try other routes. So you need to create scenarios where the cause code is in groups 1 or 3 and have alternate line group matches for those.
 
Great & Thanks very much!

I have just been using he wrong cause codes (42 & 34)which, IPO does not act on.

I'll give that a try tomorrow.

Thanks again.
 
OK, I have tried different cause codes to be issued back to the PBX (taken from group 1 below) and the Cisco router sends back whatever I tell it too which, the PBX is receiving as I can see this via the SysMonitor tool. However, the PBX/ARS table is not following the Alternate route set, based on this cause code. It shows the cause code and gives an error tone and the call is not completed.

I even set the Out of Service option to re-route calls to the PSTN which, works when I manually uncheck the InService box (as you would expect).

I just want it automated.....grrr

ANY IDEAS ?


ARS routing to digital trunks can be affected by signalling from the trunk. The response to cause codes received from the line is as follows:

1 Reroute with ARS
The following cause codes cause ARS to no longer target the line group (unless it is specified by an alternate ARS route).

Code Cause Code

1 Unallocated Number.
2 No route to specific transit network / (5ESS) Calling party off hold.
3 No route to destination. / (5ESS) Calling party dropped while on hold.
4 Send special information tone/(NI-2) Vacant Code.
5 Misdialed trunk prefix.
8 Preemption / (NI-2) Prefix 0 dialed in error.
9 Preemption, cct reserved/ (NI-2) Prefix 1 dialed in error.
10 (NI-2) Prefix 1 not dialed.
11 (NI-2) Excessive digits received call proceeding.
22 Number Changed.
28 Invalid Format Number.
29 Facility Rejected.
50 Requested Facility Not Subscribed.
52 Outgoing calls barred.
57 Bearer Capability Not Authorized.
63 Service or Option Unavailable.
65 Bearer Capability Not Implemented.
66 Channel Type Not Implemented.
69 Requested Facility Not Implemented.
70 Only Restricted Digital Information Bearer Capability Is Available.
79 Service Or Option Not Implemented.
88 Incompatible.
91 Invalid Transit Network Selection.
95 Invalid Message.
96 Missing Mandatory IE.
97 Message Type Nonexistent Or Not Implemented.
98 Message Not Implemented.
99 Parameter Not Implemented.
100 Invalid IE Contents.
101 Msg Not Compatible.
111 Protocol Error.
127 Interworking Unspecified.

2 Stop ARS
The following cause codes stop ARS targeting completely.

Code Cause Code

17 Busy.
21 Call Rejected.
27 Destination Out of Order.

3 No Affect
All other cause codes do not affect ARS operation.

 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top