hi,
we are experiencing something strange
we have smpp server with some clients running on diferent platforms
when sending Deliver_SM to almost they return Deliver_SM_Resp that server understand correctly and show status ESME_ROK
but there is a Perl-SMPP client running on Linux that who's Deliver_SM_Resp is misunderstood at server and it shows status SMPPCLIENT_UNEXPRESP
We've found that Perl Client is sending message_id on PDU but other clients doens't
SMPP doc says something like "message_id is unused and must be set to null"
Is that message_id the reason? Really should it be set to null?
Thanks
--
Sample PDU Stream
--
Short Message Peer to Peer, Command: Deliver_sm - resp, Status: "Ok", Seq: 22, Len: 53
Length: 53
Operation: Deliver_sm - resp (0x80000005)
Result: Ok (0x00000000)
Sequence #: 22
Message id.: 942f9376-74ed-4988-b4c7-ea6708b72035
Bad Deliver_SM_Resp received
Re: Bad Deliver_SM_Resp received
Hello didimo,
Yes, in SMPP doc message_id is always null. But I'll add support of this filed in the next version.
Yes, in SMPP doc message_id is always null. But I'll add support of this filed in the next version.
Re: Bad Deliver_SM_Resp received
MessageId field now supported since version 1.1.14.2
Re: Bad Deliver_SM_Resp received
thanks!
we will try this on new version...
we will try this on new version...