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

SCN Vs. PRI

Status
Not open for further replies.

kflounders

Programmer
Dec 8, 2002
694
US
Site A 406V2 at 4.1 with PRI

Site B 406V2 at 4.1 with point to point T-1 to Site A through Kentrox Routers and no local dial tone.

I have been troubleshooting dropped calls at site B and have finnally caught one on System Status on both sides. This was a call from extension 201 on site B through the SCN to the PRI on Site A. Call dropped after 14 minutes. After looking at the issue I am starting to think it doesn't have anything to do with the SCN and the PRI is to blame. There are no errors on either sites System Status, so the question is: Do these errors look like a simple PRI drop and not an IP/VCM issue?

Site A Trace output

5/7/09 5:42:55 AM-136ms Line = 5, Channel = 23, Q.931 Message = StatusEnquiry, Call Ref = 50606, Direction = To Switch
5/7/09 5:42:55 AM-137ms Line = 5, Channel = 23, Q.931 Message = Status, Call Ref = 50606, Direction = From Switch, Cause Code = 30
5/7/09 5:47:07 AM-146ms Line = 200, Channel = 1, Q.931 Message = ReleaseComplete, Call Ref = 50606, Direction = From Switch
5/7/09 5:47:07 AM-149ms Call Ref = 50606, Originator State = Clearing, Type = Trunk, Destination State = Connected, Type = Trunk
5/7/09 5:47:07 AM-149ms Call Ref = 50606, Disconnect from Originator End


Site B Trace Output from same call

1/13/09 4:40:59 PM-871ms Line = 201, Channel = 1, Q.931 Message = ReleaseComplete, Call Ref = 355, Direction = From Switch
1/13/09 4:40:59 PM-875ms Call Ref = 355, Originator State = Connected, Type = User, Destination State = Clearing, Type = Trunk
1/13/09 4:40:59 PM-875ms Call Ref = 355, Disconnect from Destination End
 
I think you will need to turn on some more of the ISDN Layer 1/2 options to get more info.

ISDN Cause Codes:

Cause No. 30 - response to STATUS INQUIRY.
This cause is included in the STATUS message when the reason for generating the STATUS message was the prior receipt of a STATUS INQUIRY.

Not sure what that means though.

Jamie Green

ACA:Implement - IP Office
ACS:Implement - IP Office

Football is not a matter of life and death-It is far more important!!!!
 
Are you getting timing errors? Sounds like clocking issues...You have several devices in the mix and they all really should have a single clock source so...

SiteB IPOffice PRI should be set for Network
SiteB Kentrox PRI interface should be set for slave
SiteB Kentrox PtP Interface should be set for Network

SiteA Kentrox PtP interface should be set for Slave
SiteA Kentrox PRI interface should be set for Network
SiteA IPOffice PtP PRI should be set to Fallback
SiteA IPOffice Carrier PRI should be set for Network

Its too early in the year to think that much
---
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top