Security

Hi,

one of my customers is using a specail prefix in the e-Mail adress: SMS#phonenumber@mailserver.

I can customize a filed to compose the new Phonenumber  sms_vistor_phone = SMS#data.visitor_phone.

The new field can be defined in the plugin manager.

But when trying to send the plugin enforces numbers: "Please provide a valid telephone number for the recipient, in international format"

Any workaround on that?

Thank you,

Johnny

You always want to store the mobile as the mobile.  I assume you created a custom SMTP Carrier pointing to your special domain.  Select 'Always include the country code', and set 'SMS#' as the country code.

Note you can edit the visitor_phone field and adjust its Validator away from NwaSmsIsValidPhoneNumber.  Some places use a regular expression to narrow in their particular countries format.

Thank you. As always the solution is much simplier than imagined. :smileyhappy:

Little question, how do you do this :

Customize a filed to compose the new Phonenumber  sms_vistor_phone = SMS#data.visitor_phone.

Thanks

Dimitri

What is the scenario you need this?  You can setup a custom carrier and use the keyword NUMBER.  In general everything left of the @ symbol in the carrier is used, but when NUMBER is seen, it is simply swapped with your number.  So a carrier email of "SMS#NUMBER@your.com" would be fine. 

What I need is :

2 fields, one with a prefix and one with the phone number. I'd like to merge both field into a new one "Phone number" then to use it for SMS sending.

Thanks

Dimitri

You cannot use extra fields when making the email destination.  Is the prefix anything other than "SMS#"?  The only way to get that is my example above.  Create your own carrier using my example, and you can hard code that as the default carrier.  You do need to be on current releases for some of this.  If you have separate prefixes, then you need a carrier for each, and then tie that to the users via visitor_carrier. 

It's a different of the original problem : so I use a SMS gateway, username is a phone number but without the prefix.

What I would like to do is to give the possibilty to choose the prefix and then the SMS is sent to a phone number that is prefix+username.

So I was looking to merge fields or past values from field to field.

You cannot mix fields, no.  The best you can do is to setup multiple visitor_carriers with the known prefixes, and then tie each user to that carrier.

Ok thanks. Can you give me more details how to do it ?

Got to the SMTP Carriers list within Guest then create and enable a carrier for each known prefix.  If your prefixes were SMS#, SMS1#, and SMS2# then you would have SMS Templates:

• SMS#NUMBER@yourgateway.com
• SMS1#NUMBER@yourgateway.com
• SMS2#NUMBER@yourgateway.com

Then add visitor_carrier to the various forms relevant to your deployment (create_user, guest_edit, guest_multi).  You can use Edit Accounts to then bulk update existing accounts.

Out of curiousity, what do the different prefixes mean to your gateway?  We have only ever seen a single prefix used that was meant simply to detect any/all things destined to an SMS.

About prefixes, I am not sure that we are talking about the same thing. In my case, it's the country code.

Well I guess there was confusion then.  Your example was "sms_vistor_phone = SMS#data.visitor_phone".  We have customers with that exact example.  Their email gateway looks for anything starting with the prefix and assuems the rest is the actual destination.  The country code is entirely different as that really needs to be asked as part of the phone number.  For all the built in SMS gateways, you must include the country code outright in the number.

Ok thanks.

Dimitri