Different ServiceID for Carrier

Different ServiceID for Carrier SearchSearch

SMS & MMS Technical Forum » NowSMS Support - SMS Issues (Product Support Only) » Archive through May 20, 2013 » Different ServiceID for Carrier « Previous || Next »
Author Message
Mark Hewson
New member
Username: Markhewson

Post Number: 2
Registered: 08-2012
Posted on Monday, October 08, 2012 - 02:39 pm:   

Hi,

I have everything running nicely with NOWSMS and MBLOX. When i submitted for network validation i got the following.
REQUIREMENTS:
1. VALIDATE: AT&T Successful Test
a. RESULT: VALIDATED
2. VALIDATE: Service IDs for Verizon & T-Mobile. No service ID evident
a. RESULT: Received Error 43 (Verizon) and Error 49 (T-Mobile)
b. FIX: Ensure service ID parameter is in place and retest
3. VALIDATE: Nextel or Boost Successful Test
a. RESULT: VALIDATED
4. VALIDATE: Sprint Successful Test
a. RESULT: VALIDATED
5. VALIDATE: Additional Carrier Successful Test
a. RESULT: VALIDATED – Virgin Mobile

Apparently Verizon & T-Mobile need a different ServiceID to the others.

I currently have mblox_serviceid=56488,String under SMPP Options in the .ini file but need to pass ServiceID = 56490 for T-Mobile and Verizon.

How do I do this?

Thanks a lot,

Mark
Des - NowSMS Support
Board Administrator
Username: Desosms

Post Number: 4119
Registered: 08-2008
Posted on Tuesday, October 09, 2012 - 03:49 pm:   

Hi Mark,

The question in issues like this is always, how do you know which carrier the message should be submitted to?

If your interaction with a subscriber starts with an SMS from that subscriber, then the SMS provider should provide this value in the received SMS. If you are using HTTP based 2-way commands, NowSMS would automatically add &SMPPOption_mblox_serviceid to the request, and you would then include that same parameter when submitting messages back to that subscriber. Just keep in mind that NowSMS does not track that parameter, so you would need to do this. (one exception...For simple 2-way commands that generate a single reply, there is a configuration setting that can be applied to copy some SMPPOption settings automatically in the reply.)

--
Des
NowSMS Support
Des - NowSMS Support
Board Administrator
Username: Desosms

Post Number: 4120
Registered: 08-2008
Posted on Tuesday, October 09, 2012 - 03:52 pm:   

Follow-up:

Here is an article that explains how to set a configuration option to copy one or more SMPPOption values when generating a reply with a simple 2-way command:
http://support.nowsms.com/discus/messages/1/24487.html
Mark Hewson
New member
Username: Markhewson

Post Number: 3
Registered: 08-2012
Posted on Tuesday, October 16, 2012 - 07:25 am:   

Thanks so much for the help so far Des.

I'm still struggling with this. I added SMPPOption_mblox_serviceid to my http call as a querystring parameter but i dont get anything back. I tried SMPPOption_mblox_serviceid as well as @@SMPPOption_mblox_serviceid@@ but all I get back is SMPPOption_mblox_serviceid or @@SMPPOption_mblox_serviceid@@

My call looks as follows:

http://myserver/NOWSMSPROXY/processquery.aspx?FULLSMS=@@FULLSMS@@&SENDER=@@SENDE R@@&SERVID=@@mblox_serviceid@@

Thanks,

Mark
Des - NowSMS Support
Board Administrator
Username: Desosms

Post Number: 4143
Registered: 08-2008
Posted on Tuesday, October 16, 2012 - 05:16 pm:   

Hi Mark,

There is no need to add any parameters to your 2-way command.

NowSMS does this automatically if it sees any TLV parameters defined in in the [SMPPOptions] section present in the received SMS message.

I'm assuming that in SMSGW.INI, you have the following setting, correct?

[SMPPOptions]
mblox_operator=1402,String,5
mblox_serviceid=1407,String

(There may be other settings defined as well.)

And ... actually, now that I look at it, mblox uses the mblox_operator parameter for the carrier ID, doesn't it?

If a received SMS message contains the mblox_operator parameter (and that parameter is defined in the [SMPPOptions] section of SMSGW.INI), then when building the 2-way command, NowSMS will automatically add &SMPPOption_mblox_operator=xxxxx to the URL string.

If this doesn't help you figure out what's going on, then it would help if I could see your settings, as well as the actual raw data in the SMS message that you are receiving.

Enable the SMSDEBUG.LOG (checkbox setting on "Serial #" page), restart the NowSMS service, and then send in another message.

E-mail the SMSDEBUG.LOG, SMPPDEBUG.LOG and SMSGW.INI file to nowsms@nowsms.com with Attention: Des in the subject line of your message.

I'll confirm that the settings are correctly applied, and then take a look at exactly what data is present in the received message.

--
Des
NowSMS Support
Mark Hewson
New member
Username: Markhewson

Post Number: 4
Registered: 08-2012
Posted on Tuesday, October 23, 2012 - 09:12 am:   

Hi Des,

Sorry for the delay, I have been out of the office. I have sent the files.

Thanks,

Mark
Des - NowSMS Support
Board Administrator
Username: Desosms

Post Number: 4167
Registered: 08-2008
Posted on Tuesday, October 23, 2012 - 07:28 pm:   

Hi Mark,

I see the issue. And actually your test that is passing probably should not pass.

Remove this line from the [SMPPOptions] section of SMSGW.INI:

mblox_serviceid=56488,String

Add the two lines that I mentioned above to the [SMPPOptions] section of SMSGW.INI:

mblox_operator=1402,String,5
mblox_serviceid=1407,String

These mBlox specific parameters are not part of the SMPP spec ... but SMPP allows anyone to add additional parameters.

Every additional parameter has a tag number associated with it. mBlox is using 1407 as the tag number for their "serviceid" parameter.

56488 and 56490 are potential values for that parameter. But the value needs to be associated with the proper tag number (1407). It is an issue that the tag number is independent of, and should not be confused with the tag value.

Fix the SMPPOptions settings, and you should start seeing &SMPPOption_mblox_operator being passed to your HTTP based 2-way commands to tell you which operator the message is arriving from. And if you include &SMPPOption_mblox_serviceid=56488 (or any other value) in your request, it should be encoded correctly.

One other note to save you time on another troubleshooting issue. If ? is present in a text string for an HTTP submission, it must be URL encoded.

--
Des
NowSMS Support

Login Login / Register Logout Logout Search Last 30 Days Topics Topics