Phones behind SBC not following caller ID rules

[VISA MC]

I have a customer site that is using an SBC. The extensions are in a group called Store 3 and use an outbound caller ID set at the extension level. When I provision my app or a STUN extension, it works properly, but behind the SBC phones are displaying the wrong outbound caller ID. Has anyone seen this before?

 

[Evolute IT]

Please provide the informations specified here : https://www.3cx.com/community/threads/information-to-provide-when-requesting-help.67558/

I never had this issue but : what caller ID does it shows? And is this only for internal or external calls or both?

 

[leejor]

What caller ID are they sending? the "main" (trunk) number, or that of another extension? Have you compared working and not working, Activity Logs?

 

[VISA MC]

3CX Version, Standard Annual 16.0.3.676

• Server OS, Debian 9
• Is the 3CX Server Hosted and where? Yes AWS
• IP Phone Make/Model/Firmware GRANDSTREAM GXP2130 1.0.9.135
• Provisioning Method:SBC
• Trunk Provider or Gateway Make/Model Callcentric
• Has the Firewall Checker passed: YES
• Are custom Phone Templates being used: YES
• 
  So there are two trunks, Store 1 and Store 3. Both callcentric. I have OB rules set so that the group Store 3 uses the Store 3 trunk and I have the OB Caller ID set as one of the DID’s on the account at Callcentric
• The caller ID being sent out is the main trunk number from Store 1. I have verified the calls are being routed through the correct trunk. Everything was displaying fine when these were STUN phones but after installing the SBC they seem to be ignoring the outbound caller ID set at the extension level.
  

 

[AWS2P]

you said it was good caller ID sent when APP is used, is App on the same extension as the one behind SBC and not working ?
if so did you check in extension settings for both App and Phone if Caller id is the good one set.
You also said when i use STUN it works, which extension do you use with STUN ?

Since when do you use SBC instead of STUN? is it few days? weeks? months?

 

[leejor]

The SBC should not be modifying the Invite, which would contain the caller ID. You may need to install one set, at the site, using STUN (as a test), to compare the Activity Log and/or Wireshark, of a working and non-working call.