E1 callerID sending troubles

Unanswered Question
Jul 31st, 2007

Dear Experts,


I had Cisco 2821(CCME) and Panasonic TDA-200 connected by E1. Calls correctly processed, but CallerID is not transfering through E1.


My configs and debugs:


mos2821v#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: 0x801F7FFF

Number of L2 Discards = 0, L2 Session ID = 6

Total Allocated ISDN CCBs = 0


mos2821v#sh run int s0/0/0:15

Building configuration...


Current configuration : 242 bytes

!

interface Serial0/0/0:15

no ip address

encapsulation hdlc

isdn switch-type primary-net5

isdn incoming-voice voice

isdn guard-timer 2000

isdn map address .* plan isdn type unknown

isdn sending-complete

fair-queue

no cdp enable

end


debug of call Panasonic->Cisco:


3w6d: ISDN Se0/0/0:15 Q931: RX <- SETUP pd = 8 callref = 0x001A

Bearer Capability i = 0x9090A3

Standard = CCITT

Transfer Capability = 3.1kHz Audio

Transfer Mode = Circuit

Transfer Rate = 64 kbit/s

Channel ID i = 0xA18396

Preferred, Channel 22

Called Party Number i = 0x80, '3219'

Plan:Unknown, Type:Unknown

4879650196255932416w12884901888d: ISDN Se0/0/0:15 SERROR: process_pri_simple: NO name in GTD

3w6d: ISDN Se0/0/0:15 Q931: TX -> CALL_PROC pd = 8 callref = 0x801A

Channel ID i = 0xA98395

Exclusive, Channel 21

4879650196255932416w12884901888d: ISDN Se0/0/0:15 SERROR: process_pri_simple: NO name in GTD

3w6d: ISDN Se0/0/0:15 Q931: TX -> ALERTING pd = 8 callref = 0x801A

Progress Ind i = 0x8188 - In-band info or appropriate now available

3w6d: ISDN Se0/0/0:15 Q931: RX <- DISCONNECT pd = 8 callref = 0x001A

Cause i = 0x819F - Normal, unspecified

3w6d: ISDN Se0/0/0:15 Q931: TX -> RELEASE pd = 8 callref = 0x801A

3w6d: ISDN Se0/0/0:15 Q931: RX <- RELEASE_COMP pd = 8 callref = 0x001A



I don't understand how to resolve this problem.


You can see error in debug:

SERROR: process_pri_simple: NO name in GTD

may be it is the main reason.


I wish you help me, thanks in forward. I'm waiting. Do you need additional information?

  • 1
  • 2
  • 3
  • 4
  • 5
Overall Rating: 0 (0 ratings)
Loading.
Paolo Bevilacqua Tue, 07/31/2007 - 04:58

Hello,


PBX is not sending calling number, there is nothing you can do about on the router, check why PBX is not sending calling number.

grievantony Tue, 07/31/2007 - 05:32

Sorry, here the correct debug:


w6d: ISDN Se0/0/0:15 Q931: RX <- SETUP pd = 8 callref = 0x0001

Bearer Capability i = 0x9090A3

Standard = CCITT

Transfer Capability = 3.1kHz Audio

Transfer Mode = Circuit

Transfer Rate = 64 kbit/s

Channel ID i = 0xA18396

Preferred, Channel 22

Facility i = 0x91AA068001008201008B0100A11A02014006042B0C0900800F53757261657620416C6578616E6472

Protocol Profile = Remote Operations Protocol

0xAA06800100820100

0x8B0100

0xA11A02014006042B0C0900800F53757261657620416C6578616E6472

Component = Invoke component, Unsupported operation

Calling Party Number i = 0x0080, '3131'

Plan:Unknown, Type:Unknown

Called Party Number

mos2821v# i = 0x80, '3219'

Plan:Unknown, Type:Unknown

3w6d: ISDN Se0/0/0:15 **ERROR**: process_facility_ie: Received unsupported Facility IE operation value 0

3w6d: ISDN Se0/0/0:15 Q931: TX -> CALL_PROC pd = 8 callref = 0x8001

Channel ID i = 0xA98395

Exclusive, Channel 21

3w6d: ISDN Se0/0/0:15 Q931: TX -> ALERTING pd = 8 callref = 0x8001

Progress Ind i = 0x8188 - In-band info or appropriate now available

mos2821v#

3w6d: ISDN Se0/0/0:15 Q931: RX <- DISCONNECT pd = 8 callref = 0x0001

Cause i = 0x8190 - Normal call clearing

3w6d: ISDN Se0/0/0:15 Q931: TX -> RELEASE pd = 8 callref = 0x8001

3w6d: ISDN Se0/0/0:15 Q931: RX <- RELEASE_COMP pd = 8 callref = 0x0001


You can see, that PBX sends only number but we can not see the name. and if i call from Cisco to PBX:


*in attachment*


And you can see that Cisco didn't send CallerID also. What is the problem?



Attachment: 
Paolo Bevilacqua Tue, 07/31/2007 - 06:09

Hello, it seems to me that PBX is using qsig signaling, configure that as switch-type and also configure:


voice service voip

qsig decode



grievantony Tue, 07/31/2007 - 06:28

Hm.


I had Cisco 2821 with Cisco IOS Software, 2800 Software (C2800NM-ADVIPSERVICESK9-M), Version 12.4(13b), RELEASE SOFTWARE (fc3)


And, Feature Navigator Tool points that there is no support of qsig supplementary servces in this model, there just 2801 of this series. Am I right?


I have no command "qsig decode" in "voice service voip".


I've changed signaling to primary-qsig, but it can't help.


Is there any way to resolve problem without upgrading software? And what software I need to use?

Paolo Bevilacqua Tue, 07/31/2007 - 07:25

Hi,


You need either a recent 12(4)T or even better, 12.4(11)XJ4. All the router models do the same services as these are purely software.


If you can configure the PBX to not use qsig, that may help. The router can send calling name as ISDN IE if you configure "isdn outgoing display-ie", but it is not said the PBX will accept it.


j.huizinga Wed, 08/01/2007 - 06:19

When connecting to a PBX make router and PBX talk QSIG. I have found that that working very well, including name support.



Jan

grievantony Wed, 08/01/2007 - 06:22

Do you have Panasonic TDA-200? So, in my practice I realize it with Nortel, Avaya and LG PBX. But I have troubles with Panasonic. Can you post here config of interface and ISDN service of you Cisco device?

Paolo Bevilacqua Wed, 08/01/2007 - 06:48

Be aware, there is even more than one variant (someone calls that version 2) of QSIG for encoded values. That is, ISO and ECMA. So you cannot say that all the QSIG installations are the same.

j.huizinga Wed, 08/01/2007 - 06:52

No I can not remember connecting to this specific model. But I remember that some time ago I had some problems connecting to a Siemens PBX using QSIG.


The issue is that on Cisco we configure for example: primary-net5 or primary-qsig. The people from the PBX world have much more options to configure an E1 PRI line.


To make work things well with this Siemens the Siemens people had to upgrade the firmware, apparently the QSIG from Cisco and Siemens was compatible enough to make calls but failed to pass the name. After the upgrade all worked fine.


I don't know if you talk with Panasonic, maybe they can tweak their configuration,


Jan




Actions

This Discussion