RE: SMPP DLR

"Rene Kluwen" <[email protected]>
Newsgroups gmane.comp.mobile.kannel.devel
Message-ID <[email protected]>
Around line 1248 in gw/opensmppbox.c

 

It’s taking the SMPP v3.3 case only, and even that with a slight
modification.

 

== Rene

 

 

From: Porter, Kelvin [mailto:[email protected]] 
Sent: donderdag 13 februari 2014 19:36
To: Rene Kluwen; [email protected]
Cc: [email protected]
Subject: RE: SMPP DLR

 

Hi Renee,

 

Thank you for your response.  I will try it with the registered_delivery set
to 1.

 

Can you please give a hint as to where you think that the bug might reside
in opensmppbox?  I can take a look at the source and see if anything sticks
out?

 

Regards,

 

Kelvin R. Porter

 

From: Rene Kluwen [mailto:[email protected]] 
Sent: Thursday, February 13, 2014 5:12 AM
To: Porter, Kelvin; [email protected]
Subject: RE: SMPP DLR

 

I see that’s a bug in opensmppbox.

 

Try to set registered_delivery to 1 instead, meanwhile I come up with a fix.

 

== Rene

 

From: users [mailto:[email protected]] On Behalf Of Porter, Kelvin
Sent: woensdag 12 februari 2014 23:52
To: [email protected]
Subject: SMPP DLR

 

Hi,

 

I have a simple problem.  I have the following set up:

 

                Client –[SMPP]à opensmppbox à sqlbox à bearerbox –[SMPP]à
SMSC

 

My clients sends a submit_sm request into the opensmppbox, I can see that
the submit_sm message is marked requested_delivery: 31 = 0x0000001f in the
logs; however, when I see the corresponding submit_sm sent to the SMSC, I
see that requested_delivery is set to 0, in the logs for the SMSC
connection.  

 

The only impediment that I can think of is that my client(s) bind as
transmitter and receiver separately and not as a transceiver.  I can send
and receive messages with no problem.

 

What do I need to do to insure that the requested_delivery flag is correctly
relayed to the SMSC?

 

Thank you.

 

Regards,

 

Kelvin R. Porter
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.