Hi,
I was asking for the raw logs, to verify that is indeed SMPP traffic, as
stated from the PDU names. If it is, then it seems contrary to the spec. He
could try talking to his SMSc about it.
BR,
Nikos
----- Original Message -----
From: "Alan McNatty" <[email protected]>
To: "Alejandro Guerrieri" <[email protected]>
Cc: "users" <[email protected]>
Sent: Thursday, February 17, 2011 11:36 PM
Subject: Re: Odd DLR msg ID from operator
Hi Alex,
I wonder (just off the top of my head) .. if using DB DLR with stored
procedure / trigger could work by stripping the prefix on insert?
Just a random idea that could be worth looking into - possible/obvious
performance implication.
Cheers,
Alan
On 18/02/11 10:26, Alejandro Guerrieri wrote:
Looks like the SMSC is doing fancy stuff with their DLR's.
If that's the case, there's no easy fix, it's either asking your SMSC
to change it (probably unlikely) or tweaking the code to ignore those
two digits before the first "/".
Regards,
Alex
On Thu, Feb 17, 2011 at 10:30 AM, Kyriacos Sakkas
<[email protected] <mailto:[email protected]>> wrote:
Hi,
Wondering if anyone can help with this.
When I submit an sms I get the following ID in the submit_sm_resp:
*01*//415ce0ae676d19fc000000000000000000000000/1231615516543
When the message is delivered I get the following id in the
deliver_sm:
*04*/415ce0ae676d19fc000000000000000000000000/1231615516543
As you can see those two numbers are not the same, leading to the
query not matching.
Any help will be greatly appreciated, I can provide further info
if needed.
Regards,
Kyriacos Sakkas
--
Kyriacos Sakkas
Development Team
Netsmart
Tel: + 357 22 452565
Fax: + 357 22 452566
Email: [email protected] <mailto:[email protected]>
http://www.netsmart.com.cy
Taking Business to a New Level!
** Confidentiality Notice: The information contained in this email
message may be privileged, confidential and protected from
disclosure.
If you are not the intended recipient, any dissemination,
distribution,
or copying of this email message is strictly prohibited.
If you think that you have received this email message in error,
please
email the sender at [email protected]
<mailto:[email protected]> **