Question

A CUBE terminates SIP trunks for two different ITSPs. ITSP-A requires the outbound INVITE to use the domain 'itsp-a.com' in the SIP From and Contact headers, while ITSP-B requires 'itsp-b.net'. Both providers reach the internet through the same egress dial-peer configuration style, but they are separated using 'voice class tenant 100' and 'voice class tenant 200' referenced under their respective outbound dial peers. You have written two separate SIP profiles that rewrite the domain. Where must these SIP profiles be applied so that each ITSP receives only its own domain rewrite without affecting the other trunk?

Accepted Answer

Associate each SIP profile inside its matching 'voice class tenant' using 'sip-profiles <n> outbound', so the profile follows the tenant bound to that dial peer

Answer

Apply each SIP profile globally under 'voice service voip' with 'sip-profiles' so all outbound INVITEs are normalized consistently

Answer

Apply both SIP profiles under the inbound dial peers, since domain rewriting must occur before digit analysis

Answer

Apply the SIP profiles under 'voice class uri', which controls which headers are matched and rewritten per provider