Trouble with mmsrouting callback

Trouble with mmsrouting callback SearchSearch

SMS & MMS Technical Forum » NowSMS Support - MMS & Advanced Issues (Product Support Only) » Trouble with mmsrouting callback « Previous || Next »
Author Message
marc bazimon
Frequent Contributor
Username: Marc_orange

Post Number: 81
Registered: 01-2007
Posted on Tuesday, September 03, 2019 - 11:26 am:   

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 ?
application/vnd.openxmlformats-officedocument.wordprocessingml.documentlog and tcpdump
MMSC LOG_issue routing.docx (252.7 k)

Thanks beforehand for your feedback,
Br
Marc
Des - NowSMS Support
Board Administrator
Username: Desosms

Post Number: 6040
Registered: 08-2008
Posted on Tuesday, September 03, 2019 - 07:52 pm:   

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
Posted on Wednesday, September 04, 2019 - 06:56 am:   

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

Add Your Message Here, or click here to create a new discussion topic.
Post:
Bold text Italics Underline Create a hyperlink Insert a clipart image
Posting Information:
This is a private posting area. Only registered users and moderators may post messages here.
Click here to create an account.
Username:
Password:
Options: Automatically activate URLs in message
Action:

Login Login / Register Logout Logout Search Last 30 Days Topics Topics