| Problem with smscRoute |  Search
|
|
NowSMS Support Forums ⬆ NowSMS Support - SMS Issues ⬆ Archive through April 16, 2015 ⬆ |
◄ ► |
| Author | Message | ||||
| Ahmed Negm New member Username: Anegm Post Number: 2 Registered: 04-2014 |
, I am new user from NowSms and I am trying to configure new SMPP connection between two NowSMS , I added SMPP connection on Server A to talk to Now SMS on Server B which have many SMPP connection with different SMSCRoute and I am trying to route all message received on Server A to specific SMSCRoute on server B , the problem is each time I send message to server B its assigned to different SMSCRoute so It’s not delivered to the end user as each SMSCRoute for one operator . Appreciate your prompt support | ||||
| Des - NowSMS Support Board Administrator Username: Desosms Post Number: 4861 Registered: 08-2008 |
Hi, I need to better understand your configuration. Let me ask a few questions to make sure I understand. On Server A, is there an SMSC connection for Server B? And on Server B, is an "SMS User" account defined for Server A? Are all messages that are routed from server A to Server B to use the same outbound SMSC connection on Server B, or different Outbound SMSC connections? I will try to help, but I need to make sure I understand. -- Des NowSMS Support | ||||
| Ahmed Negm New member Username: Anegm Post Number: 3 Registered: 04-2014 |
Thank You dear for your answer , on server A there is SMSC connection for Server B and there is SMS User On server B for Server A . the messages routed from server A to server B every time to another SMSCRoute Name on server B , the messages should routed to specific SMSCRoute on server B | ||||
| Des - NowSMS Support Board Administrator Username: Desosms Post Number: 4862 Registered: 08-2008 |
OK...hmm... I don't see an easy way to do this other than forcing the sender address. But I do have another more complicated setting that will work exactly as you want. On Server B, add the following to SMSGW.INI: [SMPP] SMSCRouteTLV=777 The above indicates that if a message is received from an SMPP Client (SMS User), then SMPP TLV parameter 0x777 should be interpreted as the SMSCRoute parameter for the message. On Server A, add the following to SMSGW.INI: [SMPPOptions] SMSCRoute=777,String The above tells server A that there is a TLV parameter named SMSCRoute, which is encoded as tag #0x777. Also on server A, in SMSGW.INI, locate the [SMPP - server:port] section that defines the connection to server B. Under that section header, add: DefaultSMPPOptions=SMSCRoute=routename Replace routename with the name of the route on server A. The above setting indicates that when transmitting messages to Server B, it should add TLV parameter SMSCRoute (0x777) with a value of routename. The above settings should ensure that when messages are transmitted from Server A to Server B, Server B can see the routename to be used, because it is passed in a TLV parameter. There may be an easier way to do this, but if there is it escapes me at present. This is a little complicated but should do exactly what you want. - Des NowSMS Support | ||||
| Ahmed Negm New member Username: Anegm Post Number: 4 Registered: 04-2014 |
Thanks Dear but i have problem with where i will write the mentioned setting attached sample from server A SMSGW , can you please tell me where i can add these setting ! Thanks in advanced
| ||||
| Des - NowSMS Support Board Administrator Username: Desosms Post Number: 4865 Registered: 08-2008 |
Under the [SMPP - IP:port] header add: DefaultSMPPOptions=SMSCRoute=routename Create a new section: [SMPPOptions] SMSCRoute=777,String (Include the above as is...String is literal...you are indicating the parameter type is String.) Then on the other server: [SMPP] SMSCRouteTLV=777 If an [SMPP] section already exists, add to it. Also make sure you have RouteName=routename for the [SMPP - ip:port header for the connection you want to be used for outbound routing of those messages. -- Des NowSMS Support | ||||
| Ahmed Negm New member Username: Anegm Post Number: 5 Registered: 04-2014 |
Thank You for your support , its working with me now | ||||
| Ahmed Negm New member Username: Anegm Post Number: 6 Registered: 04-2014 |
(I know that it is out of thread subject, but I can't create a new one) Dear support, I got another issue, I'm trying to send a text message with the following body "Test chars ! @ # $ % ^ & * () = - _ + <> ~", but I get the message with incorrect symbols for some of above special chars, I tried to follow instructions here "http://www.nowsms.com/long-sms-text-messages-and-the-160-character-limit" but I got the same result. please advise. kindly note that if I sent the message in Arabic (unicoded) I got it correctly but the problem in the plain texts only. I'm looking forward for your reply | ||||
| Des - NowSMS Support Board Administrator Username: Desosms Post Number: 5068 Registered: 08-2008 |
Hi, Apologies for the delay in response. See here: http://www.nowsms.com/smpp-character-set-issues Specifically issue "a". 9 times out of 10, the solution is to go into the “Advanced Settings” for the SMPP connection in NowSMS and change the “SMSC Character Set” to “iso-8859-1 as Default”. Note that in order to save and activate that setting change it is necessary to press “OK” twice then “Apply” when you are returned to the “SMSC” list. (If NowSMS asks if you wish to test the SMSC connection, it is ok to answer “No”.) Wait about 60 seconds for the server to activate the settings change and try another test message. -- Des NowSMS Support | ||||
