July 6, 2017 at 5:33 am
Hi All
When sending an SMS text message from SQL Server using the below. Exec msdb..sp_send_dbmail
@recipients = 'mynumber@sms.com'
, @profile_name = 'ProfileName'
, @body_format = 'TEXT'
, @body = 'TEST'
The SMS message I get on my phone is : VEVTVA=
Why would this be happening?
When emailing the message to myself, it comes through correctly.
Thanks
July 6, 2017 at 5:53 am
SQL Server can't send SMS's. I assume that you are using a 3rd party application that then transforms the received email into an SMS, and sends it to the related phone number for that email address.
I would probably talk to your 3rd party application provider, and and see if they can debug the problem.
Thom~
Excuse my typos and sometimes awful grammar. My fingers work faster than my brain does.
Larnu.uk
July 6, 2017 at 12:22 pm
SQLSACT - Thursday, July 6, 2017 5:33 AMHi All
When sending an SMS text message from SQL Server using the below.Exec msdb..sp_send_dbmail
@recipients = 'mynumber@sms.com'
, @profile_name = 'ProfileName'
, @body_format = 'TEXT'
, @body = 'TEST'The SMS message I get on my phone is : VEVTVA=
Why would this be happening?
When emailing the message to myself, it comes through correctly.Thanks
what happens if you add a second email to the recipeints list, do you get the actual reslult or do you get VEVTA== ? also, if you change the body message from TEST to somethign else, do you get a different value?
July 7, 2017 at 1:44 am
NJ-DBA - Thursday, July 6, 2017 12:22 PMSQLSACT - Thursday, July 6, 2017 5:33 AMHi All
When sending an SMS text message from SQL Server using the below.Exec msdb..sp_send_dbmail
@recipients = 'mynumber@sms.com'
, @profile_name = 'ProfileName'
, @body_format = 'TEXT'
, @body = 'TEST'The SMS message I get on my phone is : VEVTVA=
Why would this be happening?
When emailing the message to myself, it comes through correctly.Thanks
what happens if you add a second email to the recipeints list, do you get the actual reslult or do you get VEVTA== ? also, if you change the body message from TEST to somethign else, do you get a different value?
The problem doesn't occur when it goes to an actual email address and not a cellphone. I get the actual result when it's an email address
If I change the message to something else it yields a different value.
July 7, 2017 at 5:57 am
SQLSACT - Friday, July 7, 2017 1:44 AMNJ-DBA - Thursday, July 6, 2017 12:22 PMSQLSACT - Thursday, July 6, 2017 5:33 AMHi All
When sending an SMS text message from SQL Server using the below.Exec msdb..sp_send_dbmail
@recipients = 'mynumber@sms.com'
, @profile_name = 'ProfileName'
, @body_format = 'TEXT'
, @body = 'TEST'The SMS message I get on my phone is : VEVTVA=
Why would this be happening?
When emailing the message to myself, it comes through correctly.Thanks
what happens if you add a second email to the recipeints list, do you get the actual reslult or do you get VEVTA== ? also, if you change the body message from TEST to somethign else, do you get a different value?
The problem doesn't occur when it goes to an actual email address and not a cellphone. I get the actual result when it's an email address
If I change the message to something else it yields a different value.
This tells me that as Thom A suggested, the problem likely resides with the carrier...after all dbmail is succeeding to some email addresses. I would try with another carrier just to prove it out. I know that db mail to @vtext.com (verizon) works. Sounds like maybe something about your carrier is not implmeneted correctly. A Google search of VEVTA== suggests that this is something to do with base64 hashing and the word "test"... (https://md5hashing.net/hash/base64/QsXHX9PYca9rC274K ) so maybe something is getting converted incorrectly. The only other idea I have is try with @body_format='HTML'... maybe that is handled differently.... sorry, I'm afraid there's probably not a good answer for you.
July 7, 2017 at 1:19 pm
I send SMS messages to my phone using database mail and your code looks right to me.
Setting a subject forces it to an MMS message and you aren't doing that.
Including HTML messes things up.
You aren't sending long text, which can also convert it to MMS.
Thom is likely correct - the carrier is the one to talk to.
Viewing 6 posts - 1 through 5 (of 5 total)
You must be logged in to reply to this topic. Login to reply