If anyone is using Sangoma Talk with SipStation SMS can you test something for me? I do not have SipStation, and I want to know if it’s an issue with them also. I know SMS messages work, and you can receive a picture via MMS, but if you receive an MMS with text, do you get the picture and text or only the text? I am asking only about incoming messages specifically to Sangoma Talk on a cell phone, not to UCP, the Sangoma Phone app, or the web app. Yes, it should work, but I needed it confirmed that it actually does in Talk. Thanks!
We use Sangoma Talk here, both with the mobile and desktop client. We have the txt/mms set to go to multiple Sangoma Talk mobile phones (ie, the goal is to have an central phone number that go to multiple IT phones).
Based on my testing, inbound MMS doesn’t show up in the Sangoma Talk Mobile app. But I do see it on the Desktop client. If I send an image outbound MMS, it does go out, but the other phones don’t see the image.
I’d have to check with some of our staff that have a dedicated number, and see if it works for them.
Hopefully this helps.
Chris
Yes, it does. Thank you for letting me know that. Long story, but I do not have SipStation, but I do have SMS through a 3rd party. Incoming MMS to a Talk user will only show up if you send the picture without text, but it shows up in UCP and in the phone app/web app. I believe this is a bug with Sangoma Talk mobile or the SMS module, not the 3rd-party module. I have been going back and forth with Support on this, asking them to test it with SipStation to see if it’s a bug in the commercial SMS or Sangoma Connect modules because I don’t think it’s an issue with the 3rd pary module because it works fine in UCP and the phone app/web app, but they’ve refused to test it because I mentioned I was using a 3rd-party module for the trunks. Even though I kept telling them I was not asking them to test the 3rd-party module, but to test it with SipStation. The only way I could prove it one way or another was either to buy a SipStation trunk, numbers, and go through all the red tape to set up SMS on it, or see if someone who already has it can test it and see if my suspicion is right, so that test was very helpful. If that is something you find important, I would submit a commercial ticket. Thanks.
It’s not critical for us, but definitely looks like a bug. Considering it works in the desktop client.
Chris
I don’t have SipStation but as the author of the SMS Connector module you’re using, I confirm your findings. I investigated it a long time and concluded the issue was with the Talk mobile app since it does work everywhere else. If I send a photo and text in the same message from my cell phone, it is received as a photo and text in UCP, Sangoma Phone desktop app, and even the ClearlyAnywhere app. Only in Sangoma Talk is the message broken (I only receive the text, not the photo).
As a workaround on mobile, you can load the Sangoma Chat app, which connects to the PBX in the same way as Sangoma Phone desktop (username/password login, PBX hostname port:6443). MMS work correctly here. It has a few other features too, but not the main feature: making phone calls. So you have to keep both Talk and Chat on your mobile to both have working MMS and use the phone.
I am a bit honored you replied. Yes, and I left a message on GitHub about it also. I wrote the Clearfly provider, but I never finished the instructions, so I apologize for that. Thanks for the description; that confirms what I thought. I didn’t bring it up on GitHub sooner because I didn’t want to waste your time, and after reading through the code, it didn’t make sense to me that the issue would have been the module. I have been going back and forth with support (I never mentioned it was your module until my Sangoma rep mentioned he had recommended it to other clients), but all I ever asked them to do was test it with SipStation. I have my rep now involved, and he is just as difficult. If it comes down to it, I will provision a trunk, set up a number, test it, then get back with support using only their products to have them open a Jira ticket to get it fixed. I never thought about the chat app; we only had one customer who wanted the chat feature, and I kind of forgot it also supports SMS. We have a customer who depends on being able to do pictures, and the one-app-does-all idea is appealing, so I am trying to get this to work. Thanks for the module; at some point, I am hoping to contribute to it.
Recommended to test this with a real MMS containing both a photo and some text. If Sangoma Talk is only showing the text while dropping the image, that would point more toward an MMS handling issue in Talk rather than SipStation itself. ![]()
I completely agree with you, but commercial Sangoma Support refuses to test it or even look at it because I am not using one of their commercial supported carriers, even though the issue is not related to the carrier. Even though the issue clearly has to do with their commercial module that is not open source, because it originates from a 3rd-party module, they will not do anything. They told me that once I buy a SIPStation trunk and use all Sangoma-supported modules, they will look into it. Aside from using an approved carrier, I am not sure how I would test it with only Sangoma modules. Unbelievably, Sangoma Talk does not support the Chat feature. (That may be the root of the issue)
We use Sangoma Talk with both the mobile and desktop clients. It was recommended to us by Sangoma management as a replacement for UCP texting.
Unfortunately, I cannot recommend Sangoma Talk. In our experience, it has been very unreliable, and the bugs we have reported have not been handled or resolved satisfactorily.
I use it - how can I help?
If you want to see the bug, have someone send a text, then a picture, then a picture with text. You will see the text works, and the picture works, but the picture with text will only display the text. Sangoma will not address this issue unless the support request comes from a user with SipStation, even though the issue is neither carrier-related nor related to a 3rd-party module. If you would like to see this resolved, put in a support ticket to address it. Maybe if more than one person submits a ticket, they will take it seriously.
I have spent my own personal money on a trunk, and I am going through the 10DLC complete nonsense, wasting more money and time, wasting my own funds just to submit an official ticket. I am going to raise hell with my rep on this. Utter nonsense to just put in a ticket.
I have reported this issue multiple times and provided evidence and logs. There are also other similar issues where only a question mark appears instead of the picture.
I currently have an active ticket that has been escalated, but it has now been about a month without any answer.
I am a SipStation customer.
Thanks, I actually ended up buying a trunk and going through all the 10DLC nonsense at my own expense to test it, so I could also put in a request that they would listen to. Hopefully more requests will get something to happen. I also noticed that for the SIPStation MMS, the pictures show up as “Document” and you cannot open them, but with the 3rd-party SMS Connector module, the pictures actually work. LOL, the 3rd-party module works better. However, if you send a picture with a text message, the picture doesn’t go through. It’s very frustrating because the issue has nothing to do with the provider or the module supplying the request; there is no logical reason I’d need to do that other than them trying to avoid the request. My initial question was: Is there a known issue? They could have just said yes, and I would have left it. But no, they just kept arguing that because of the 3rd party module, they would not answer me. Very frustrating. So I couldn’t submit a request until I had a SIPStation account, even though SIPStation has nothing to do with my issue.