2 way sms, a few trouble with CIMD2

2 way sms, a few trouble with CIMD2 SearchSearch
Author Message
Stef
New member
Username: Stef

Post Number: 1
Registered: 07-2006
Posted on Tuesday, July 18, 2006 - 10:38 am:   

Hello,

I am currently trying out NowSMS to a project. The objective is to receive messages from different SMPP and CIMD2 connections and reply back with a generated sms. Reply must be channeled through the same SMPP or CIMD2 where it originally came from. The different SMPP/CIMD2 represent a combination of different numbers that mobiles sent sms to and different mobile telephony providers. That is, 2 numbers and 3 providers for example result 6 SMPP/CIMD2.

So far so good, i have create and test all the SMPP/CIMD2 connections. SMS are coming through a specific SMPP/CIMD2 depending the number and the provider. I get the SMS, create the reply and sent it back through the specific SMPP/CIMD2

There is only 1 problem and i dont even know if it is something about NowSMS or not

I have 2 different CIMD2 connections. They serve different numbers i get sms, for the SAME provider. Those CIMD2 have same Server Host Name (IP address) and same port, different username and password for their connection and both support incoming and outgoing sms traffic.

The 'problem' is that there are a lot of retry attempts at the log files for the OUTGOING sms only.

This is an example of a normal sms within the log:
2006-07-18 00:04:36,44BB79AB.req,195.97.30.42,306974701048,OK -- CIMD - 195.167.65.245:9971,SubmitUser=stef;Text="TΩPA ΣTEIΛE TO MONTEΛO TOY KINHTOY ΣOY ΠX 6600"

And this is an example of e retry:

2006-07-18 00:10:44,44BB79D5.req,195.97.30.42,306979778540,Retry Pending - ERROR: Timeout waiting for response from server or lost connection -- CIMD - 195.167.65.245:9971,SubmitUser=stef

If i delete 1 of the CIMD2 connections, the retry attempts are totaly gone!

If you have a clue about it it would be really helpfull since everything else is working fine and this is the only issue i have seen so far.

Thank you in advance
Bryce Norwood - NowSMS Support
Board Administrator
Username: Bryce

Post Number: 6238
Registered: 10-2002
Posted on Wednesday, July 26, 2006 - 07:59 pm:   

Hi Stef,

Do the 2 different CIMD connections show up in the NowSMS list where one of them has "#2" appended after it? If not, that could be a problem.

If that "#2" suffix is showing up properly, then I wonder ...

We've got a lot of customers that have multiple SMPP connections, or multiple UCP/EMI connections. But I can't recall any with multiple CIMD2 connections. So perhaps there is an issue.

I'd like to see a CIMDDEBUG.LOG file to try to check out what is occurring.

Enable the CIMDDEBUG.LOG by enabling the SMSDEBUG.LOG on the "Serial #" page of the configuration dialog.

As the log file will contain passwords, you might not want to reply with it here (although you could edit the passwords out). Either reply here with the CIMDDEBUG.LOG as an attachment ... or send an e-mail to nowsms@now.co.uk with "Attention: Bryce" in the subject line, and the log file attached ... referencing this thread. And I'll take a closer look.

-bn
Stef
New member
Username: Stef

Post Number: 2
Registered: 07-2006
Posted on Thursday, July 27, 2006 - 11:35 am:   

Bruce,
Thank you very much for your instant answer and support.

Yes, nowsms automatically fix the names for me, i copy to you the names as i take them off the smsgw.INI file.

Modem3=CIMD - 195.167.65.245:9971
Modem7=CIMD - 195.167.65.245#2:9971

And yes, watching the list at SMSC tab i can see the #2 after the IP address and before the port.

I will sent you the CIMDDEBUG.LOG to the e-mail you request. Together with the log i will write the results i had, in a general view, after i make some expirements with some SMSC options at the smsgw.INI file.

Thank you in advance
Bryce Norwood - NowSMS Support
Board Administrator
Username: Bryce

Post Number: 6260
Registered: 10-2002
Posted on Friday, July 28, 2006 - 08:33 pm:   

Follow-up ...

Stef sent me the logs, and we determined that there was a packet sequencing problem if NowSMS was configured to connect simultaneously to 2 or more CIMD2 connections.

There was also a related bug where NowSMS would not properly recover from a packet sequencing problem in a CIMD2 environment.

As I mentioned to Stef, we see a lot of customers with multiple SMPP connections, multiple EMI/UCP connections, and/or multiple GSM modems ... but this is the first time I recall a setup with multiple CIMD2 connections.

We've produced an update which resolves the packet sequencing problem with multiple CIMD2 connections, and that fixes the problem in the recovery logic should a packet sequencing problem occur.

Temporarily this update for NowSMS 2006 is available for download as http://www.nowsms.com/download/20060727.zip. The fix will be included in all future updates.

-bn