TIPS Change Outgoing CID

[kameleon]

I am combining a couple of old IncrediblePBX boxes on to a newer one I have to simplify administration amongst other things. I am running into an issue with outbound trunk not taking the caller ID I give it on one trunk. On my IncrediblePBX 16-15 I have a skyetel trunk I only use it for outbound calls, I have IPCOMMS as all my inbound calls. On the skyetel I have the outbound caller id set to be the number from the IPCOMMS side so I only have to present customers one phone number and not confuse them. However when I set this trunk up on my newer IncrediblePBX 2020 box it does not take the caller ID I give it, it takes the trunks number which would confuse customers. I have made everything I can find match between the old and new systems. What am I doing wrong?

 

[atsak]

Whats' the caller ID on the extension you're using to make the call?

 

[wardmundy]

Restricting outbound CID to your trunk's CID might also be the result of your provider's Stir/Shaken implementation. Unlike some providers, VoIP.ms is a bit more flexible by letting you use any trunk CID registered with them as well as any other number that you have previously verified with them in Account Settings -> General -> CallerID Number:

 

[kameleon]

Whats' the caller ID on the extension you're using to make the call?

All blank so should be taking what is configured for the trunk right?

 

[kameleon]

Restricting outbound CID to your trunk's CID might also be the result of your provider's Stir/Shaken implementation. Unlike some providers, VoIP.ms is a bit more flexible by letting you use any trunk CID registered with them as well as any other number that you have previously verified with them in Account Settings -> General -> CallerID Number:

View attachment 5175

Good point. The old system is on a skyetel account that is 3+ years old where the new one is less than a year old. That may have something to do with it although both new and old have the same STIR/SHAKEN info.

 

[Samot]

Good point. The old system is on a skyetel account that is 3+ years old where the new one is less than a year old. That may have something to do with it although both new and old have the same STIR/SHAKEN info.

None of this is STIR/SHAKEN related based on the data so far. What CID option is set for the trunk? It needs to be forced to "Force Trunk CID". The default setting just passes any CID that has already been set in the call progress.

 

[kameleon]

None of this is STIR/SHAKEN related based on the data so far. What CID option is set for the trunk? It needs to be forced to "Force Trunk CID". The default setting just passes any CID that has already been set in the call progress.

Outbound Caller ID is set to the BUSINESS NAME <+1XXXXXXXXXX> and the CID Options is set to Allow any CID. This is for Skyetel and is outbound only. Same settings I have on the old server. I will test tonight after close of business to "Force Trunk CID" and see how that works.

 

[wardmundy]

If it's an IPCOMMS number being set as Outbound CID on a Skyetel trunk, that sounds pretty stir/shaken to me unless you've verified the IPCOMMS number with Skyetel.

 

[Samot]

If it's an IPCOMMS number being set as Outbound CID on a Skyetel trunk, that sounds pretty stir/shaken to me unless you've verified the IPCOMMS number with Skyetel.

STIR/SHAKEN doesnt set callerids. It doesnt manipulate the callerid at all. An IPCOMMS number as the CID on a Skyetel trunk = B level per S/S.

 

[kameleon]

So here is the thing: on the old system (and new for that matter) it is using GV to ring an IPCOMMS number on the PBX. That is the incoming route. Then I use Skyetel to do outbound. The GV number that is the business number I am wanting to be displayed as the CID no matter what trunk I am using. On the old system this works as expected. The new, even with exact same settings, does not.

I tried the forced CID setting and no dice. Same thing, shows the skyetel DID number instead of what I need shown. The only thing I can think of that is different between the two is the old 16-15 server has the Skyetel setup with the 6 or so sip trunks, one for each region. The new is using the single pjsip trunk. Inbound calls work great but I cannot for the life of me get the caller ID on the new one to work the way it does on the old one for outbound.

 

[atsak]

Drop that + from the CID field.

 

[wardmundy]

So here is the thing: on the old system (and new for that matter) it is using GV to ring an IPCOMMS number on the PBX. That is the incoming route. Then I use Skyetel to do outbound. The GV number that is the business number I am wanting to be displayed as the CID no matter what trunk I am using. On the old system this works as expected. The new, even with exact same settings, does not.

I tried the forced CID setting and no dice. Same thing, shows the skyetel DID number instead of what I need shown. The only thing I can think of that is different between the two is the old 16-15 server has the Skyetel setup with the 6 or so sip trunks, one for each region. The new is using the single pjsip trunk. Inbound calls work great but I cannot for the life of me get the caller ID on the new one to work the way it does on the old one for outbound.

Have you called the Skyetel support folks??

 

[kameleon]

Have you called the Skyetel support folks?

Not yet. Honestly I don't like the whole $25/month minimum now as previously I could load $25 and go 5 or 6 months on that. So I am just moving one of my lines over to the newest Skyetel account I have that still has a good bit of money on it so I can drain it as they won't do refunds. I am working on moving/adding some other lower cost trunks to replace skyetel in the background while this drains. I should be able to get another 2-3 months out of them before I have to swap.
I did get it working though. I don't know what exactly fixed it but it is doing correctly now. I do plan to spin up a newer 2027 server and do the whole setup from scratch following the "

Building a Dirt-Cheap Communications Platform with VoIP" way so hopefully I won't have to deal with this again. Thanks for all the pointers!​

 

[JohnEasterling]

Not yet. Honestly I don't like the whole $25/month minimum now as previously I could load $25 and go 5 or 6 months on that. So I am just moving one of my lines over to the newest Skyetel account I have that still has a good bit of money on it so I can drain it as they won't do refunds. I am working on moving/adding some other lower cost trunks to replace skyetel in the background while this drains. I should be able to get another 2-3 months out of them before I have to swap.
I did get it working though. I don't know what exactly fixed it but it is doing correctly now. I do plan to spin up a newer 2027 server and do the whole setup from scratch following the "

Building a Dirt-Cheap Communications Platform with VoIP" way so hopefully I won't have to deal with this again. Thanks for all the pointers!​

Any update?