My setup a bunch of SIP phone numbers I own that forward to an external phone number. For example, I own 2222222222 on our SIP Trunk. We then have a translation pattern that translates the called number to “3333333333”, which is an external number for our CRM.
Call example: 1111111111 (MyCell phone) calls 2222222222 (My owned phone number), gets translated to 3333333333 (CRM owned phone number)
- 1111111111 (My Cell phone) to 2222222222 (My owned phone number)
From: " CALL "<sip:1111111111@voip.centurylink.com;user=phone>;tag=****************
To: "2222222222 2222222222"<sip:2222222222@voip.centurylink.com;user=phone>
- 1111111111 (My Cell phone) to 3333333333 (CRM owned phone number)
From: " CALL " <sip:+11111111111@voip.centurylink.com>;tag=*****************
To: <sip:93333333333@10.4.221.8>
Since “1111111111” is not a valid phone number on the SIP trunk, it’s shown as an Alien TN and shows as a unique line on our billing. This causes our bills to have thousands of Alien TN’s and has become a billing nightmare.
Is there anything we can do with our SIP messaging (ie SIP diversion header), to fix this? I’m not great with SIP messaging, but maybe the second SIP message can be from the 2222222222@voip.centurylink.com user, but somehow still preserve the unique calling number?
