Well i for one, when i send an sms to some MTN numbers from my orange
number i get a delivery report as delivered and some i get failed yet
they all get delivered. So is the problem an MTN one or an orange
problem. Though i also chose to ignore the status of those reports i
cant help but wonder considering an end user who is a lay-man.

On 17 August 2010 13:41, Mike Barnard <[email protected]> wrote:
> well... I know that if I sms an MTN number from my UTL line, I get a
> successful delivery report, but when I do so with my orange line to an mtn
> number, I always get delivery failed report. At times, even when the message
> has been delivered. A quick check on the orange side shows the delivery
> report of a failure at MTN to deliver my message, albeit being received. I
> have learnt to send and ignore the status report.
>
> calling a utl line from orange, the lady at utl tells you how the number you
> have called is not available on the utl network :-/ call it off any other
> network and you go through #:-s
>
>
>
> On Tue, Aug 17, 2010 at 1:11 PM, simbwa <[email protected]> wrote:
>>
>> Read a post on delayed mail & thought I could also raise the issue of
>> delayed SMS delivery esp. when it's coming from a different provider (not
>> sure but could the problem be around the switch or it's just the SMSGW
>> that's stressed!) .  May be someone on this list could enlighten us on
>> what's happening & when we can expect things to normalize. To reproduce what
>> am talking about, proceed as follows:
>> 1. Install & configure kannel 1.4.3
>> 2. Use a GSM modem of any other operator but MTN ( I use the orange E160)
>> 3. In your preferred scripting/programming language; write an app to send
>> bulk SMS (I use python)
>> 4. If you have an MTN line, include your number say 4/5 times in the
>> recipient list ( which could have numbers of other networks)
>> 5. The first MTN number(recipient) will recieve the SMS shortly but the
>> rest get kind of delayed or in some cases never delivered.
>> 6. I figured, may be my script was over pushing. So I included some rate
>> control method in the bulk class...(played with rates upto 1sms per 3sec)
>> --- no change!
>> 7. Looked @bearerbox log (boxes running in debug mode)... I couldn't see
>> anything unusual. The SMS traffic gets to the orange SMSC ( I also get
>> billed for all the messages)
>> 8. Visited the orange HQ to verify with them, and from the printout they
>> showed me, all my traffic was recieved & duly sent to MTN (for MTN numbers).
>>
>>
>> Sent from iPhone Mobile Mail
>> _______________________________________________
>> LUG mailing list
>> [email protected]
>> http://kym.net/mailman/listinfo/lug
>>
>> LUG is generously hosted by INFOCOM http://www.infocom.co.ug/
>>
>> All Archives can be found at http://www.mail-archive.com/[email protected]/
>>
>> The above comments and data are owned by whoever posted them (including
>> attachments if any). The List's Host is not responsible for them in any way.
>> ---------------------------------------
>>
>
>
>
> --
> Mike
>
> Of course, you might discount this possibility, but remember that one in
> a million chances happen 99% of the time.
> ------------------------------------------------------------
>
> _______________________________________________
> LUG mailing list
> [email protected]
> http://kym.net/mailman/listinfo/lug
>
> LUG is generously hosted by INFOCOM http://www.infocom.co.ug/
>
> All Archives can be found at http://www.mail-archive.com/[email protected]/
>
> The above comments and data are owned by whoever posted them (including
> attachments if any). The List's Host is not responsible for them in any way.
> ---------------------------------------
>
>
>



-- 
Roy Mukasa
MUK FCIT
+256794291110
_______________________________________________
LUG mailing list
[email protected]
http://kym.net/mailman/listinfo/lug

LUG is generously hosted by INFOCOM http://www.infocom.co.ug/

All Archives can be found at http://www.mail-archive.com/[email protected]/

The above comments and data are owned by whoever posted them (including 
attachments if any). The List's Host is not responsible for them in any way.
---------------------------------------

Reply via email to