Route on TGRP with stir shaken and pass all original parameters

[NicoleTan]

When ProSBC passes the Invite to Stir/Shaken service provider (e.g. ClearIP, Neustar), in the 302 returned message, it will keep only the basic hearders and parameters.
Meaning, some specific parameters, e.g. cic, trgp, rn, npdi, calling_noa, callled_noa, trunk-context...
Also in the 302 message, it will replace the original contact number (normall it is the same as the From number in the Inivte) with the called number, which causes a confusion/wrong number in the Diversion header of the next Inivte from ProSBC.
So this script is to
1. Reserve all the original headers/parameters of the inbound Invite
2. Send the call to the Stir/Shaken service provider to get the token/signing
3. Match the routes by the TGRP value from the source Invite
4. Pass all the reserved original headers/parameters to the outbound Invites along with the token/signing.

To use these filters, add the following lines to main script (simple_routing.rb)
require 'process_ruri_tgrp'

 include ProcessRuriTgrp
 
 before_filter :method => :process_ruri_tgrp

 Add NAP columns: send_clearip_flag with YES|NO
 Add NAP columns: tgrp with Value like "TG999"

[NicoleTan]

main script and the filter script

Attachments

tgrp routing with stir shaken and pass all original parameters.zip tgrp routing with stir shaken and pass all original parametersYou don't have permission to download attachments.(6 Kb) Downloaded 2 times

[NicoleTan]

For the more common scenarios with ClearIP/Transnexus Robocall, Stir Shaken solutions, please refer to the TBWiki pages here:

https://docs.telcobridges.com/ProSBC_With_Transnexus_Solutions