NetXMS server crash when triggering SMS action to multiple destinations

[Anders]

I'm looking forward to it, keep up the great work!

[Anders]

Hi,

Did this fix make it into 1.2.5?

Regards

Anders

[victor]

Hi!

It should. Do you still have same issue with 1.2.5?

Best regards,
Victor

[NetS]

Hello. In 1.2.6 sms not send to multiple destinations. Only to first

[victor]

Hi!

Do you have any errors in server log? Was it working before 1.2.6?

Best regards,
Victor

[NetS]

No errors on log. I don't tested it before 1.2.6. I use modem ZTE and Windows 2008 r2 system.

How i can help to diagnostic it?

[victor]

Hi!

Just found a bug in PDU mode sender that can cause crash on 64-bit systems. Can you try to switch SMS driver to text mode?

Best regards,
Victor

[NetS]

how to make it?

[macro]

@nets said in NetXMS server crash when triggering SMS action to multiple destinations:

how to make it?

SMSDrvConfig has the following format:

Device[,PortSpeed[,DataBits[,Parity[,StopBits[,Mode]]]]]

Where Mode is either P (PDU) or T (Text). PDU is on by default.

For example: /dev/ttyUSB0,9600,8,n,1,T will enable SMS driver to send texts in plain text mode.

[NetS]

Thanks. But i allready transfer server from Windows Server 2008R2 to Ubuntu 12.04 x64.

Now it works for 2 of 3 Numbers. I tried to add dummy numbers and it works but passes numbers through one. First-work Second-no Third-Work Fourth-Work ... etc. I think that need delay for send sms, becouse driver not send correctly multiple numbers on one time.

[macro]

@nets said in NetXMS server crash when triggering SMS action to multiple destinations:

Thanks. But i allready transfer server from Windows Server 2008R2 to Ubuntu 12.04 x64.

Now it works for 2 of 3 Numbers. I tried to add dummy numbers and it works but passes numbers through one. First-work Second-no Third-Work Fourth-Work ... etc. I think that need delay for send sms, becouse driver not send correctly multiple numbers on one time.

I'm not sure if this is a driver's fault, but could be. The most obvious guess is that your modem needs some time to process an sms and ignores subsequent AT commands for this period of time. Please post your log here (or PM me) and we'll try to figure this out.