I used MTU to send a forwardSM message from my local end to remote end, and ROUTED THIS MESSAGE ON GT. Here is my configuration for GTT in my config.txt file: SCCP_GTT_PATTERN 1 0x10 0 0 0x001104 0987654321 SCCP_GTT_ADDRESS 1 0x03 2 7 0x00 - SCCP_GTT 1 R 1 I had been trying to use different called and calling party GT addresses in the mtu.exe command but it was not working; and then I found this thread and based my mtu.exe command on the one given at the end of the question in the thread, and it started working. Here is my mtu.exe command: mtu -d0 -a12080012049078563412 -g12080012049078563412 -i987654321 -s"Happy" I know that it started working because I could capture the request packet in Wireshark. It was great that it started working. But there is one confusion. According to my command: 12 - Address Indicator - 00001100 - i.e. "International Network ||| Route on GT ||| Global Title includes Translation Type, Numbering Plan, and Encoding Scheme ||| SSN Included ||| Point Code Included" 00 - Translation Type - 0000 0000 12 - 0001 0010 - Numbering Plan (ISDN/Telephony) and Encoding Scheme (BCD, even number of digits) 04 - 0 000 0100 - Nature of Address Indicator (International Number) 9078563412 - Address Signals in BCD BUT here is what the packet being sent looks like in Wireshark: If I was talking about the Destination/Called Party Address, then we could say that GTT (Global Title Translation) is making changes to the address, but I am talking about the Originating/Calling Party Address? So can someone explain to me how the values shown in the Wireshark map to the values in the Originating Address in my mtu.exe command?
↧