MMS Outbound routing

MMS Outbound routing SearchSearch
Author Message
Min
Unregistered guest
Posted on Tuesday, October 11, 2005 - 06:15 am:   

Dear Bryce,
I am trying to connetc NowSMS with the mobile operator through Internet connection(public IP address). On MMSC Routing tag, I added an MMS Outbound Routing, but I encounted same thing shown in the following link:
http://support.nowsms.com/discus/messages/485/7560.html
your answer to it was "Add /mm7 to the URL ... that tells the MMSC that it is processing an MM7 connection. Otherwise, it assumes that it is processing an MM1 connection", but I am confused and want to know where to add /mm7 ?
Thx.
Min
Unregistered guest
Posted on Tuesday, October 11, 2005 - 06:34 am:   

Hi Bryce,
In the following link, http://support.nowsms.com/discus/messages/485/6981.html, I know "where" to add /mm7 now, but, this is just a debug information(MMSCdebug.txt), how should I config NowSMS to add /mm7 option?? Is this a bug?
Bryce Norwood - NowSMS Support
Board Administrator
Username: Bryce

Post Number: 5098
Registered: 10-2002
Posted on Tuesday, October 11, 2005 - 03:22 pm:   

Hi Min,

The "/mm7" is specific to when an MM7 application wants to connect to a NowSMS server using MM7. The NowSMS MMSC looks for "/mm7" at the beginning path of the URL.

So the advice that you are looking at is for the opposite direction ... NowSMS receiving an MM7 connection ... instead of NowSMS initiating an MM7 connection.

If you are connecting to a mobile operator, they would need to provide you with a URL for their server. It can be pretty hard to just guess at it, because it is generally installation specific.

-bn
Min
Unregistered guest
Posted on Tuesday, October 11, 2005 - 03:34 pm:   

Hi Bryce,
I am still confusing.
Bryce Norwood - NowSMS Support
Board Administrator
Username: Bryce

Post Number: 5127
Registered: 10-2002
Posted on Thursday, October 13, 2005 - 09:43 pm:   

Min,

You need to tell me more details about the service to which you are connecting.

An MMSCDEBUG.LOG would also be helpful, because I just don't have enough information to answer your questions.

It sounds like you are telling me that the service you are trying to connect to is rejecting your message. Have you verified with that service provider that you are using the correct settings?

-bn
Min
Unregistered guest
Posted on Friday, October 14, 2005 - 02:12 am:   

Dear Bryce,

Thank you for your help and reply, I called the Mobile Operator, and the problem is solved. I made a very stupid mistake, I inputed the wrong URL. :-)

Thanks again!

Min
Bryce Norwood - NowSMS Support
Board Administrator
Username: Bryce

Post Number: 5143
Registered: 10-2002
Posted on Friday, October 14, 2005 - 07:43 pm:   

Glad to hear it Min!
Min
Unregistered guest
Posted on Saturday, October 15, 2005 - 06:05 pm:   

Dear Bryce,
Thx for your kind help, but I bring trouble to you again this time.

When I send out an MMS(submitted from web interface of NowSMS, delivered via mobile operator's MMSC), the sender address(short code doesn't appear at all on the receiving phone. I uploaded the debug information, plz help me. and sorry for the trouble I've made.
I am looking forward to your answer.
application/octet-stream
MMSCDEBUG2.LOG (6.9 k)
Min
Unregistered guest
Posted on Wednesday, October 19, 2005 - 07:18 am:   

Anything? Can anyone help me?
Bryce Norwood - NowSMS Support
Board Administrator
Username: Bryce

Post Number: 5162
Registered: 10-2002
Posted on Wednesday, October 19, 2005 - 06:29 pm:   

Hi Min,

I don't know. The sender address is clearly present in the message that you are submitting to the operator.

But, I see that they are using a Huawei MMSC. And I'm going to make a guess that this MMSC might want to see something slightly different.

Download the update at http://www.nowsms.com/download/min.zip, and see if this makes a difference.

If it doesn't, then I've got one more idea to try. But let's try this first.

-bn
Min
Unregistered guest
Posted on Thursday, October 20, 2005 - 08:46 am:   

Thx Bryce, but unfortunately, it doesn't work. I changed the connection type of the "MMS Outbound Routing" to "To VASP(deliver format)", it gave me another debug msg with failure information.hope this will give you more information.
P.S. I called the operator MMSC, they told me that they've checked the log file on their side and it showed that NowSMS didn't fill the sender information at all.
application/octet-stream
MMSCDEBUG.LOG (9.7 k)
Min
Unregistered guest
Posted on Monday, October 24, 2005 - 05:06 am:   

Any suggestion, Bryce?
Min
Unregistered guest
Posted on Tuesday, October 25, 2005 - 02:08 pm:   

Where is Bryce?
Min
Unregistered guest
Posted on Tuesday, November 01, 2005 - 01:04 am:   

Hello Bryce.......
Min
Unregistered guest
Posted on Friday, November 04, 2005 - 07:32 am:   

Dear Bryce,
Please help.........I am looking forward to your reply....
Thx
Bryce Norwood - NowSMS Support
Board Administrator
Username: Bryce

Post Number: 5206
Registered: 10-2002
Posted on Friday, November 04, 2005 - 08:38 pm:   

Min,

Sorry for the long delay (again). We are working on a major new release, and it has been difficult to keep up with this discussion board.

You want to go back to "To MMSC (Submit format)" as the connection type. This is the format that you use when submitting a message to an MMSC.

The deliver format is used when NowSMS is the MMSC and it is delivering messages to a VASP.

But if the sender address is still showing up blank, then I am not sure why this would be. The sender address is being included in the message submission. Perhaps your account on the MMSC needs to be provisioned with a sender address and currently it is not.

I do have one other idea ...

I notice in your earlier log that when you submit a message to the MMSC, it includes some proprietary HTTP headers in the response:

x-huawei-mmsc-tid: 20051015173150-5065063C@218.201.121.8
x-huawei-mmsc-from:
x-huawei-mmsc-to: xxxxxxxxxxx
x-huawei-mmsc-code: 1000

I am wondering if perhaps the MMSC also looks for these headers when messages are submitted.

If so, we could try including "x-huawei-mmsc-from: xxxxx" to try to set the sender address.

Unfortunately, the current NowSMS does not have a way to do this for standard MM7 connections. So I've uploaded another update to the same URL as above http://www.nowsms.com/download/min.zip.

With this version, try editing VASPOUT\vaspaccountname\VASP.INI, and under the [VASP] header, add:

ExtraHeader=x-huawei-mmsc-from: xxxxx

And see if that makes a difference.

If it doesn't, then I suspect there is an issue at the MMSC where your account needs to be provisioned for a sender address.

-bn

Min
Unregistered guest
Posted on Saturday, November 05, 2005 - 03:50 am:   

Thx Bryce, unfortunately, it doesn't work. I'll contact my mobile provider for some info.
Min
Unregistered guest
Posted on Tuesday, November 08, 2005 - 09:59 am:   

Dear Bryce,

I uploaded the log file from mobile operator, it includes the log of another SP and mine. Maybe this will help u to figure out the problem?
Thx!
application/octet-stream
session.log (3.7 k)
Min
Unregistered guest
Posted on Wednesday, November 09, 2005 - 02:24 am:   

Dear Bryce,
any help?
Min
Bryce Norwood - NowSMS Support
Board Administrator
Username: Bryce

Post Number: 5234
Registered: 10-2002
Posted on Wednesday, November 09, 2005 - 07:56 pm:   

Hi Min,

There is another thread going on here where people are having problems interfacing with an "Huawei" MMSC, which is the same type of MMSC that you are interfacing with.

However, they were getting errors instead of just missing a "From" field in the sent message.

But maybe you are experiencing a related problem.

In their case, they needed to include a "Service Code" when submitting a message to the operator MMSC. However, the "Service Code" option in NowSMS did not work properly.

I posted an update to the same URL as before (http://www.nowsms.com/download/min.zip) to correct the "Service Code" problem.

I see from your logs that you are not using a "Service Code". But maybe your operator wants you to be using one?

I can't see much from that operator log, however, I do see that a "Service Code" is being reported on the other submission, so perhaps this is important to the Huawei MMSC.

-bn
Min
Unregistered guest
Posted on Thursday, November 10, 2005 - 04:55 pm:   

Dear Bryce,

I am so sorry to bother you again and again. I found the other thread you mentioned and try the new update, and I think I am almost there, but still failed. I added Sender=12345 under the [AdditionalSettings] as you said, when I submit MMS via webpage with "From :" field filled, NowSMS gives me debug information in 1.txt, if I leave it blank, NowSMS gave me debug information in 2.txt. any suggestion?
Again, I am sorry to bother you again and again.
Thx a lot!
Min
text/plain
1.txt (9.8 k)
text/plain
2.txt (7.4 k)
Min
Unregistered guest
Posted on Friday, November 11, 2005 - 05:19 am:   

Dear Bryce,
My problem has been solved. Thank you very very much! You're really a great man!

Min
Min
Unregistered guest
Posted on Friday, November 11, 2005 - 06:30 am:   

Dear Bryce,
The strange thing is, I just added Sender = ***** under [AdditionalSettings] section, I didn't add any of ServiceCode, ChargedParty, ChargedPartyID. I din't even fill "Service Code" option in MMS Outbound Routing, and the problem solved.
Bryce Norwood - NowSMS Support
Board Administrator
Username: Bryce

Post Number: 5240
Registered: 10-2002
Posted on Friday, November 11, 2005 - 06:19 pm:   

Hi Min,

I'm glad to hear that the problem is resolved.

Although admittedly, I'm a bit puzzled what made the difference. But what counts is that the problem is resolved.

-bn
Min Lu
New member
Username: Uspepper

Post Number: 2
Registered: 08-2005
Posted on Sunday, December 04, 2005 - 02:32 pm:   

Hi Bryce,

It's me again. SORRY! What I am trying to do now is, I set up one server(Server1) connect to mobile operator's MMSC, using shortcode say 1234. And I use [AdditionalSettings] in VASP.INI(in VASPOUT folder) and it works fine now. At the same time, I set up another two server(Server2 and Server3) connect to Server1, trying to use short code 12341 and 12342 accordingly. But the sender information on the receiving cell phone, is always 1234.
I tried to put [AdditionalSettings] in VASP.INI in VASPIN folder on Server1, but it won't work.

Any suggestion? Hope I've explained the problem clearly.
Thx
Bryce Norwood - NowSMS Support
Board Administrator
Username: Bryce

Post Number: 5358
Registered: 10-2002
Posted on Monday, December 19, 2005 - 06:10 pm:   

Min,

Sorry, I missed this posting earlier. I don't know any reason why the short code would be truncated.

I'd suggest enabling the MMSCDEBUG.LOG, and look at the raw message submission. I suspect that the full short code is present in the message submission. What do you see?

-bn