| Recipient address(es) to route to this user issues |  Search
|
|
NowSMS Support Forums ⬆ NowSMS Support - SMS Issues ⬆ |
◄ ► |
| Author | Message | |||
| liudas New member Username: Bogiukas Post Number: 21 Registered: 08-2011 |
Hey Team, I am interested in forwarding incoming sms to other smpp (LocalUser) when any number is added in "Recipient address(es) to route to this user" field and "Accept received messages for this user" is checked. Its clear when NowSMS receives a message, it records the recipient address, and it then knows to route the received message to an "SMS Users" account where the client can receive the message via SMPP. However having this configuration problem appears for using the same number (which is added in recipient address) as a sender ID for submiting outgoing messages. In this case sender ID is recognized as recipient address and all messages including DLR are routed to Local user which is not good due to dublication and overloading system. Additionally, DLR in SMS-IN is not created and server doesnt have DLR because all is routed to Local user. for example: 1. "recipient address to route to this user" is set +44xxxxxxxx so any inbound messages are routed to Users account - no issue. 2. in order to make client to reply to +44xxxxxxxx need to send sms to him initially so sending sms and using sender name as +44xxxxxxxx system recognizes this number as recipient address and start routing everything what is related with this number (outgoing/inbound sms/DLR). 3. DLR in SMS-IN is not created and not possible to add in DB information. Is there known problem? What configuration/set up must be used to avoid this issue? Is possible somehow to trick the system by not recognizing sender name as recipient address which would solve the problem? Cannot wait Your answer. Thanks Bogiukas | |||
| liudas New member Username: Bogiukas Post Number: 22 Registered: 08-2011 |
Team, Any updates? B | |||
| Bryce Norwood - NowSMS Support Board Administrator Username: Bryce Post Number: 8494 Registered: 10-2002 |
Hi, We are not able to recreate this behavior. Everything works as expected when we attempt a similar configuration. As a test, I edited an SMS user account, adding a value of +999999999 to "recipient address to route to this user". Messages to +999999999 get routed to this user account. Messages with a sender of +999999999 get routed outbound as expected. There must be some other issue specific to your configuration, or perhaps a protocol specific issue. What version of NowSMS? Do you have an accounting callback defined that performs message routing? To troubleshoot, I would like to see relevant log entries from SMSIN-yyyymmdd.LOG, SMSWEB-yyyymmdd.LOG and SMSOUT-yyyymmdd.LOG that reference these messages. That would help me understand what is different between my test setup and your system. Regards, Bryce Norwood NowSMS Support | |||
| liudas New member Username: Bogiukas Post Number: 23 Registered: 08-2011 |
Hi Bryce, Thanks for reply. You are right till that moment everything as expected. However, problem starts with delivery receipt of this outbounded number +999999999. DRL comes and gets routed to user account who has edited value of +999999999 in "reccipient address to route to this user" as well as incoming messages because sender name is recognized edited number. In addtion I believe (need to check again) file for DLR in SMS-IN folder is not created. I hope now is clear tricky spot. I tested the latest version, no any callbacks were set, if needed can play again and provide logs. Cannot wait Your answer Bogiukas | |||
| liudas New member Username: Bogiukas Post Number: 24 Registered: 08-2011 |
Bryce, Like that: a. SMSOUT-20230427.LOG file 1. Sending sms: 2023-04-27 20:49:04,72F59FEA,127.0.0.1,+9999999999,OK -- SMPP - 222.22.222.22:1111,SubmitUser=test;SMSCRouteName=test1;Sender=+77777777777;SMSCMsgId=187c3d533110;Text="testing" 2. Routing (to "recipient address to route to this user"): 2023-04-27 20:49:28,72F59FFT,,+77777777777,OK -- LocalUser:client1,SubmitUser=SMPP - 222.22.222.22:1111;Sender=+9999999999;Text="id:187c3d533110 sub:001 dlvrd:001 submit date:2304271949 done date:2304271949 stat:ENROUTE err:215 text:" b. SMSIN-20230427.LOG file Getting report: 2023-04-27 20:49:28,+9999999999,SMPP - 222.22.222.22:1111,Text="id:187c3d533110 sub:001 dlvrd:001 submit date:2304271949 done date:2304271949 stat:ENROUTE err:215 text:";SMSCRouteName=test1;Recip=+77777777777;SMSCReceiptMsgId=187c3d533110 c. SMS-IN folder 72F59FEA.SMS file NOT created d. Issue: 1. if DLRs to process are taken from folder SMS-IN then no DLRs are provided. This valid only in the case when sender name is NUMERIC the same as used in to "recipient address to route to this user". 2. If sender name is ALPHA then no issue because no routing is involved. 3. Incoming sms (2way sms) works good. Do You see where is problem? Bogus } | |||
| liudas New member Username: Bogiukas Post Number: 25 Registered: 08-2011 |
Bryce, Is there any possibility to enable Delivery Receipt to be generated into SMS-IN folder? B | |||
