Weird. it looks like a the old behaviour of SMPP which was broken but was fixed quite
a long time ago. maybe you have a problem with the message ID received from the SMSC
being hex instead of decimal or the other way around. check the message id
configuration feature recently introduced by
Try setting interface_version to 33 - that sometimes solves the problem with nice
SMSCs that check what version the client supports and only uses fields supported by
v3.3 if the interface version is set to that - for example, CMG.
--
Oded Arbel
m-Wise mobile solutions
[EMAIL PROTECTED]
Your openssl package is not registered to provide libcrypto.so. known problem with
redhat. if you know for sure that it is installed, just use --nodeps or get the source
RPM and --rebuild it on your computer.
--
Oded Arbel
m-Wise mobile solutions
[EMAIL PROTECTED]
+972-9-9581711 (116)
don't use the --force switch to install RPMs, unless you are 200% sure you know what
you are doing - it can cause tons of grief if used w/o proper caution. the --nodeps
OTOH is usually quite safe - unless you are upgrading glibc or something, at the most
it would cause your newly installed
