SMS to Main Number Routing

Status
Not open for further replies.

jestruch

Gold Partner
Advanced Certified
Joined
Sep 9, 2019
Messages
12
Reaction score
6
I have seen/read that 3cx does not allow separate SMS routing anymore. All routing follows the inbound route destinations now. I find it very strange the 3cx does not allow this anymore. Many customers have their Main number that routes to an IVR. With the latest 3cx update there is no way for the customer to receive SMS/MMS to their main number that routes to an IVR anymore, unless I am missing something? I see this as a big potential issue for many customers as many like to receive SMS to their main number but that main number also uses an IVR. Is there any workaround for this or is 3cx not going to support different SMS routing anymore?

Thanks,
Justin
 
This is definitely going to be an issue. Glad we tested this deployment to only one instance. So what was functional before becomes very unfunctional. Many companies want sms on their main numbers which route to ivrs/queues/etc. Sms word for this before, so why they'd remote this now makes no sense.
 
Can you also make the provision the same as it was in the terms of app id and token, not bandwidth user name and password. Using a user name and password becomes an issue for 3cx partners who are reselling voice services. Thanks for the quick reply Nick.
That's with Bandwidth. It's a Bandwidth problem, not 3CX.

Twilio uses API, Telnyx, Skyetel, Voxtelesys, etc.

Only Flowroute (one callback per account) and Bandwidth (what you said) has messed up ways of doing SMS.
 
Bandwidth does app ids with api's. it just needs the account id on the old messaging. On the new configuration, it wants the bandwidth user info with app id.
 
With Bandwidth, you can create API only users so that systems do not share credentials, but you currently cannot limit them by Sub-Account or Location.
 
  • Like
Reactions: Evolute IT
With Bandwidth, you can create API only users so that systems do not share credentials, but you currently cannot limit them by Sub-Account or Location.
this is correct, however with the new update it wants user names and password
 
this is correct, however with the new update it wants user names and password

These API only users will have a Username and a Password. They don't have access to the Dashboard, only API access.
 
FYI if anyone needs a temp workaround whilst 3CX fixes this issue, I have managed to get SMS useable again by doing the following
  1. Send the DiD to a new 'dummy' queue with all the members you need to have access to the SMS,
  2. Set the ‘Destination if no Answer’ to route to the IVR it should normally route to. (The queue is Prioritised hunt in my scenario)
  3. Now Log all users out of the 'Dummy' Queue you just created
  4. Test DiD and SMS.
Essentially the queue passes the voice call immediately to your IVR and the SMS routes to the queue

Hope this helps a few of you, ...

Tony Cave
Servcomm
 
  • Like
Reactions: accentlogic
@Tony Cave That's a smart work around thanks for this!

@Nick Galea Thank you for understanding. I think this will benefit many customers. Cheers.
 
  • Like
Reactions: N_G
Reading through all these, i see the workaround but has 3CX ever solved this issue, because i don;t understand why the SMS is not working when calls are sent to IVR??? everything is setup correctly. And btw this is a workaround, however 3cx only allows 5sec minimal for No answer in the Call queue, that is way to much to have the customer wainting on the line for regular calls. I need help ASAP
 
Reading through all these, i see the workaround but has 3CX ever solved this issue, because i don;t understand why the SMS is not working when calls are sent to IVR??? everything is setup correctly. And btw this is a workaround, however 3cx only allows 5sec minimal for No answer in the Call queue, that is way to much to have the customer wainting on the line for regular calls. I need help ASAP
I believe this has been answered here: https://www.3cx.com/community/threa...low-different-destination.118383/#post-570828
 
Status
Not open for further replies.

Forum statistics

Threads
112,065
Messages
590,592
Members
165,019
Latest member
rsaldin@advancedbrainspin