Trouble with mmsrouting callback | Search |
NowSMS Support Forums ⬆ NowSMS Support - MMS & Advanced Issues ⬆ |
◄ ► |
Author | Message | ||||
marc bazimon Frequent Contributor Username: Marc_orange Post Number: 81 Registered: 01-2007 |
Hi Since one week , we manage the traffic for Orange France through an MMS HUB. Before we had a direct VPN with OFR and route the traffic trough it. we have a strange behaviour here, i attach a document with what happen in the lOG from MMSC an a tcpdump taking from the MMSC on the interface that manage the mmsrouting callback. On the LOG , you can check that the mmsc show the old route ( OFR ) but if you check the tcpdump , the route returned is the HUB one. is it a king of cache on the routing callback mechanism ? the only think that could explain is the part of the mmsc.ini in which OFR is defined with the 336 , but HUB had the same. Any ideas of what could happen here ?
Thanks beforehand for your feedback, Br Marc | ||||
Des - NowSMS Support Board Administrator Username: Desosms Post Number: 6040 Registered: 08-2008 |
Hi Marc, I notice that this particular message is a delivery report. Are regular messages also misrouted? I ask because if a message comes in from a particular VASP connection, and there is a Route with the same name, we use that route for any reports. -- Des NowSMS Support | ||||
marc bazimon Frequent Contributor Username: Marc_orange Post Number: 82 Registered: 01-2007 |
Hi Des , thanks for your update The delivery report is an example, but regular message has got the same behaviour. it happen globally 50% of the case. Sometime it works , sometimes not. we thought about a loadsharing trouble with our routing frontal but the tcpdump trace doesn't lie ^^ Frontal send the good answer. i will try to find out , if the wrong route , come from the same incoming route. I will give you update asap, Br Marc |