Hi everyone,
We're currently experiencing an issue where incoming texts to 3cx are showing up as coming from the wrong phone number. If for example, we send an outgoing text to a number who's last three digits are 311, when they respond it comes in as if it's from a completely different contact/phone number which happens to share the last three digits as the correct phone number/contact.
We use Twilio for our trunking and have had zero issues with how they are formatting and sharing information with the 3cx system which is how we know it's not on their end. The only way for us to verify who is actually texting us is actually to check the Twilio logs which always correctly show who actually sent the text, despite 3cx saying it's coming from a different contact/phone number.
We are struggling to resolve this issue as it seems to be possible the short codes are getting mismatched in 3cx, does anyone have any possible solutions or advice? Is it an issue on the backend with how short codes are being identified and associated with phone numbers in our system? Is this something we can adjust or has anyone had this issue? As we're growing our business it's becoming a much larger issue everyday as more phone numbers are put in 3cx and many will inevitably share the last 3 digits.
For reference we do have everything configured correctly for E164 format as this is required on Twilios end and must match formatting in 3cx as well.
We're currently experiencing an issue where incoming texts to 3cx are showing up as coming from the wrong phone number. If for example, we send an outgoing text to a number who's last three digits are 311, when they respond it comes in as if it's from a completely different contact/phone number which happens to share the last three digits as the correct phone number/contact.
We use Twilio for our trunking and have had zero issues with how they are formatting and sharing information with the 3cx system which is how we know it's not on their end. The only way for us to verify who is actually texting us is actually to check the Twilio logs which always correctly show who actually sent the text, despite 3cx saying it's coming from a different contact/phone number.
We are struggling to resolve this issue as it seems to be possible the short codes are getting mismatched in 3cx, does anyone have any possible solutions or advice? Is it an issue on the backend with how short codes are being identified and associated with phone numbers in our system? Is this something we can adjust or has anyone had this issue? As we're growing our business it's becoming a much larger issue everyday as more phone numbers are put in 3cx and many will inevitably share the last 3 digits.
For reference we do have everything configured correctly for E164 format as this is required on Twilios end and must match formatting in 3cx as well.
