When i make a call that from 1016 to 1015 ,and my voip phone support msrp,so i want to send text-message form one leg to the other. I find that FreeSwitch handle the incoming message as a normal sip invite and will generate a session (also a channel)instance for the invite i make.The channel state is set to CS_NEW,then it into the sofia state callback to handle the different stage of sip procedure.When the sdp is parsed ,the freeswitch tell me the sdp is not match,so the session is turn off and the channel is hungup.I don't know how to configuration(if the freeswitch support msrp),or how to make this right.Thank you very much if you can give me more infomation.
I would suspect that you might be running an older code base that doesn't have MSRP support it was only recently added to FreeSWITCH in JIRA FS-3748 (DEC-2011). If you're running the latest code then the proper course of action would be to reopen FS-3748 (http://jira.freeswitch.org/browse/FS-3748) and report your findings on the JIRA and seek a possible fix.
StackOverflow isn't the proper location to report bugs.
Thanks,
Brian West
FreeSWITCH.org
Related
I tried to send a SMS with APDU (without the 23.048 headers - I know it doesn't suppose to be without those headers).
For every SMS (no matter what the APDU I sent) I got the 9000 response (no additional data even if setting the Le byte).
Can someone please explain this behavior to me?
So I got the answer from the GlobalPlatform mailing list -
For any event in the UICC, the card will trigger all the applets registered to the event or the applet specified by the TAR. If no applet registered to the event the UICC will act as the process done successfully - because no error or unpredictable behavior occurred.
As per the question title, I've integrated Twilio and Zendesk with Smooch. I can send SMS to my Twilio number and receive this in Zendesk, however when I reply to the ticket in Zendesk the reply just goes to space and doesn't reach the number that initiated the ticket.
I've removed all integrations in Smooch and added them back in with no success - I have no idea what to. I have upgraded my Twilio account from the trial to a paid one, whereas my Zendesk account is a trial account.
I've tested this to/from SMS using Slack in lieu of Zendesk and I have a similar problem i.e. I receive the SMS in Slack but cannot reply. The only way a reply works is when I use "/sk" followed by the reply. Is there something similar that has to happen when replying to SMS generated tickets in Zendesk?
Any help would be much appreciated!
OK so after a bit of investigating what I have found is that the automatic integration Smooch setup in Zendesk didn't work properly. This is because the trigger Smooch applied was based on the incoming SMS having a tag=smooch. The Trigger that was set up was based on the tag=smooch...something else (I can't remember what it was).
I changed the trigger value to be tag=smooch and now I can respond to SMS received in Zendesk.
I wasn't able to reproduce your issue.
When Smooch configures the trigger on Zendesk that allows the agent to respond to the customer, it doesn't check for equality with "supportkit smooch", it checks whether the ticket has a tag that is "smooch" OR "supportkit".
So it's unlikely that editing the condition solved the problem, unless it had been previously manually changed for some reason.
Maybe you were just unlucky. If you encountered your issue around August 22, 2016, it's may be that Zendesk had trouble fulfilling trigger actions at that time (https://twitter.com/ZendeskOps/status/767850822038351872).
Alternatively, perhaps you did your initial testing with a Twilio trial account and responded to a number other then the one that was used to set up the account. In that case Twilio will not deliver messages.
Note on /sk:
Using a slash command is the only way for an agent to respond to the customer on Slack, otherwise you're just writing into the Slack channel for your team's benefit. The equivalent to the slash command in Zendesk is just responding to the ticket.
I've been using Twilio to send SMS and things work great. The only issue is that Twilio charges for both outbound and inbound messages. As such, we've been looking for other solutions.
We thought we found it with Plivo as their pricing was more favorable for SMS.
However, with Plivo, very quickly our outbound messages are being marked as spam or something and they're not being delivered.
We are sending the exact same message every day to about 5k users at a given time in the day. The message has a url in it, but it is something our users signed up for.
Two questions:
1. Why does everything work on Twilio and not on Plivo?
2. Is there a code change I can make to ensure our outbound messages sent with Plivo are not marked as spam by carriers and then stopped?
You need to contact Plivo about this. I experience this problem too. Their carrier mark our number as spammer since we are sending almost the same messages (verification). They called their carrier and our number was white-listed.
Plivo Sales engineer here. This is indeed an issue with the carrier marking your messages as spam. We can definitely help you overcome this. Could you please drop an email to ramya(at)plivo.com and we can sort this out?
You need to contact with Plivo support , there may be problem for number prefix for country like if you are using twilio you have to add +(with country prefix) but not in Plivo. It will be better to contact with Plivo support.
Thank You
I dont know how Pilvo work but usually with SMSC there is Message Queue associated sometimes with each SMPP Client and also with Mobile Station. You can't always send messages until your certain number of request are still pending. there is a specific error code that SMSC sent to its client about message queue overflow.
BADABING BADABOM! After having a look in the Plivo administration I noticed a new option under other-settings "Automatic Encoding Of Unicode Characters". As Norway uses inernational characters this is definately a setting for me, and after enabling it all SMS are delivered as expected. So remember to enable this setting.
MAKE SURE TO ENABLE THIS:
Path: Plivo admin / Messages / Settings / Other settings
Feature: Automatic Encoding Of Unicode Characters -> Enable
I am making an event organisation platform. Whenever user creates an event, the candidate gets an email notification as well as sms notification asking whether the suggested time fits or not. The problem is that since it is event organisation, there may be more than one occurance of candidate's mobile phone. So I need to have some unique information to identify to which event candidate is responding to.
I have tried identify using Message SID, but then I realised that Message SID is different on reply message.
So my question would be: is there any way to authenticate to which message candidate is replying to?
Hi Twilio developer evangelist here.
Because every message is idempotent, you wouldn't be able to track them just via the call sid. however, there's way to get around that such as passing a code that goes with each message which you can then read, or using cookies.
I think you are probably going to be more successful using cookies, and luckily enough there is an article on twilio's website that describes just how to do that. And because I noticed you're using PHP, I'm pointing you directly to the PHP article on tracking SMS conversations.
Hope this helps you
I am trying out different things with Twilio, but open for other solutions with Nexmo, Tropo or Plivo.
Here's a situation, I am sending an SMS texts from a server to bunch of clients. I can get a status back: like queued, sending, sent, or failed. Here's what Twilio says about SMS sent status:
"Sent" indicates that your message was successfully sent into the SMS
network for delivery. However Twilio does not receive confirmation from
the destination carrier that the message was received, and this is not
a guarantee that the message has reached the intended device.
(https://www.twilio.com/help/faq/sms/what-do-the-sms-statuses-mean)
So, my question is: does Plivo, Tropo or Nexmo (or any other service that I missed) do anything like that? I mean, knowing that an SMS was received either by client directly, or client's carrier would be really important.
PS. I'm not even sure if it is possible
Any help or suggestions would be appreciated.
It's certainly possible with Nexmo - as the other answer and comment state, it's not possible with Twilio & Tropo. Plivo's docs look like their delivery receipts are similar to Nexmo's.
Nexmo sends a delivery receipt if it's supported by the carrier. In the US it's not, but internationally it is supported often. In those cases Nexmo will give your app a callback with a delivery receipt. You can also use the message ID to query for the message status.
This screencast shows checking the DLR from the dashboard, which is really just a UI on top of the API.
Kevin makes the point that this could be difficult if the message is bounced through multiple providers - one of Nexmo's focuses is getting as direct a connection as possible.
[Disclaimer: I do occasional developer evangelism for Nexmo.]
I'm a Tropo customer, and I've asked the same question, and so far, the answer's similar to what Kevin Burke gave for Twilio. It's hard to do, so there's no confirmation at this time. They do give some debugging information in the logs which is helpful with that first-hop negotiation, at least, even if it's hard to retrieve/parse easily. They are working on it, and have been very active adding new features.