Route on TGRP with stir shaken and pass all original parameters
Page 1 of 1
Route on TGRP with stir shaken and pass all original parameters
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"
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"
Last edited by NicoleTan on Tue Dec 19, 2023 12:47 pm; edited 1 time in total
NicoleTan- Number of Messages : 18
Point : 38
Registration Date : 2017-11-27
main script and the filter script
main script and the filter script
- Attachments
NicoleTan- Number of Messages : 18
Point : 38
Registration Date : 2017-11-27
Re: Route on TGRP with stir shaken and pass all original parameters
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
https://docs.telcobridges.com/ProSBC_With_Transnexus_Solutions
NicoleTan- Number of Messages : 18
Point : 38
Registration Date : 2017-11-27
Similar topics
» Script to route the call by otg from the calling parameters
» Script to route on TGRP integrated with C15 and ClearIP
» STIR-SHAKEN Top 10 FAQ
» How to Implement STIR-SHAKEN
» Top 10 SBC Use Cases #7, STIR/SHAKEN
» Script to route on TGRP integrated with C15 and ClearIP
» STIR-SHAKEN Top 10 FAQ
» How to Implement STIR-SHAKEN
» Top 10 SBC Use Cases #7, STIR/SHAKEN
Page 1 of 1
Permissions in this forum:
You cannot reply to topics in this forum