MM7 Issue

MM7 Issue SearchSearch
Author Message
Omar
Frequent Contributor
Username: Kfsmart

Post Number: 72
Registered: 01-2008
Posted on Sunday, December 15, 2013 - 07:07 am:   

Hi,
I made a connection with one of operators but I have a problem with MSISDN:
They are expecting to send mobile in such parameters:

<Recipients>
<To>
<ShortCode>
MSISDN
</ShortCode>
</To>
</Recipients>

But from your gateway in this format:

<Recipients>
<To>
<Number>MSISDN</Number>
</To>
</Recipients>

How to change "Number" to "Shortcode"?
Des - NowSMS Support
Board Administrator
Username: Desosms

Post Number: 4773
Registered: 08-2008
Posted on Tuesday, December 17, 2013 - 08:05 pm:   

Hi,

Are you actually sending to MSISDN numbers?

It seems insane that they would require you to indicate that the recipient numbers are short codes.

That said, it is possible.

In MMSC.INI, under the [MMSC] section header, add ShortCodeMaxLength=20

This will cause NowSMS to use ShortCode instead of number if the recipient number is 20 characters or less.

One exception ... be sure not to use + in recipient numbers, otherwise, NowSMS will treat as MSISDN (Number) instead of a very long short code.

--
Des
NowSMS Support
Omar
Frequent Contributor
Username: Kfsmart

Post Number: 73
Registered: 01-2008
Posted on Thursday, December 19, 2013 - 11:21 am:   

<env:Envelope xmlns:env="http://schemas.xmlsoap.org/soap/envelope/">
<env:Header>
<ns2:TransactionID xmlns="http://www.3gpp.org/ftp/Specs/archive/23_series/23.140/schema/REL-5-MM7-1-2" xmlns:ns2="http://schemas.xmlsoap.org/soap/envelope/" ns2:mustUnderstand="0" xmlns:MM7="http://www.3gpp.org/ftp/Specs/archive/23_series/23.140/schema/REL-5-MM7-1-2">
A REQUEST TRANSACTION ID
</ns2:TransactionID>
</env:Header>
<env:Body>
<SubmitReq xmlns="http://www.3gpp.org/ftp/Specs/archive/23_series/23.140/schema/REL-5-MM7-1-2" xmlns:ns2="http://schemas.xmlsoap.org/soap/envelope/">
<MM7Version>5.3.0</MM7Version>
<SenderIdentification>
<VASPID>PARTNER ROLE PASSWORD</VASPID>
<VASID>PARTNER ROLE ID</VASID>
<SenderAddress>
<ShortCode displayOnly="false">6863</ShortCode>
</SenderAddress>
</SenderIdentification>
<Recipients>
<To>
<ShortCode xmlns:xs="http://www.w3.org/2001/XMLSchema" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:type="xs:string">
MSISDN
</ShortCode>
</To>
</Recipients>
<MessageClass>Informational</MessageClass>
<DeliveryReport>true</DeliveryReport>
<Priority>Normal</Priority>
<Subject>THE MMS SUBJECT</Subject>
</SubmitReq>
</env:Body>
</env:Envelope>
Omar
Frequent Contributor
Username: Kfsmart

Post Number: 74
Registered: 01-2008
Posted on Thursday, December 19, 2013 - 11:24 am:   

Hi,

Above I mentioned Actual format required,
They need to submit the mobile number as this:
<Recipients>
<To>
<ShortCode xmlns:xs="http://www.w3.org/2001/XMLSchema" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:type="xs:string">
MSISDN
</ShortCode>
</To>
</Recipients>

Note: I have a live connection with other partner and I don't want to affect it.

Please advise
Omar
Frequent Contributor
Username: Kfsmart

Post Number: 75
Registered: 01-2008
Posted on Thursday, December 19, 2013 - 11:30 am:   

And this is the way I'm submitting the MMS:
http://URL/?user=xxx&password=xxx&PhoneNumber=[mobileno]&MMSFrom=[shortcode]&MMS Subject=xxxx&MMSfile=[url]&MMSText=Text
Des - NowSMS Support
Board Administrator
Username: Desosms

Post Number: 4774
Registered: 08-2008
Posted on Thursday, December 19, 2013 - 02:25 pm:   

Hi Omar,

I spoke with our engineering manager, and he said that if they can accept this:

<SenderIdentification>
<VASPID>PARTNER ROLE PASSWORD</VASPID>
<VASID>PARTNER ROLE ID</VASID>
<SenderAddress>
<ShortCode>6863</ShortCode>
</SenderAddress>
</SenderIdentification>
<Recipients>
<To>
<ShortCode>
MSISDN
</ShortCode>
</To>
</Recipients>

Then we can make a quick update to add a connection specific ShortCodeMaxLength=## setting so that you could have the above for this provider and not change how things are handled for other providers.

The ability to add other custom attributes to the ShortCode tag is not feasible at this time.

We are looking at updating the logic to allow the use of custom MM7 XML templates that could be custom edited. However, we cannot do this until the 1Q2014 time period.

--
Des
NowSMS Support