-
Notifications
You must be signed in to change notification settings - Fork 129
SCCP module does not support the ANSI / T1.112 address layout #236
Comments
I wanted to chime in with my findings to avoid lost time. I checked T1.112 (ANSI) and Q.713 (ITU-T) and ANSI has the "SSN Indicator" and "Point Code Indicator" reversed as compared to the ITU-T standard. I will start by a simple patch to reverse these fields and will comment back here. If I need to make other changes, I will mention them here as well. |
Alright, the patching approach worked. I went up the chain of function calls and changed the items I needed to change in This last patched class was modified to call my modified
and
It is a bit of hacking but it works well! I haven't looked at other differences between T1.112 and Q.713 flavors of SCCP because I was only after getting the calling and called SSN's. Hopefully this can be useful for others! |
Thanks for the analysis. |
May I had @davidlag-telus, that if you can share (privately if needed) a tiny ANSSI SCCP pcap, this would help a lot. |
Hi,
I am trying to extract the SSN's from the SCCP layer. So far, I tried these (just for CallingPartyAddr, same for CalledPartyAddr anyways):
sccp_message["CallingPartyAddr"].show()
The SSNInd value above is incorrect because the SSN is really present.
sccp_message["CallingPartyAddr"]["Value"].show()
Same comment as above regarding the SSNInd value.
sccp_message["CallingPartyAddr"]["SSN"].show()
The SSN value is either not shown or is set to 0. I don't know if the SCCP flavor we use (ANSI) makes a difference here. I had to patch the ANSI version of MTP3 to get the point codes. Maybe I have to do the same here?
Thank you!
The text was updated successfully, but these errors were encountered: