Create a new RestComm Extension that extends the current data model to support storing the above Default Account Routing parameters for Voice and SMS.
If SMS routing instructions are present, RestComm will add a TLV field to the message called “destination_network_id”. This will correspond to a given subnetwork on the SMSC Cluster downstream (see architecture diagram below). The SMSC will read this value and route it to the proper network. If the network is invalid, the SMSC will attempt to deliver the message to the default network.
If Voice routing instructions are present, RestComm will add a custom Route Header to the SIP message (specific header TBD) so that the downstream provider can read this message and route traffic accordingly.
Have the ability to turn on or off the new RestComm extension
@gvagenas assigning this to you for the spec work, then we can break up into multiple issues as need be for @abdulazizali77 to start work on.
Create a new RestComm Extension that extends the current data model to support storing the above Default Account Routing parameters for Voice and SMS.
If SMS routing instructions are present, RestComm will add a TLV field to the message called “destination_network_id”. This will correspond to a given subnetwork on the SMSC Cluster downstream (see architecture diagram below). The SMSC will read this value and route it to the proper network. If the network is invalid, the SMSC will attempt to deliver the message to the default network.
If Voice routing instructions are present, RestComm will add a custom Route Header to the SIP message (specific header TBD) so that the downstream provider can read this message and route traffic accordingly.
Have the ability to turn on or off the new RestComm extension
@gvagenas assigning this to you for the spec work, then we can break up into multiple issues as need be for @abdulazizali77 to start work on.