| Originating Address in MMSC logs for MM4 interface |  Search
|
|
NowSMS Support Forums ⬆ NowSMS Support - MMS & Advanced Issues ⬆ Archive through July 28, 2006 ⬆ |
◄ ► |
| Author | Message | |||
| Gustavo Sepulveda New member Username: Gsepulve Post Number: 1 Registered: 04-2004 |
Hi, I have running nowsms in our cdma network working as MMSC, and we have MM4 interfaces connected to other MMSC´s fron other companies. Works fine, only problem is with billing, because MMSC logs, for incoming VASP conection, only register Ip address of the VASP Server, and It don´t register the real originating address. My question is: What can I do in NowSMS in order to have Phone number or originating address of the MMS arriving on MM4 interface,in MMSC logs files.? Follow is a logs curently received. 2006-03-22 00:06:02,MMSIN,172.16.54.32,VASP:172.16.54.32,+5684917997,20060322/00/FB7A6569,S AR-+5684917997-bf-2-1.req,493 Thanks in advance. Gustavo | |||
| Bryce Norwood - NowSMS Support Board Administrator Username: Bryce Post Number: 5723 Registered: 10-2002 |
Hi Gustavo, The information that you are interested in should be present in the accounting callbacks. The accounting callback would have the originating phone number in the "From=" parameter, and the name of the VASP from which the message was received in the "VASPIN=" parameter. We definitely should update the accounting interface documentation at: http://www.nowsms.com/support/bulletins/tb-nowsms-001.htm But the key difference is that if the message was received from an incoming VASP connection, there is a VASPIN parameter to identify it. And if the message is routed outbound to an "MMSC Routing" definition, there is a VASP parameter to identify the route. We've concentrated more on updating these accounting callbacks for billing purposes, more so than the log files. If you can't work with the accounting callbacks, we can look at adding this information to the log files (as it really should also be there), but we need to do more investigation to determine the effort involved in implementing this. -bn | |||
