cancel
Showing results for 
Search instead for 
Did you mean: 
cancel
Announcements
775
Views
15
Helpful
10
Replies
Cameron Whitehead
Enthusiast

PRI not working

I have setup a new PRI on a 4321 ISR as I have done before however this time I am having issues getting calls working.  Layer 1 is showing active, layer 2 is showing multiple frames established but when I do an inbound call I get a busy signal.  When I do a debug isdn q931 I do not see anything coming in from the telco.  I did a "Show Tech Voice" and I can see Path Code Violations in the output but not sure what to do with that.  I have called the telco and we put the 4321 into loopback and everything looked fine with that.  We put it back into service and they said on their side it shows the D channel is up but that the B channels are all showing "remotly made busy"  he said it looks like my phone system has forced all the B channels into busy.  I am not sure how this would be done.


Hopefully this all makes sense.  Please let me know know if anyone has any ideas.

1 ACCEPTED SOLUTION

Accepted Solutions

You have to work with ISP then. 

 



Response Signature


View solution in original post

10 REPLIES 10
Scott Leport
Rising star

If you issue "show isdn service" on your ISR, what are the operational state of the B channels?

Do you have any method of testing outgoing calls out the PRI?

The link here shows how to deliberately busy out your B channels, but I would hope this config isn't in place.

https://community.cisco.com/t5/collaboration-voice-and-video/how-to-busy-out-the-b-channel-on-an-isdn-pri-in-ios-gateways/ta-p/3132765

 

Thanks for the reply Scott.  Yes I can see using show isdn service that all the channels are idle.  I have not tried an outbound call but I will try to setup a phone to use this gateway and see what I can see.  I looked at the line and that configuration is not in place.

 

ISDN Se0/1/0:23, Channel [1-24]
Configured Isdn Interface (dsl) 0
Channel State (0=Idle 1=Proposed 2=Busy 3=Reserved 4=Restart 5=Maint_Pend)
Channel : 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4
State : 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 3
Service State (0=Inservice 1=Maint 2=Outofservice 8=MaintPend 9=OOSPend)
Channel : 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4
State : 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 2

So I have now tested an outbound call and it is giving me a very interesting result.  The call seems to go through as my cell phone (the called device) rings but at the same time my Cisco phone is giving me a busy tone.  My debug is showing me sending setup messages to the Telco but I am getting nothing back.  In the end I get the following error:

ISDN Se0/1/0:23 **ERROR**: CCPCC_CallOrigination: SETUP timed-out (2nd T303) to NETWORK. The SETUP failed.

Hi Cameron,

 

That's progress I suppose. It does sound like a provider issue TBH, based on the fact that you're not seeing anything in the debug for inbound and they're not responding to your setup message for outbound.

 

Based on the error message, there are some threads on the web suggesting to check the physical connections, ISDN switch-type, your voice-port and for line code errors on your T1 controller. I am a little out of practice in the PRI realm these days, but I find it unlikely that any of these would contribute to this issue.

 

There is also this post, which seems to hint at a provider issue, unfortunately no resolution or solution was given:

https://community.cisco.com/t5/ip-telephony-and-phones/error-ccpcc-callorigination-setup-timed-out-2nd-t303-to-network/td-p/2476025

 

I think the best you can do is keep working with your provider and try to get a resolution.

Nithin Eluvathingal
VIP Mentor

Can you share the Output of show controller E1 output. To check If there is any errors. 

 

If calls doesn't land on your gateway, its an ISP issues. They didn't add required  routes to  your New PRI. 

 

What network clock commands you configured on your gateway ?

 

 



Response Signature


T1 0/1/0 is up
Applique type is Channelized T1
Cablelength is long gain36 0db
No alarms detected.
alarm-trigger is not set
Soaking time: 3, Clearance time: 10
AIS State:Clear LOS State:Clear LOF State:Clear
Framing is ESF, Line Code is B8ZS, Clock Source is Line Primary.
BER thresholds: SF = 10e-3 SD = 10e-6
Data in current interval (313 seconds elapsed):
0 Line Code Violations, 18 Path Code Violations
0 Slip Secs, 0 Fr Loss Secs, 0 Line Err Secs, 0 Degraded Mins
18 Errored Secs, 0 Bursty Err Secs, 0 Severely Err Secs, 0 Unavail Secs
Total Data (last 24 hours)
0 Line Code Violations, 25916 Path Code Violations,
3 Slip Secs, 0 Fr Loss Secs, 0 Line Err Secs, 0 Degraded Mins,
12878 Errored Secs, 4254 Bursty Err Secs, 0 Severely Err Secs, 0 Unavail Secs

 

I have clock source line primary setup on controller T1 0/1/0

3 Slip Secs, 0 Fr Loss Secs, 0 Line Err Secs, 0 Degraded Mins,
12878 Errored Secs, 4254 Bursty Err Secs, 0 Severely Err Secs, 0 Unavail Secs

 

I can see error on your PRI. Try the below commands. 

 

controller E1 0/1/0

clock source line primary

 

!
network-clock synchronization automatic

network-clock input-source 1 controller E1 0/1/0



Response Signature


Thanks Nithin,  I tried adding the lines you suggested and it seems the number errors on my T1 have reduced.  It looks steady for a while then it jumps up where as before it was just constantly climbing.  When I do a debug isdn q931 for an outbound call I can see my system sending setup requests but it never receives a response so eventually it just times out.

 

066849: *Nov 5 08:06:27.440: ISDN Se0/1/0:23 Q931: Applying typeplan for sw-type 0xD is 0x2 0x1, Calling num 5555555555
066850: *Nov 5 08:06:27.440: ISDN Se0/1/0:23 Q931: Sending SETUP callref = 0x0081 callID = 0x8009 switch = primary-ni interface = User
066851: *Nov 5 08:06:27.440: ISDN Se0/1/0:23 Q931: TX -> SETUP pd = 8 callref = 0x0081
Bearer Capability i = 0x8090A2
Standard = CCITT
Transfer Capability = Speech
Transfer Mode = Circuit
Transfer Rate = 64 kbit/s
Channel ID i = 0xA98397
Exclusive, Channel 23
Calling Party Number i = 0x2181, '5555555555'
Plan:ISDN, Type:National
Called Party Number i = 0xA1, '6666666666'
Plan:ISDN, Type:National
066852: *Nov 5 08:06:28.440: ISDN Se0/1/0:23 Q931: TX -> SETUP pd = 8 callref = 0x0081
Bearer Capability i = 0x8090A2
Standard = CCITT
Transfer Capability = Speech
Transfer Mode = Circuit
Transfer Rate = 64 kbit/s
Channel ID i = 0xA98397
Exclusive, Channel 23
Calling Party Number i = 0x2181, '5555555555'
Plan:ISDN, Type:National
Called Party Number i = 0xA1, '6666666666'
Plan:ISDN, Type:National
066853: *Nov 5 08:06:31.440: ISDN Se0/1/0:23 Q931: TX -> SETUP pd = 8 callref = 0x0081
Bearer Capability i = 0x8090A2
Standard = CCITT
Transfer Capability = Speech
Transfer Mode = Circuit
Transfer Rate = 64 kbit/s
Channel ID i = 0xA98397
Exclusive, Channel 23
Calling Party Number i = 0x2181, '5555555555'
Plan:ISDN, Type:National
Called Party Number i = 0xA1, '6666666666'
Plan:ISDN, Type:National
066854: *Nov 5 08:06:35.442: ISDN Se0/1/0:23 **ERROR**: CCPCC_CallOrigination: SETUP timed-out (2nd T303) to NETWORK. The SETUP failed.

You have to work with ISP then. 

 



Response Signature


ISP finally found the issue on their switch.

Create
Recognize Your Peers
Content for Community-Ad