SS7 ISUP

As part of the PRI test effort, I worked alongside the ISUP developer to test the code. We did this by executing scripts I wrote on a protocol analyzer and verified correct ISUP mapping, both mandatory and optional messaging including coding of the entire service information (SIF) field of a message sending unit (MSU). Sometimes, two protocol analyzers were needed in order to generate the necessary backward response such as error conditions and timer tests.

This part of the test effort was fairly straight forward since I already had most of the scripts written for the valid message cases, I just copy-pasted them into the ISUP test folder and made minor changes to them. For error conditions, clearing, timers, link failure/maintenance, MF (non-ISDN) trunk interworking and link maintenance tests, I wrote additional scripts.

Tests requiring use of the Tekelec Message Generator Traffic Simulator (MGTS) had to be kept to a minimum since that was a lab resource in high demand. So, I did the best I could with a pair of ISDN PRI protocol analyzers and only when absolutely necessary did I get time on the MGTS to test protocol scenarios for which there was no other tool available.