Remove "/type=PLMN" from the sender

Remove "/type=PLMN" from the sender Search Search

SMS & MMS Technical Forum » NowSMS Support - MMS & Advanced Issues (Product Support Only) » Archive through July 28, 2006 » Remove "/type=PLMN" from the sender « Previous || Next »
Author Message
mohammed
New member
Username: Mta

Post Number: 1
Registered: 07-2006
Posted on Monday, July 03, 2006 - 03:09 pm:   

I have a connection with GSM operator via MM7 protocol
When I submit mms to the GSM operator and forward it to the user. The message sender appeared in the handset "/type=PLMN"
I don’t want the "/type=PLMN" appear on the user handset, how can I remove the "/type=PLMN" ?
Thank you a lot

Bryce Norwood - NowSMS Support
Board Administrator
Username: Bryce

Post Number: 6155
Registered: 10-2002
Posted on Monday, July 03, 2006 - 03:52 pm:   

Hi,

That is strange ... because "/TYPE=PLMN" is normally not included by NowSMS when it submits via MM7.

Unless maybe you're using the Ericsson variant, but even there it looks like "/TYPE=PLMN" is not included.

Could you enable the MMSCDEBUG.LOG (easiest done on the Serial # page of the configuration dialog) ... and send another message. I'd like to see this MMSCDEBUG.LOG to better understand your configuration and why this string might be present. Post the MMSCDEBUG.LOG as a reply here (or e-mail it to nowsms@now.co.uk with "Attention: Bryce" in the subject line ... include a reference to this thread in the text of the message, so that I can remember why I wanted to look at this log).
mohammed
New member
Username: Mta

Post Number: 2
Registered: 07-2006
Posted on Tuesday, July 04, 2006 - 09:54 am:   

this is the log file
text/plain
MMSCDebug.txt (11.6 k)
mohammed
New member
Username: Mta

Post Number: 3
Registered: 07-2006
Posted on Tuesday, July 04, 2006 - 09:58 am:   

i am sorry this is the correct log file
application/octet-stream
MMSCDEBUG.LOG (266.2 k)
Bryce Norwood - NowSMS Support
Board Administrator
Username: Bryce

Post Number: 6167
Registered: 10-2002
Posted on Thursday, July 06, 2006 - 07:42 pm:   

Hi,

Thanks for posting the log.

I do not know what to suggest. When NowSMS posts the message to the MMSC, the "/TYPE=PLMN" suffix is not present, as I expected.

The data of the MM7 post is included in the MMSCDEBUG.LOG, and there is no "/TYPE=PLMN".

Maybe the operator MMSC is confused by your sender address of "BAB"?

Technically, I don't think that sender address is valid. It should be either a short code number, a phone number, or an e-mail address. (Your operator may have additional restrictions on what values are legal.)

Because the sender address "BAB" is not valid, this might be causing some confusing logic in the operator MMSC, making it add the "/TYPE=PLMN" suffix. So I'd suggest trying different sender address values.

-bn
mohammed
New member
Username: Mta

Post Number: 4
Registered: 07-2006
Posted on Saturday, July 08, 2006 - 11:55 am:   

hi
thank you for your reply

I tried to put a number but the same problem see the new log file in attachment
application/octet-stream
MMSCDEBUG 8-7-2006.LOG (10.9 k)
Bryce Norwood - NowSMS Support
Board Administrator
Username: Bryce

Post Number: 6180
Registered: 10-2002
Posted on Tuesday, July 11, 2006 - 06:43 pm:   

Hi,

I don't see a sender address present in that log, so I would assume that whatever sender address is present in the resulting message was applied by the mobile operator.

What sender address do you see in the resulting message? If it is the same sender address as before, then maybe it is an issue with the way your account is configured in the operator MMSC.

Since there is no sender address in your latest log, I would suggest setting one ... set in under the "MMSC Routing" definition ... and UNcheck "Allow Sender Address Override".

-bn
mohammed
New member
Username: Mta

Post Number: 5
Registered: 07-2006
Posted on Thursday, July 13, 2006 - 10:13 am:   

hi

see this log . i put 07 as asender address

The same message apparel in the sender address /TYPE=PLMN


thank you
mohammed
application/octet-stream
MMSCDEBUG 13-7-2006.LOG (10.9 k)
Bryce Norwood - NowSMS Support
Board Administrator
Username: Bryce

Post Number: 6196
Registered: 10-2002
Posted on Thursday, July 13, 2006 - 09:21 pm:   

Hi mohammed,

Everything looks ok at the point that the MMS message leaves NowSMS.

The sender address is "07" ... and there is no "/TYPE=PLMN" suffix present in the sender address.

I believe that "/TYPE=PLMN" is being added by your mobile operator. However, I see no reason why they should or would be doing this.

Therefore, I think you will have to ask your mobile operator why.

I do have two posssible suggestions though ...

1.) Do you have a particular short code that your operator told you that you should be using? What if you specify that as the sender address, does that work?

2.) I also notice from the debug log that you are interfacing with an MMSC from Huawei. I seem to recall a sender address problem with that MMSC in another thread ... yes ... here it is ... http://www.nowsms.com/discus/messages/485/11789.html

There are several updates mentioned in that thread. However, you DO NOT need an update, as you are running NowSMS 2006, which is more current than the version referenced in that thread.

The person in that thread resolved their problem by editing VASPOUT\vaspAccountName\VASP.INI, and adding the following to that file:

[AdditionalSettings]
Sender=1234

Substitute your intended Sender address for 1234 in this example.

However, I see no reason why this should work. In fact, it should be invalid to do this ... so if it does not fix your problem, remove this setting immediately so that it does not cause future confusion.

If it works, I can only figure that the Huawei MMSC has a bug in its MM7 implementation, where it expects the sender address to be within a <Sender> element instead of a <SenderAddress> element. However, this is not the way things are defined in the MM7 XML schema ... and adding this would cause XML validation to fail.

-bn
mohammed
New member
Username: Mta

Post Number: 6
Registered: 07-2006
Posted on Monday, July 24, 2006 - 10:01 am:   

Hi

Thank you for your reply
I put "6174" as a sender address that the operator provides it to me
But I released in MMS out log file the "/TYPE=PLMN" was added !!

So what do you think??

mohammed
text/plain
MMSC-20060724.LOG.txt (0.2 k)
text/plain
MMSCDEBUG 24-7-2006.txt (10.6 k)
Bryce Norwood - NowSMS Support
Board Administrator
Username: Bryce

Post Number: 6264
Registered: 10-2002
Posted on Friday, July 28, 2006 - 09:21 pm:   

Yes, the "/TYPE=PLMN" in the MMSC-yyyymmdd.LOG file.

However, this does not mean that we included "/TYPE=PLMN" in the data that was actually transmitted to the operator MMSC. Whether or not it is included depends on the protocol that is used.

In your case, MM7 is the protocol being used. And the MMSCDEBUG.LOG clearly shows that we are not including "/TYPE=PLMN" in the sender address in the actual MM7 data that is submitted to the mobile operator.

Here is the data that is actually being transmitted to your mobile operator:


quote:

<?xml version="1.0" ?>
<env:Envelope xmlns:env="http://schemas.xmlsoap.org/soap/envelope/">
<env:Header>
<mm7:TransactionID xmlns:mm7="http://www.3gpp.org/ftp/Specs/archive/23_series/23.140/schema/REL-6-M M7-1-0" env:mustUnderstand="1">20060724113209-55018FA6@172.20.1.101</mm7:TransactionID>
</env:Header>
<env:Body>
<SubmitReq xmlns="http://www.3gpp.org/ftp/Specs/archive/23_series/23.140/schema/REL-6-MM7-1 -0">
<MM7Version>6.3.0</MM7Version>
<SenderIdentification>
<VASPID>844007</VASPID>
<VASID>007</VASID>
<SenderAddress><ShortCode>6174</ShortCode></SenderAddress>
</SenderIdentification>
<Recipients>
<To>
<Number>966562070640</Number>
</To>
</Recipients>
<ServiceCode>07</ServiceCode>
<Priority>Normal</Priority>
<DeliveryReport>False</DeliveryReport>
<ReadReply>False</ReadReply>
<Subject>test</Subject>
<Content href="cid:mms_cid"/>
</SubmitReq>
</env:Body>
</env:Envelope>

-----mime-boundary-A545EEA7.1D6F1868---
Content-Type: multipart/related; start="<44B60937.smil>"; type="application/smil"; boundary="---mime-boundary-91A09CE9.0C4A0C2A---"
Content-ID: <mms_cid>

-----mime-boundary-91A09CE9.0C4A0C2A---
Content-Type: application/smil
Content-ID: <44B60937.smil>
Content-location: 44B60937.smil

<smil>
<head>
<layout>
<region id="Image" height="100%" width="100%" fit="meet"/>
<region id="Text" height="100%" width="100%" fit="scroll"/>
</layout>
</head>
<body>
<par dur="3s">
<text src="44B60937.txt" region="Text"/>
</par>
</body>
</smil>

-----mime-boundary-91A09CE9.0C4A0C2A---
Content-Type: text/plain
Content-ID: <44B60937.txt>
Content-location: 44B60937.txt

tetse
-----mime-boundary-91A09CE9.0C4A0C2A-----

-----mime-boundary-A545EEA7.1D6F1868-----




As you can see, "/TYPE=PLMN" appears nowhere in this data.

I wish I could offer you a solution. But I don't see what can be done. We're not putting it there.

But, as I think about this ... this whole discussion might be completely irrevelant.

The operator MMSC is going to use the MM1 protocol to deliver the message to the recipient mobile phone.

Within the MM1 protocol, "/TYPE=PLMN" is ALWAYS added to a phone number in the message header ... whether it is a sender or a recipient.

Of course, most mobile phone will hide "/TYPE=PLMN" from the actual end-user because it is likely to only confuse them.

So maybe the fact that you are seeing this "/TYPE=PLMN" present is a user interface issue with the mobile phone that you are testing with.

What if you send an MMS to that phone from another phone? (Make sure that the sender phone number is not a phone number that is in your contact list on the receiving phone, otherwise most phones will detect this and display the information from your contact list/address book instead of the actual sender phone number.)

All in all ... the bottom line is that we are not including "/TYPE=PLMN" when we post the message to the mobile operator, as the MM7 protocol does not want this suffix to be included.

However, the mobile operator MMSC has to add this "/TYPE=PLMN" suffix to any sender phone number when it delivers the message using the MM1 protocol. It is just that the user interface on most mobile phones will hide this "/TYPE=PLMN" suffix because it can only confuse an end user.

Login Login / Register Search Search   Home Home
Logout Logout Topics Topics Search Last 1|3|7|30 Days   Previous Page Previous Next Next Page