Re: E1 ISDN PRI - Up but not able to make or receive calls

segrana · ‎10-29-2010

Hi, help needed,

Having this seriuos problem, telco said everything is ok form their point of view.

This is my config and my status

network-clock-participate wic 0
network-clock-select 1 E1 0/0/0

isdn switch-type primary-net5

controller E1 0/0/0
framing NO-CRC4
pri-group timeslots 1-31
trunk-group tg_AntelDTT timeslots 1-31

interface Serial0/0/0:15
no ip address
encapsulation hdlc
isdn switch-type primary-net5
isdn incoming-voice voice
isdn send-alerting
isdn negotiate-bchan resend-setup
isdn sending-complete

sh isdn status

Global ISDN Switchtype = primary-net5
ISDN Serial0/0/0:15 interface
        dsl 0, interface ISDN Switchtype = primary-net5
    Layer 1 Status:
        ACTIVE
    Layer 2 Status:
        TEI = 0, Ces = 1, SAPI = 0, State = MULTIPLE_FRAME_ESTABLISHED
    Layer 3 Status:
        0 Active Layer 3 Call(s)
    Active dsl 0 CCBs = 0
    The Free Channel Mask: 0xFFFF7FFF
    Number of L2 Discards = 0, L2 Session ID = 1
    Total Allocated ISDN CCBs = 0

E1 0/0/0 is up.
Applique type is Channelized E1 - balanced
Cablelength is Unknown
No alarms detected.
alarm-trigger is not set
Version info Firmware: 20090408, FPGA: 13, spm_count = 0
Framing is NO-CRC4, Line Code is HDB3, Clock Source is Line.
CRC Threshold is 320. Reported from firmware is 320.
Data in current interval (4 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

When I make an outgoing call this is the output of the debug isdn q931

*Oct 29 22:13:43.011: ISDN Se0/0/0:15 Q931: Applying typeplan for sw-type 0x12 is 0x4 0x1, Calling num 29160756
*Oct 29 22:13:43.011: ISDN Se0/0/0:15 Q931: Applying typeplan for sw-type 0x12 is 0x4 0x1, Called num 24196457
*Oct 29 22:13:43.011: ISDN Se0/0/0:15 Q931: TX -> SETUP pd = 8 callref = 0x0081
        Sending Complete
        Bearer Capability i = 0x8090A3
                Standard = CCITT
                Transfer Capability = Speech
                Transfer Mode = Circuit
                Transfer Rate = 64 kbit/s
        Channel ID i = 0xA18381
                Preferred, Channel 1
        Calling Party Number i = 0x4181, '29160756'
                Plan:ISDN, Type:Subscriber(local)
        Called Party Number i = 0xC1, '24196457'
                Plan:ISDN, Type:Subscriber(local)
*Oct 29 22:13:45.027: ISDN Se0/0/0:15 Q931: RX <- RELEASE_COMP pd = 8 callref = 0x8081
        Cause i = 0x82A9 - Temporary failure

When I make an incoming call no info is received in the router.

The temporary failure cause does not help, it is a swith failure.

Any help will be appreciated.

Thanks

Regards

paolo bevilacqua · ‎10-29-2010

Set called numbering plan/type to unknown/unknown or isdn/national.

If you don't know what that means, I seriously recommend you get help from someone that does.

About no call received, challenge telco to prove they are delviering the call, or do not accept the circtui, and do not pay for it.

segrana · ‎10-29-2010

Hi Paolo,

Thanks for your message. I know what you are talking about, and i have already configured translations to set the appropriate type/plan

voice translation-rule 3
rule 1 /^$.*$$/ /\1/ type unknown subscriber plan unknown isdn
!
voice translation-rule 4
rule 1 /^.*/ /29156161/ type unknown subscriber

Finally, after 10 hours telco has done something and things started to work.

If you ever come to Uruguay, please stay away from ANTEL.

Regards

asandborgh · ‎10-29-2010

+5 to both for the frustration and diligence- sad that one of the biggest challenges we have is Telcos - all over the world...

paolo bevilacqua · ‎10-30-2010

Todos telcos son asì.

Consolate, al otro lado del Rio ni el PRI tengon.

Gracias y saludos!

russell.sage · ‎10-30-2010

As an engineer for a major UK Telco I can fully understand where they are coming from they will have checked the switch port on the exchange and as your show ISDN status shows multiframe is established.

I would try setting your numbering plan and number type to unknown/unknown usually the safest bet unless your telco has advised you otherwise

paolo bevilacqua · ‎10-30-2010

As an engineer for a major UK Telco I can fully understand where they are coming from they will have checked the switch port on the exchange and as your show ISDN status shows multiframe is established.

As OP indicated above problem is solved, it was indeed telco fault.