Re: urgent help! CIMD2 missing DLR answer!

To give you a quick update.. I told the provider about the problem, they are now checking their traces.. so far about this issue ;)


btw. Does anybody of you have experience with routing logic of kannel?

basically I am sending (forced-smscid) to SMSCA. And in the follow 4 SMSCID I have set the configuration parameter with denied-smscid and allowed-smscid and so on..

my purpose is the follow:

force to send always via smscA. if the link to smscA is down, send all SMS via smscB, if the link is down send to smscC. And when the link to smscC is down, then make load balancing through the smscD,E and F. 

Im testing right now but it never worked... with forced-smscid I managed to send always via smscA - I disconnected for testing the smscA now it is offline, but the routing-rules are not working. it also sends via smscD ! It driving me crazy!!!!!!!!!!!!

note: I dont want my application to send the parameter smsc= (btw, this actually doesnt work anyway as I tested...)

I would appreshiate any help!

Alejandro? Any hints?

THANKS!

cheers

beatrice



-------- Original-Nachricht --------
> Datum: Thu, 20 Jan 2011 16:37:51 +0100
> Von: "Beatrice Tamburrino" <[email protected]>
> An: Alejandro Guerrieri <[email protected]>
> CC: [email protected]
> Betreff: Re: urgent help! CIMD2 missing DLR answer!

> this is exactly what I was thinking... I am really not sure that they are
> sending all dlr's.. (I also barely know the protocol I am often working
> with EMI)
> 
> also we have 5 differents smsc, but the customer wants that we only send
> via smsc1 - if the smsc1 is not online, then send via smsc2 and so on... 
> 
> The point with the reroute is a very good point that you are mentioning..
> I "removed" 4 smscs, so now I am sending only with the smsc1 but still the
> same problem - I will check again with the provider..
> 
> thanks for the support, I will give a feedback.
> 
> cheers
> 
> -------- Original-Nachricht --------
> > Datum: Thu, 20 Jan 2011 15:09:15 +0100
> > Von: Alejandro Guerrieri <[email protected]>
> > An: Beatrice Tamburrino <[email protected]>
> > CC: [email protected]
> > Betreff: Re: urgent help! CIMD2 missing DLR answer!
> 
> > I've checked the CIMD2 protocol here:
> > 
> >
> http://www.forum.nokia.com/info/sw.nokia.com/id/7a27b9e7-7cdd-4456-b630-3d7c35f30a4f/CIMD_Interface_Specification_SC80.pdf.html
> > 
> > From what I see, and considering that I barely know the protocol, looks
> > like you only got 2 messages with opcode 23 (deliver status report). In
> those
> > cases, the messages were properly processed and removed of the queue.
> > 
> > The rest of the messages didn't get a deliver status report, so they
> > remain on the queue.
> > 
> > I believe the carrier is not returning all the delivery reports, or
> maybe
> > they're being routed someplace else (if you have redundant connections
> with
> > different smsc-id's that could explain it as well).
> > 
> > Regards,
> > --
> > Alejandro Guerrieri
> > [email protected]
> > 
> > 
> > 
> > On 20/01/2011, at 14:35, Beatrice Tamburrino wrote:
> > 
> > > Hi Alejandro
> > > 
> > > Im using dlr-mask 31. thanks for the explanation, but why is the type
> 1
> > sometimes getting parsed from the kannel and sometimes not (added in the
> > DLR-queue). I thought neverthless wich protocol is used, the kannel
> parses
> > the requests from the smsc and does interpret it to the type it needs..
> > correct?
> > > 
> > > cheers
> > > 
> > > -------- Original-Nachricht --------
> > >> Datum: Thu, 20 Jan 2011 13:05:01 +0100
> > >> Von: Alejandro Guerrieri <[email protected]>
> > >> An: Beatrice Tamburrino <[email protected]>
> > >> CC: [email protected]
> > >> Betreff: Re: urgent help! CIMD2 missing DLR answer!
> > > 
> > >> What dlr-mask are you using?
> > >> 
> > >> Please note that there's an important difference between the "first"
> > DLR
> > >> (the one that Kannel creates right after sending the message) and all
> > the
> > >> rest. The first one is the only one guaranteed to arrive, the rest
> > depends on
> > >> the carrier delivering further messages with the status updates.
> > >> 
> > >> Another important thing to note is that Kannel has its own internal
> set
> > of
> > >> statuses, that doesn't relate to CIMD2's statuses, so a CIMD2 status
> > "1"
> > >> doesn't mean it should be store as "1" on Kannel (Kannel implement
> > various
> > >> SMSC protocols and they all differ on that kind of stuff, so Kannel
> > uses its
> > >> own internal set of codes to abstract the different protocol
> > >> implementations).
> > >> 
> > >> What dlr-mask are you using?
> > >> 
> > >> Regards,
> > >> --
> > >> Alejandro Guerrieri
> > >> [email protected]
> > >> 
> > >> 
> > >> 
> > >> On 20/01/2011, at 12:31, Beatrice Tamburrino wrote:
> > >> 
> > >>> Hi Alejandro
> > >>> 
> > >>> Thanks for your feedback.
> > >>> 
> > >>> 
> > >>> Yes I can confirm that "sometimes" the DLR type 1 is coming - thats
> > the
> > >> strange thing, sometime it does... but often I only receive the type
> 8,
> > and
> > >> when I receive the type 8 i can see on the status file that it queues
> a
> > >> DLR: DLR: 1 queued, using internal storage , so I think that (maybe
> > kannel)
> > >> is exactly queueing the type 1! or am I wrong?
> > >>> 
> > >>> I set the log-level to 0. I attache the logfile...
> > >>> 
> > >>> -------- Original-Nachricht --------
> > >>>> Datum: Thu, 20 Jan 2011 11:57:23 +0100
> > >>>> Von: Alejandro Guerrieri <[email protected]>
> > >>>> An: Beatrice Tamburrino <[email protected]>
> > >>>> CC: [email protected]
> > >>>> Betreff: Re: urgent help! CIMD2 missing DLR answer!
> > >>> 
> > >>>> Assuming you've setup the dlr-mask to "listen" to dlrs of type 1,
> are
> > >> you
> > >>>> sure that you're receiving the DLR from the carrier?
> > >>>> 
> > >>>> I don't know how that works on CIMD2 (I'm mostly the SMPP type) but
> I
> > >>>> guess you need the equivalent of a "deliver_sm" DLR coming from the
> > >> carrier.
> > >>>> The DLR you've got is actually created by kannel based on the
> > response
> > >> for
> > >>>> the CIMD2 equivalent for a submit_sm (in smpp it would be a
> > >> submit_sm_resp
> > >>>> PDU).
> > >>>> 
> > >>>> Set the log level to 0 on the SMSC bind and see if you're getting
> the
> > >>>> DLR's back, otherwise it might be your carrier's problem.
> > >>>> 
> > >>>> Regards,
> > >>>> --
> > >>>> Alejandro Guerrieri
> > >>>> [email protected]
> > >>>> 
> > >>>> 
> > >>>> 
> > >>>> On 20/01/2011, at 11:52, Beatrice Tamburrino wrote:
> > >>>> 
> > >>>>> Hi!
> > >>>>> 
> > >>>>> I have a really urgent problem! We have Kannel 1.4.3 Operating on
> > the
> > >>>> customer site.. using the protocol cimd2 to an SMSC (actually we
> have
> > 5
> > >>>> different SMSC) but the customer wants us to send the SMS only to
> the
> > >> first SMSC
> > >>>> (named sc1)- the SMSC provider has confirmed that he allows DLR (so
> > far
> > >> so
> > >>>> good)
> > >>>>> 
> > >>>>> Im facing some strange problem that I cant understand:
> > >>>>> 
> > >>>>> When I send a message, I quickly receive the ack and the DLR code
> 8.
> > >>>> This is good, means the DLR funtion works and the SMSC has received
> > our
> > >>>> message. I sent the message to my phone and I could see that the
> > >> message was
> > >>>> delivered on my phone. than I waited for the DLR code 1 (confirmed
> > >> deliver to
> > >>>> the phone) but I saw in my logs that the code 1 was never received.
> > I
> > >>>> tested a lot of times and I saw that sometimes (very rarely) I also
> > >> received the
> > >>>> code 1! So sometimes it workes but the most time I get
> > >>>>> only the 8.
> > >>>>> 
> > >>>>> I cecked the status file of the kannel- there I could see the
> follow
> > >>>> entry.
> > >>>>> 
> > >>>>> DLR: 3 queued, using internal storage
> > >>>>> 
> > >>>>> Box connections:
> > >>>>>  smsbox:smsbox_XXXX, IP 127.0.0.1 (0 queued), (on-line 0d 0h 23m
> > 17s)
> > >>>>> 
> > >>>>> SMSC connections:
> > >>>>>  sc1    CIMD2:xxx.xxx.xxx.xxx:yyy:ZZZZ (online 1229s, rcvd 5, sent
> > 4,
> > >>>> failed 0, queued 0 msgs)
> > >>>>> 
> > >>>>> What I dont understand: the DLR: 3 queued entry seems that the
> > missing
> > >>>> DLR code 1 is somekind of buffered?? so this are the 3 missing DLR
> > >> answer
> > >>>> that I need. Is that problem on Kannel side or provider side??? I
> > would
> > >>>> appreshiate if somebody could explain what this means and maybe
> also
> > >> give me a
> > >>>> hint how to solve this!! :)
> > >>>>> 
> > >>>>> 
> > >>>>> 
> > >>>>> I need to solve this till tomorrow, and after LONG time research I
> > >>>> really dont have a clue what to do know.. 
> > >>>>> 
> > >>>>> Pleas help!!!
> > >>>>> 
> > >>>>> many many thanks in advance!
> > >>>>> 
> > >>>>> cheers
> > >>>>> 
> > >>>>> beatrice
> > >>>>> 
> > >>>>> -- 
> > >>>>> Neu: GMX De-Mail - Einfach wie E-Mail, sicher wie ein Brief!  
> > >>>>> Jetzt De-Mail-Adresse reservieren:
> > http://portal.gmx.net/de/go/demail
> > >>>>> 
> > >>>> 
> > >>> 
> > >>> -- 
> > >>> NEU: FreePhone - kostenlos mobil telefonieren und surfen!			
> > >>> Jetzt informieren: http://www.gmx.net/de/go/freephone
> > >>> <smsc_sc1_cimd2.log>
> > >> 
> > > 
> > > -- 
> > > Sicherer, schneller und einfacher. Die aktuellen Internet-Browser -
> > > jetzt kostenlos herunterladen! http://portal.gmx.net/de/go/chbrowser
> > 
> 
> -- 
> Sicherer, schneller und einfacher. Die aktuellen Internet-Browser -
> jetzt kostenlos herunterladen! http://portal.gmx.net/de/go/chbrowser
> 

-- 
Ihr GMX Postfach immer dabei: die kostenlose GMX Mail App für Android.
Komfortabel, sicher und schnell: www.gmx.de/android