07-05-2008 03:40 PM - edited 03-15-2019 11:45 AM
Hello everyone
I have one issue with the name display that i can't understand.
My config is that : CME(4.1) <==> PBX (4400)
The cme and the PBX are connected by 3 BRI and the signalling protocol used is qsig.
When i call a pbx phone from an ip phone, on the ip phone i see the name but on the pbx phone i only see the number.
Below the Q931 debug :
Jul 4 15:24:30.275: ISDN BR0/1/0 Q931: TX -> SETUP pd = 8 callref = 0x010A
Bearer Capability i = 0x8090A3
Standard = CCITT
Transfer Capability = Speech
Transfer Mode = Circuit
Transfer Rate = 64 kbit/s
Channel ID i = 0xA98381
Exclusive, Channel 1
Facility i = 0x9FAA068001018201018B0100A110020200E6020100800749542074657
374
Calling Party Number i = 0x0080, '7348'
Plan:Unknown, Type:Unknown
Called Party Number i = 0x80, '7329'
Plan:Unknown, Type:Unknown
Sending Complete
Jul 4 15:24:30.351: ISDN BR0/1/0 Q931: RX <- STATUS pd = 8 callref = 0x810A
Cause i = 0x80E41C - Invalid information element contents
Call State i = 0x06
Jul 4 15:24:30.371: ISDN BR0/1/0 Q931: RX <- CALL_PROC pd = 8 callref = 0x810A
Channel ID i = 0xA98381
Exclusive, Channel 1
Jul 4 15:24:30.411: ISDN BR0/1/0 Q931: RX <- ALERTING pd = 8 callref = 0x810A
Facility i = 0x91AA068001008201008B0100A11C02022EE106042B0C0901801041495
448414D4F55205261646F75616E
Progress Ind i = 0x8088 - In-band info or appropriate now available
Locking Shift to Codeset 5
Codeset 5 IE 0x32 i = 0x81
Jul 4 15:24:36.891: ISDN BR0/1/0 Q931: RX <- CONNECT pd = 8 callref = 0x810A
Facility i = 0x91AA068001008201008B0100A11C02022EE206042B0C0902801041495
448414D4F55205261646F75616E
Connected Number i = 0x0081, '7329'
Locking Shift to Codeset 5
Codeset 5 IE 0x32 i = 0x81
Jul 4 15:24:36.895: %ISDN-6-CONNECT: Interface BRI0/1/0:1 is now connected to 7
329 N/A
Jul 4 15:24:36.895: ISDN BR0/1/0 Q931: TX -> CONNECT_ACK pd = 8 callref = 0x01
0A
Jul 4 15:24:42.895: %ISDN-6-CONNECT: Interface BRI0/1/0:1 is now connected to 7
329 N/A
Jul 4 15:24:50.859: ISDN BR0/1/0 Q931: RX <- DISCONNECT pd = 8 callref = 0x810
A
Cause i = 0x809080 - Normal call clearing
Jul 4 15:24:50.863: %ISDN-6-DISCONNECT: Interface BRI0/1/0:1 disconnected from
7329 , call lasted 13 seconds
Jul 4 15:24:50.863: ISDN BR0/1/0 Q931: TX -> RELEASE pd = 8 callref = 0x010A
Cause i = 0x8090 - Normal call clearing
Jul 4 15:24:50.895: ISDN BR0/1/0 Q931: RX <- RELEASE_COMP pd = 8 callref = 0x8
10A
Cause i = 0x809080 - Normal call clearing
The only thing strange that i could see is : Cause i = 0x80E41C - Invalid information element contents.
But why i don't know.
If you could help me on this issue that will be very nice from you guys.
Thanks
07-06-2008 02:58 AM
Hi, "invalid information element" means the PBX doesn't like something in the call setup, the best way to deal with that is to compare with an incoming call and then adapt fields to be the same like the PBX sets them.
For the name issue, I suppose you have:
voice service pots
qsig decode
already configured ?
07-06-2008 07:25 AM
Hello
Thank you for your answer.
So it is possible to adapt the fields in the qsig message send by the cme? What kind of command could do this ?
Yes, qsig decode is configured but in the voice service voip.
Tommorow, i will do an inbound call to compare qsig messages. Do you know a qsig decoder?
thank you.
07-06-2008 08:57 AM
Hi,
no you cannot change anything in the QSIG portion. However it appears the names are OK in both directions. I know of no free qsig decoders around.
07-06-2008 03:17 PM
Providing you have IOS versions 12.4.4XC or later, the following commands normally allow the Calling name to be passed via Facility IE -
voice service voip
qsig decode
and under the D channel -
isdn outgoing ie facility
isdn supp-service name calling
Refer here for some more details -
http://www.ciscotaccc.com/kaidara-advisor/voice/showcase?case=K24001364
For your interest, attached is a very simple ISDN facility decoder. I used it to decode the following messages in the Q931 traces. You will need to rename it as a .exe file to allow it to be run under windows.
From the Setup message
0x9FAA068001018201018B0100A110020200E6020100800749542074657374
Decodes to "IT test"
From the alerting message
0x91AA068001008201008B0100A11C02022EE106042B0C0901801041495448414D4F55205261646F75616E
Decodes to "AITHAMOU Radouan"
To use the application, paste the Facility message block of hex after the 0x.
You then need to delete single characters at the start of the hex to remove the facility header. Generally after a few characters are removed at the start of the string the message starts making sense.
Simple ISDN facility decoder
07-06-2008 11:12 PM
Paul,
the fact is that he has already configured "qsig decode".
The other commands:
isdn outgoing ie facility
isdn supp-service name calling
Are on by default, in fact we can see that the name facility is passed in the router decode.
07-07-2008 12:45 AM
Hi Bevilcqua, Paul
In your response Paul, the url that you give, i think give me the answer of the issue.
The pbx is "perhaps" (not verified for the moment) configured with a different kind of QSIG.
The CME could decode ECMA QSIG and ISO QSIG, but send ISO QSIG that the pbx couldn't decode.
Do you know if it is possible to configure the kind of QSIG message send by the CME ?
My version is CME 4.1 and the ios is c2800nm-spservicesk9-mz.124-15.T3 .
Thanks for your help.
07-07-2008 12:49 AM
Raduane,
you're correct. A different qsig version could cause inability for the PBX to decode.
Unfortunately is not possible to change the format that the router is using.
07-07-2008 01:01 AM
CME interoperability documents are listed here - these may be useful in setting up your particular PBX :
I found some internal references about QSIG support, these may help indentify how to make the PBX interwork as well:
ECMA/ISO: Compliant QSIG supplementary services supported on PRI and BRI interfaces
ECMA-164: Calling Line/Name Identification (CLIP/CNIP)
ECMA-164: Connected Line/Name Identification (COLP/CONP)
ECMA-174: QSIG Call Forward Busy/No Answer/Unconditional (CFB/CFNA/CFU)
ECMA-178: Transfer by join (hairpinning)
ECMA-242: MWI activation/deactivation
11-20-2008 11:35 PM
Hi Paul
The ISDN facility decoder attachment you mentioned seems to have expired from the post.
Do you think you could reattach it?
Also, could I expect the decoder to decode QSIG facility messages?
Many thanks,
-Martin
Discover and save your favorite ideas. Come back to expert answers, step-by-step guides, recent topics, and more.
New here? Get started with these tips. How to use Community New member guide