Cisco Support Community
cancel
Showing results for 
Search instead for 
Did you mean: 
Community Member

ISDN PRI E1 on incoming call says: isdnAsn1Inv: error: unknown operation 12

I have a new setup consisting of a Call Manager v4.1.3 and a 2811 voice router with an NM-HDV2-2T1/E1 two port PRI ISDN card. The outgoning calls initiated from any IP phone to all destinations are all right, but incoming calls terminate with an unknown ISDN error. Anyone has an idea of what's going on on this ISDN and what could be done?

running config excerpt from 2811:

voice translation-rule 1

rule 1 /^\(.*\)/ /0\1/

!

voice translation-rule 2

rule 1 /^48200\(...\)/ /9\1/

!

voice translation-rule 3

rule 1 /^9\(...\)/ /48200\1/

!

!

voice translation-profile CreateExtPrefix

translate calling 1

translate called 2

!

voice translation-profile CreatePTTNumber

translate calling 3

!

--trunkated--

controller E1 1/0

pri-group timeslots 1-31

!

--trunkated--

!

interface Serial1/0:15

no ip address

encapsulation hdlc

isdn switch-type primary-net5

isdn incoming-voice voice

isdn sending-complete

!

voice-port 1/0:15

translation-profile incoming CreateExtPrefix

translation-profile outgoing CreatePTTNumber

no vad

cptone SK

bearer-cap 3100Hz

!

I use the following debug:

The following ISDN debugs are enabled on all DSLs:

debug isdn error is ON.

debug isdn q931 is ON. (filter is OFF)

debug isdn q931 detail is ON.

debug isdn asn1 is ON.

Translation debug detail is on

Translation debug min is on

The debug output gives this with debug q931 and asn1, and nothing else, when an incoming call is received:

*Jan 9 18:22:01.705 MET: ISDN Se1/0:15 Q931: RX <- FACILITY pd = 8 callref = N/A

Facility i = 0x91A129020200A402010C30200A01010A0101A014A012800D303033363330393431313431360A0103A1028200

Protocol Profile = Remote Operations Protocol

0xA129020200A402010C30200A01010A0101A014A012800D303033363330393431313431360A0103A1028200

Component = Invoke component, Unsupported operation

Called Party Number i = 0xC1, '48200621'

Plan:ISDN, Type:Subscriber(local)

*Jan 9 18:22:01.705 MET: ISDN Se1/0:15 Q931d: L3IF_rx_L2_pak: received data

*Jan 9 18:22:01.705 MET: 0800621C2C91A129020200A402010C30

*Jan 9 18:22:01.705 MET: 200A01010A0101A014A012800D303033

*Jan 9 18:22:01.705 MET: 363330393431313431360A0103A10282

*Jan 9 18:22:01.705 MET: 007009C13438323030363231

*Jan 9 18:22:01.705 MET: ISDN Se1/0:15 Q931d: L3_Go: source 0x020A, event 0xFFFFFFF9, call id 0x0000, int id 0x0

*Jan 9 18:22:01.709 MET: ISDN Se1/0:15 Q931d: L3_Go: event 0xFFFFFFF9 cr_len 0 cr 0

*Jan 9 18:22:01.709 MET: ISDN ASN1: isdnAsn1Component

*Jan 9 18:22:01.709 MET: ISDN ASN1:

:type=

*Jan 9 18:22:01.709 MET: ISDN ASN1: 161

*Jan 9 18:22:01.709 MET: ISDN ASN1: isdnAsn1Invoke

*Jan 9 18:22:01.709 MET: ISDN ASN1:

: invId=

*Jan 9 18:22:01.709 MET: ISDN ASN1: 164

*Jan 9 18:22:01.709 MET: ISDN ASN1:

: linkedId OPTIONAL, not set

*Jan 9 18:22:01.709 MET: ISDN ASN1:

: op=

*Jan 9 18:22:01.709 MET: ISDN ASN1: 12

*Jan 9 18:22:01.709 MET: ISDN Se1/0:15 **ERROR**: isdnAsn1Inv: error: unknown operation 12

*Jan 9 18:22:01.709 MET: ISDN Se1/0:15 **ERROR**: isdnAsn1Component: generated error 4:ASN1_MESSAGE_ERR_UNKNOWN_OP

*Jan 9 18:22:01.709 MET: ISDN Se1/0:15 **ERROR**: isdnAsn1Component: ERROR

*Jan 9 18:22:01.709 MET: ISDN Se1/0:15 **ERROR**: process_facility_supp_services: Facility IE operation unsupported

Thank you!!

Laszlo

4 REPLIES

Re: ISDN PRI E1 on incoming call says: isdnAsn1Inv: error: unkno

Hi Laszlo,

This is the piece of information causing the error messages:

Component = Invoke component, Unsupported operation

The ISDN switch is attempting to use some ISDN supplementary services in the facility message that IOS does not support and can not parse.

hth,

nick

Community Member

Re: ISDN PRI E1 on incoming call says: isdnAsn1Inv: error: unkno

Hello,

Thank you for your input.

I tried two other IOSs but was no help.

Finally, the PTT (T-Com) changed their ISDN PRI signalling somehow and it solved the problem, now works fine with incoming calls also.

It was not easy to have them do it...

Regards,

Laszlo

Community Member

I came across this post from

I came across this post from a Google search (and I realise it's many years old) when looking for some information on messages I was seeing when the ISDN was in a known diverted state.

 

If anyone else finds these messages, it's likely due to the Telco having a diversion on the entire service. Inbound calls are hitting the exchange port (which is causing the strange signalling) and then being diverted elsewhere.

 

Community Member

Had the same errors below and

Had the same errors below and yes, phones were diverted from provider.

Jan 19 2017 14:33:18.079 AEDST: ISDN Se0/0/0:15 **ERROR**: isdnAsn1Inv: error: unknown operation 12
Jan 19 2017 14:33:18.083 AEDST: ISDN Se0/0/0:15 **ERROR**: isdnAsn1Component: generated error 4:ASN1_MESSAGE_ERR_UNKNOWN_OP
Jan 19 2017 14:33:18.083 AEDST: ISDN Se0/0/0:15 **ERROR**: isdnAsn1Component: ERROR
Jan 19 2017 14:33:18.083 AEDST: ISDN Se0/0/0:15 **ERROR**: process_facility_supp_services: Facility IE operation unsupported

2647
Views
15
Helpful
4
Replies
CreatePlease to create content