MMS Errors

MMS Errors SearchSearch
Author Message
Abas Mohamed
New member
Username: Bigdongol

Post Number: 19
Registered: 02-2009
Posted on Sunday, June 14, 2009 - 02:17 pm:   

Dear Brother,

How Are you??
Today i came for you to help me in some MMS via MM7 sending problems.

i have MMS account via MM7 and i define it in MMSC Routing
i design application via VB and send the MMS via Http link URL by define the number and MMSfile and subject within the URL.
Till now; there's no problem but the problems in some advanced requests i'll list it bellow

1) to get delievery status for the MMS, how could this happens?

2) in some ways there will be errors recieved like

-Service denied, too many simultaneous connections
-Service denied, maximum allowed message size exceeded

and some other errors like that, how could i recieve that error as i read it from the daily MMS Log File

3) when i sent multirecipent MMS and put for example 10 number separtaed by (;) and some times it goes right and another times it gave me errors like the above point but when it sent successfuly , i notice that when i open the message and choose message details, i found the 10 number which i already sent to this message.

wish you be calm and quiete :-) and solve with me that problems
Bryce Norwood - NowSMS Support
Board Administrator
Username: Bryce

Post Number: 7784
Registered: 10-2002
Posted on Tuesday, June 16, 2009 - 02:33 pm:   

Hi Abas,

1.) Include MMSDeliveryReport=Yes in your request.

In your "MMSC VASP" definition for how you receive MMS messages via MM7, make sure that the routing is to receive messages to the MMS-IN directory.

You will find delivery reports in the MMS-IN directory.

Some more information can be found here:

http://blog.nowsms.com/2009/02/connecting-to-operator-mmsc-with-mm7.html

2.) dealing with "too many simultaneous connections"

When defining the "MMSC Routing" MM7 connection in NowSMS, if you set "Max Connections" to 1 (or leave it blank it will default to 1), then NowSMS will never make more than one connection at a time to your service provider. So it is very odd that they would return this error.

If you install the updated version of NowSMS (http://www.nowsms.com/download/nowsms2009rc.zip),there is a way to limit NowSMS for how quickly it sends MMS messages over a connection. Your provider may need you to slow down.

Here is how you can limit the speed at which NowSMS sends MMS messages over an MM7 connection with the 2009 version:

Outbound message throttling limits are supported for sending messages via external "MMSC Routing" connections (e.g., MM7, MM4, MM1, EAIF). These limits can be defined by manually editing the VASPOUT\accountname\VASP.INI file, and under the [VASP] header, adding SendLimit=x/y where "x" is the number of messages that can be sent over a "y" second interval. If "y" is omitted, a value of "1" is assumed. For example, SendLimit=3 limits the connection to a speed of 3 messages per second. SendLimit=1/2 limits the connection to a speed of 1 message every 2 seconds.

Dealing with "maximum allowed message size exceeded"

For this you will have to determine what your provider's size limit is, and stay under this limit.

3.) Ask your provider what the maximum number of recipients is that they will allow.

When a message is routed to an external MMSC connection, NowSMS will automatically break messages sent to multiple recipients into separate message instances for grouped recipients. The number of recipients per message instance is variable based upon the MMSC connection type. For MM7 connections, the value is 100 recipients per message instance.

Your provider may not support this many recipients per message. You can configure NowSMS so that if you send to more recipients than your provider allows, NowSMS automatically breaks the bigger list of recipients into multiple groups.

To modify this setting, it is necessary to manually edit the VASPOUT\accountname\VASP.INI file associated with the "MMSC Routing" definition. Under the [VASP] header, add MaxRecips=#### to specfy the number of recipients allowed per single MMS message instance.

-bn
Abas Mohamed
New member
Username: Bigdongol

Post Number: 20
Registered: 02-2009
Posted on Sunday, June 21, 2009 - 01:19 pm:   

Thank Bryce for answer me

You are great in all you explain above about the point of deliver reports for MMS...

But still now i have two main problems, some times i get error message about connection limits and i don't know what's the perefcet value i have to set it to MMS account

the second problem was in when sending MMS to multirecipent, there's a problem when i get the mms message i found in the message details all information about the message include all the number that i was sending to them this message, how could i solve that problem..

thanks
Bryce Norwood - NowSMS Support
Board Administrator
Username: Bryce

Post Number: 7801
Registered: 10-2002
Posted on Monday, June 22, 2009 - 07:09 pm:   

The error about "too many simultaneous connections" is very strange, because by default, NowSMS will only make one connection at a time, unless you set "Max Connections" to a value higher than 1.

If you leave "Max Connections" at 1, or leave it blank, the NowSMS will only make one connection at a time. So there should not be too many connections.

I can only guess the possibility that the service provider is confused because NowSMS is disconnecting and then reconnecting again, and the service provider is slow to realise that NowSMS has disconnected.

If you are using a version prior to 2008.04.10, then NowSMS would disconnect/reconnect for every message submitted via MM7.

Beginning with 2008.04.10, NowSMS uses keep-alive sockets for MM7 when the service provider supports it. So if you are using an older version, it may be necessary to update in order to work with this service provider.

The other idea is to use the SendLimit= setting that I mentioned above, and lower the rate at which NowSMS submits messages to the service provider over MM7. Start with lowering it to 1 per second ... unfortunately, in this case it is impossible to guess the right value, it would have to be trial and error.

For the recipient issue, if you are submitting via the NowSMS web interface, it puts all recipients in as "to" recipients.

But there is a way to force them to BCC ...

Edit he VASPOUT\accountname\VASP.INI file, and under the [VASP] header, add ForceBCC=Yes ... this will cause all recipients to be BCC.

-bn