Error log on MMSC - NowMMS- OMADA

Error log on MMSC - NowMMS- OMADA SearchSearch
Author Message
Rambeloson Andry Juvenale
New member
Username: Andry_juvenale

Post Number: 7
Registered: 01-2014
Posted on Tuesday, June 24, 2014 - 03:22 pm:   

Dear Support
We come back to you on this topic. since yesterday 06/23/2014, we receive a several Error logs generated by NowMMS / SMS. We performed a service failover from Node1 to Node2 on WAPGATEWAY side and the service works fine till now. but the service does not work on the MMS side(we have not made any changes of node on MMS.). Could you explain us these errors. below an extract Logs from MMS-20140624.LOG

2014-06-24 16:30:15,MMSIN,10.150.0.115,,,User Not Defined,FAILED
2014-06-24 16:30:29,MMSIN,10.150.0.115,,,User Not Defined,FAILED
2014-06-24 16:30:52,MMSIN,10.150.0.115,,,User Not Defined,FAILED
2014-06-24 16:31:01,MMSIN,10.150.0.115,,,User Not Defined,FAILED
2014-06-24 16:31:03,MMSIN,10.150.0.115,,,User Not Defined,FAILED
2014-06-24 16:31:19,MMSIN,10.150.0.115,,,User Not Defined,FAILED
2014-06-24 16:32:09,MMSIN,10.150.0.115,,,User Not Defined,FAILED
2014-06-24 16:34:13,MMSIN,10.150.0.115,,,User Not Defined,FAILED
2014-06-24 16:36:13,MMSIN,10.150.0.115,,,User Not Defined,FAILED
2014-06-24 16:37:20,MMSIN,10.150.0.115,,,User Not Defined,FAILED
2014-06-24 16:41:25,MMSIN,10.150.0.115,,,User Not Defined,FAILED
2014-06-24 16:47:30,MMSIN,10.150.0.115,,,User Not Defined,FAILED
2014-06-24 16:55:36,MMSIN,10.150.0.115,,,User Not Defined,FAILED
2014-06-24 17:00:04,MMSIN,10.150.0.115,,,User Not Defined,FAILED

Thank you in advance for your support.
Best regards
Andry Juvenale
orange Madagascar
Des - NowSMS Support
Board Administrator
Username: Desosms

Post Number: 4937
Registered: 08-2008
Posted on Tuesday, June 24, 2014 - 03:46 pm:   

Hi Andry,

This means either the X-MSISDN header is not being inserted by the WAP gateway (possibly due to configuration of the WAP gateway, or lack of RADIUS accounting feed to the Node2 WAP gateway).

Or possibly the MMSC is configured to trust the X-MSISDN header from Node1 WAP Gateway, but not Node2 WAP Gateway.

Refer to this article for an explanation of how the process works: http://www.nowsms.com/doc/mmsc-messaging-server/operator-mmsc-considerations

If it worked via Node1 WAPGW, but not Node2, the first thing I would check is the MSISDNHeaderGateways setting in MMSC.INI ... Node1 is likely in this list, verify that Node2 (10.150.0.115) is also in the list.

If that setting is ok, then the problem is in the WAPGW configuration, or the RADIUS accounting feed is not being sent from the GGSN to the WAPGW. Is the WAPGW NowWAP? If so, is there a RADIUS-yyyymmdd.LOG in the NowWAP directory? This log would show RADIUS transactions received. The link above also has instructions on configuring NowWAP to receive a RADIUS accounting feed.

--
Des
NowSMS Support