Long text message | Search |
NowSMS Support Forums ⬆ NowSMS Support - SMS Issues ⬆ Archive through September 26, 2009 ⬆ |
◄ ► |
Author | Message | |||
Omar New member Username: Kfsmart Post Number: 18 Registered: 01-2008 |
Dear Des, I'm testing a new connectivity,but my problem is the long messages. If I sent the message(for example 2 messages) through nowsms ,nowsms spilts into the message the first is 160chars and the second is empty without text paramter. This this log 2009-04-09 21:51:02,SAR-971503004950-a1-2-1.req,208.43.51.106,971503004950,OK -- SMPP - xxxxx,SubmitUser=xxx;Sender=971503004950;SMSCMsgId=994972820604;Text="aklds,kdkl dskldsl ds,ds,ldsl d,sl,lds,ldsl,,,,,,,,,,,,,,,,,,,,,,,,,,,,,sddddddddddddddsdsssssssssssssssssssss ssdsdsdsdssddsdssddsdsdsdsdsdsdsdsdsssssssssssssdsdsdsdsdsdsdsdsssssssdsdsdssdds dsdsdsdsdsdsdsddsdsds" 2009-04-09 21:51:02,SAR-971503004950-A1-2-2.req,208.43.51.106,971503004950,OK -- SMPP - xxxxx:xxx,SubmitUser=Zbulk;Sender=971503004950 look at the second split "there is no text paramter" Note :if I post the message through their URL,it will be ok but I have to add a paramter called split. then if the message is 2 long message then split=2 if 3 then split=3 What I must do in nowsms to handles this? Thanks for your time. | |||
Omar New member Username: Kfsmart Post Number: 19 Registered: 01-2008 |
Dear Des, MY SMPP connectivity Provider informed me that: "From our logs, these messages were sent without any payload –only UDH." I tried to check "USE TLV Parameters for port number and segmentation" but still I'm facing the same problem,but the differnece that now I'm getting 2 Empty messages. Check these from the log: 2009-04-13 11:10:23,SAR-971503004950-5c-2-1.req,127.0.0.1,971503004950,OK -- SMPP - as.sas.net:7004,SubmitUser=kamel;Sender=kamel2;SMSCMsgId=066972819101;Binary=1;U DH=0500035C0201;Data=C2E1F07C3E9FCFE7F3F97C3E9FCFE7F3F97C3E9FCFE70D45381C9ECFE7F 3F97C3E9FCFE7F3F97C3E9FCFE7F3F9BCA10887C3F3F97C3E9FCFE7F3F97C3E9FCFE7F3F97C3E9F3 714E170783E9FCFE7F3F97C3E9FCFE7F3F97C3E9FCFE7735043110E87E7F3F97C3E9FCFE7F3F97C3 E9FCFE7F3F97C3E0785C3E1F97C3E9FCFE7F3F97C3E9FCFE7 2009-04-13 11:10:24,SAR-971503004950-5c-2-2.req,127.0.0.1,971503004950,OK -- SMPP - as.ss.net:7004,SubmitUser=kamel;Sender=kamel2;SMSCMsgId=066982819102;Binary=1;UD H=0500035C0202;Data=E6F3F97C3E9FCFE7F3F97C3E9FCFE7F3F97C3E9FCF1B8A70383C9FCFE7F3 F97C3E9FCFE7F3F97C3E9FCFE7F379783E9FCFE7F3F97C3E9FCFE7F3F97C3E9FCFE7F379783E9FCF E7F3F97C3E9FCFE7F3F97C3E9FCF01 Note: I sent and English message not a binary message. | |||
Bryce Norwood - NowSMS Support Board Administrator Username: Bryce Post Number: 7760 Registered: 10-2002 |
Hi Omar, In this first situation (no text in the second split), this suggests that the setting "Enable WDP Adaptation" is enabled. That configuration is normally used only for WAP push in CDMA environments. When this setting is enabled, NowSMS recombines the message for submission and only submits one large message to the provider. Make sure that "Use WDP Adaptation" is NOT enabled. It is unusual to use this setting in most environments. What you need to do is experiment with some different settings, because there is not one right solution for every environment (the SMPP specification is vague, and different provider software implementations work differently). Here are the different settings that you should try: 1.) Encode long text messages with 7-bit packed encoding - NOT CHECKED Use TLV Parameters for port numbers and segmentation - NOT CHECKED 2.) Encode long text messages with 7-bit packed encoding - CHECKED Use TLV Parameters for port numbers and segmentation - NOT CHECKED 3.) Encode long text messages with 7-bit packed encoding - NOT CHECKED Use TLV Parameters for port numbers and segmentation - CHECKED One of those combinations should work properly, it's just a matter of testing to determine which one. Don't worry that the log files says the message is binary. That is just the way NowSMS records if if there are any user data header elements present (they are used for segmentation). -bn | |||
karite vert New member Username: Karite Post Number: 1 Registered: 04-2009 |
Hello all, i use php in my small application which consists to return a sms response. my probleme is in the sms received, there are a zero (0) added and empty afrer the text message on the phone. Mys script is : <?php header("Content-type: text/plain"); echo ".ceci est un test" ; ?> thank you. | |||
Des - NowSMS Support Board Administrator Username: Desosms Post Number: 724 Registered: 08-2008 |
For the last posting in this thread, refer to duplicate posting at http://support.nowsms.com/discus/messages/1/25067.html | |||
jarule lz New member Username: Jarulelz Post Number: 1 Registered: 05-2009 |
hi k chha missing ur family and susant toooooooo.......good night la fr uncle and aunt also | |||
Sarada Prasan Behera New member Username: Sprasan Post Number: 1 Registered: 07-2009 |
The "Use WDP Adaptation" enablement or disablement option is available only for connection type "SMPP over TCP/IP" , similarly many other options for fragmentation. Can someone suggest how to make fragmentation of messages work with "GSM Modem Connection".} Currently when I'm sending a long message, NOWSMS accepts the fragmented message, but the messages remain only in the Outbound queue, it doesnt able to send them out to the handset ( Modem Error: CMS 304)...Waiting for suggestions. | |||
Des - NowSMS Support Board Administrator Username: Desosms Post Number: 1005 Registered: 08-2008 |
Hi, When sending with a GSM modem, the message MUST be segmented for sending. If you're getting a CMS ERROR 304, then this suggests that you are using a Motorola phone as a GSM modem. Unfortunately, the GSM modem implementation in Motorola mobile phones has a long standing bug. If you try to send any message that includes user data header (segmented long text messages, WAP Push, EMS, port addressed messages for Java apps), the modem returns "CMS ERROR 304". There is no solution other than a different modem. -- Des NowSMS Support |