Can you please let me know which flag to look for in SMPP trace? Although I am already comparing the tcp trace of a true long message with the one my provider is sending, still it would be helpful to know what exactly to look for.
On Tue, Mar 10, 2015 at 8:50 PM, Alvaro Cornejo <cornejo.alv...@gmail.com> wrote: > Hi > > Might be that your SMSC is not compliant with the concatenate specs and > just use that + signs to indicate the next part of the message. > > Ask you provider about this. > > You can also check logs and/or tcp dump to verify message has the > concatenate flag enabled and set correctly. Compare logs/tcp dumps with > those from your other smsc's > > Regards > > Alvaro > > > |-----------------------------------------------------------------------------------------------------------------| > Envíe y Reciba Datos y mensajes de Texto (SMS) hacia y desde cualquier > celular y Nextel > en el Perú, México y en mas de 180 paises. Use aplicaciones 2 vias via SMS > y GPRS online > Visitenos en www.perusms.com > > On Tue, Mar 10, 2015 at 8:06 AM, ha...@aeon.pk <ha...@aeon.pk> wrote: > >> Hi, >> >> My kannel is receiving long SMS from the operator's SMSC in weird >> fashion. The message is broken into 2 parts, with first part getting >> truncated at 154 characters ending with a '+' sign, and second part is >> appearing as a new SMS with text starting with the '+' sign. I do have >> 'sms-combine-concatenated-mo' >> parameter set to true, but still a long message appears as 2 separate >> messages. >> >> Please note that the same bearerbox is connected to 3 more SMSCs from >> different operators, and is working fine for long messages coming from >> those. This issue is coming only over 1 SMPP connection. >> >> Any clues? >> >> Regards, >> Hamza >> > >
