RE: SMPP 3.4 Optional Fields
"Oded Arbel" <[email protected]>
| Newsgroups | gmane.comp.mobile.kannel.devel |
|---|---|
| Message-ID | <[email protected]> |
Indeed SMPPv3.4 can use message_payload, and if you are using that version, they can sure avoid using message_text. Have you tried setting the interface-version configuration parameter to 33 ? -- Oded Arbel m-Wise mobile solutions [email protected] +972-9-9581711 (116) +972-67-340014 ::.. Math is like love -- a simple idea but it can get complicated. -----Original Message----- From: Troy Kelly [mailto:[email protected]] Sent: Monday, October 28, 2002 2:03 AM To: '[email protected]'; '[email protected]' Subject: SMPP 3.4 Optional Fields Hi, I was curious to see if any body has developed a way to handle the 'optional' SMPP 3.4 fields (such as message_payload). Our carrier is insistent that SMPP 3.4 does not use the message_text field - but only the message_payload field. We had developed a hack previously that is now failing as it assumed there would only ever be one optional field delivered; now our carrier occasionally delivers other optional fields. It is no fun arguing with a large telco! Regards, Troy Kelly http://www.webcentral.com/ AU: 1800-800-099 NZ: 0800-440-077 MSN: [email protected]