I wanted to know which format is used on calledPartyBCDNumber!
On calledPartyBCDNumber I have: 9183e31164280230. If this is BCD format, e is not part of BCD!
on Called Party BCD Number I have: 383c1146822003
Help :)
Hex e maps to digit c.
19776: ISDN Numbering format (E.164) in Wireshark does not support "d"
/*
* As per A.S0001 Called Party BCD Number
*/
static dgt_set_t Dgt_tbcd = {
{
/* 0 1 2 3 4 5 6 7 8 9 a b c d e f */
'0','1','2','3','4','5','6','7','8','9','*','#','a','b','c', 0
}
};
91 83 e3 11 64 28 02 30 xx 38 3c 11 46 82 20 03
Thank you Cuckc for your answer, but still is not clear to me why on field:
calledPartyBCDNumber : 9183e31164280230 ('e' is present, most probably this value is not in BCD format, event name is with BCD), but on
Called Party BCD Number : 383c1146822003 (which is correct based on your comment and based on BCD)
There is a sample capture (Camel_IDP.pcap) attached to 18485: Decode timeandtimezone syntax in CAMEL IDP message.
One field is a byte string (hex data) and the other is a formatted character string. Same data presented in two difference formats with a translation of the phone keys "a"-"e" hex value to letters.
The example capture does not include those keys in its data but you can see in the tree that the fields are two different formats.
calledPartyBCDNumber: a186808150047391
1... .... = Extension: No Extension
.010 .... = Type of number: National number (0x2)
.... 0001 = Numbering plan identification: ISDN/Telephony Numbering (ITU-T Rec. E.164 / ITU-T Rec. E.163) (0x1)
Called Party BCD Number: 68081805403719
---
calledPartyBCDNumber: a186808150047391
camel.calledPartyBCDNumber
a186808150047391
https://www.wireshark.org/docs/dfref/c/camel.html
camel.calledPartyBCDNumber calledPartyBCDNumber Byte sequence 1.0.0 to 4.4.7
---
Called Party BCD Number: 68081805403719
gsm_a.dtap.cld_party_bcd_num
68081805403719
https://www.wireshark ...Asked: 2025-06-13 08:33:26 +0000
Seen: 145 times
Last updated: Jun 13
