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 biv343 on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

SITE A USING TRUNKS FOR SITE BE TO CALL OUT

Status
Not open for further replies.

pea123

Technical User
Aug 26, 2009
380
Hi all.

I have 2 IPO 500v2 R9 systems connected together via H323. Extensions can call each other fine. I want Site A to use trunks on Site B for outgoing calls. When Site A makes an outgoing call I see the call hitting Site B on SSA but the call does not complete. get a fast busy. System B can call outside fine. See traces below.
What could be wrong? Please advise.

2014/10/14 3:50:11 PM-102ms Line = 18, Line Ref = 32787, Q.931 Message = Setup, Direction = To Switch, Calling Party Number = 1110, Called Party Number = 00776867238
2014/10/14 3:50:11 PM-108ms Line = 18, Channel Allocated, Channel ID = 1, Call Ref = 26, Line Ref = 32787
2014/10/14 3:50:11 PM-108ms Call Ref = 26, Short Code Matched = System, 007XXXXXXXX
2014/10/14 3:50:11 PM-117ms Call Ref = 26, Originator State = Waiting For Line, Type = Trunk, Destination Type = ARS Form
2014/10/14 3:50:11 PM-125ms Line = 18, Channel = 1, Q.931 Message = Progress, Call Ref = 26, Direction = From Switch
2014/10/14 3:50:15 PM-111ms Line = 18, Channel = 1, Q.931 Message = Setup, Call Ref = 26, Direction = To Switch, Calling Party Number = 1110, Called Party Number = 00776867238
2014/10/14 3:50:15 PM-112ms Line = 18, Channel = 1, Q.931 Message = Status, Call Ref = 26, Direction = From Switch, Cause Code = 101
2014/10/14 3:50:19 PM-127ms Line = 18, Channel = 1, Q.931 Message = ReleaseComplete, Call Ref = 26, Direction = To Switch, Cause Code = 102
2014/10/14 3:50:19 PM-128ms Call Ref = 26, Originator State = Clearing, Type = Trunk, Destination Type = ARS Form
2014/10/14 3:50:19 PM-128ms Call Ref = 26, Disconnect from Originator End
 
Well these are the cause codes

101
Message not compatible with call state / (NI-2) Protocol threshold exceeded.

102
Recovery on timer expiry.

Its looking like you are insering an extra 0 if you are in the uk so your ARS needs to be looked at , can you give them a break out button at site A get them to press it select site b and see if they can call out in that scenario

APSS (SME)
ACSS (SME)
ACIS (UC)
 
No luck.
Actual Number 0776867238
Short Code for Site B is Dial 00776867238->0776867238->Line 18
Site B can call 0776867238

What does code 101 and 102 mean?
 
I have seen the problem but unfortunately not the solution.
Site B has Force Authorization checked for the Short Code. If unchecked the call goes through. I want the short code to be checked. How do I achieve this?
Site A is already checked for Force Authorization and must remain so.
 
Site B has Force Authorization checked for the Short Code. If unchecked the call goes through (got to be a clue)

have you tried the break out button or not , have you addressed the ars you are sending one 0 too many to site B

APSS (SME)
ACSS (SME)
ACIS (UC)
 
Doing the authorisation code check on switch A before the dialling then goes off switch too Site B. The Force Authorization/Force Account code options are only supported for on-switch dialing by users of that switch.

Stuck in a never ending cycle of file copying.
 
On the code that dials out site A add a prefix, use that prefix to route calls to a different ARS that doesn't check again for Auth codes on Site B :)

 
Add a shortcode in the H.323 line of site B : sc=0N TN = N Action = dial line ID = the ID of the outgoing line on site B
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top