Voice over IP: ISDN PRI Voice E1 - Calling Out problmes (PSTN)

Answered Question
Jun 22nd, 2009

Hi All,

Has anyone seen this before in a 'debug isdn q931' on a H323 gateway.

*Jun 15 07:39:03.893: ISDN Se0/2/1:15 **ERROR**: CCPMSG_OutCall: fails with cause 0x22.

When I am trying to call out side getting busy signal.The incoming calls working fine. But some times it working without any problems.

Please go through the attached configs...

Thanks

Ilyas

I have this problem too.
0 votes
Correct Answer by Paolo Bevilacqua about 7 years 5 months ago

Hi, you have major problems on the physical circuit, have telco fix it.

Please send output of "show controllers e1" and "show network-clocks" just for an additional check.

Do not use attachments unles necessary.

  • 1
  • 2
  • 3
  • 4
  • 5
Overall Rating: 5 (1 ratings)
Loading.
Correct Answer
Paolo Bevilacqua Wed, 06/24/2009 - 13:51

Hi, you have major problems on the physical circuit, have telco fix it.

Please send output of "show controllers e1" and "show network-clocks" just for an additional check.

Do not use attachments unles necessary.

ilyasrahiman Wed, 06/24/2009 - 20:46

10.31.144.2#sh controllers e1

E1 0/2/0 is administratively down.

E1 0/2/1 is up.

Applique type is Channelized E1 - balanced

Cablelength is Unknown

No alarms detected.

alarm-trigger is not set

Version info Firmware: 20080918, FPGA: 13, spm_count = 0

Framing is CRC4, Line Code is HDB3, Clock Source is Line.

Data in current interval (351 seconds elapsed):

0 Line Code Violations, 0 Path Code Violations

0 Slip Secs, 0 Fr Loss Secs, 0 Line Err Secs, 0 Degraded Mins

0 Errored Secs, 0 Bursty Err Secs, 0 Severely Err Secs, 0 Unavail Secs

Total Data (last 24 hours)

0 Line Code Violations, 0 Path Code Violations,

0 Slip Secs, 0 Fr Loss Secs, 0 Line Err Secs, 0 Degraded Mins,

0 Errored Secs, 0 Bursty Err Secs, 0 Severely Err Secs, 0 Unavail Secs

10.31.144.2#

10.31.144.2#sh network-clocks

Network Clock Configuration

---------------------------

Priority Clock Source Clock State Clock Type

1 E1 0/2/1 GOOD E1

10 Backplane GOOD PLL

Current Primary Clock Source

---------------------------

Priority Clock Source Clock State Clock Type

1 E1 0/2/1 GOOD E1

10.31.144.2#

*Jun 25 04:49:30.483: ISDN Se0/2/1:15 Q931: Applying typeplan for sw-type 0x12 is 0x0 0x1, Calling num 73845

*Jun 25 04:49:30.483: ISDN Se0/2/1:15 Q931: Sending SETUP callref = 0x02D4 callID = 0x8260 switch = primary-net5 interface = User

*Jun 25 04:49:30.483: ISDN Se0/2/1:15 Q931: TX -> SETUP pd = 8 callref = 0x02D4

Sending Complete

Bearer Capability i = 0x8090A3

Standard = CCITT

Transfer Capability = Speech

Transfer Mode = Circuit

Transfer Rate = 64 kbit/s

Channel ID i = 0xA9839F

Exclusive, Channel 31

Calling Party Number i = 0x0181, '73845'

Plan:ISDN, Type:Unknown

Called Party Number i = 0x80, '141'

Plan:Unknown, Type:Unknown

10.31.144.2#

In this output the E1 was up - able to call outside..., will try to get the down time output if necessary

ashraf1891 Thu, 06/25/2009 - 12:48

Hey Brother

Is your gateway is registerd as MGCP or H323?!?!

your description is H323 but the configuration is MGCP.

so under the interface Serial0/2/1:15 you should bind the layer 3 to the CCM (isdn bind l3 ccm).

also in the pri group configuration you should but service MGCP (pri-group timeslots 1-31 service MGCP)

another thing if its MGCP you will never need those VOIP dial-peers.

coz your channel whill be backholed in the CCM. make sure in the CCM that you configured the Chanel B maintenance on the service parameter.

after that just stop MGCP by no MGCP and turn it on again.

HTH

ilyasrahiman Thu, 06/25/2009 - 13:10

One port is H323 config - working one.

But I have tested the other port using MGCP.

ilyasrahiman Sat, 06/27/2009 - 07:01

Teleco team working on the PRI, they told me that there is some issues related with channeling. Once it resolved I will update the details.

Thanks...

Actions

This Discussion