MMSC Routing "Ghost" Accounts

MMSC Routing "Ghost" Accounts SearchSearch

SMS & MMS Technical Forum » NowSMS Support - SMS Issues (Product Support Only) » Archive through May 20, 2013 » MMSC Routing "Ghost" Accounts « Previous || Next »
Author Message
Jeremy Baxendell
New member
Username: Jbaxendell

Post Number: 6
Registered: 12-2012
Posted on Tuesday, December 11, 2012 - 10:29 am:   

We've recently changed our VASP from Company A to Company B. To facilitate these changes we've changed the settings in the "MMSC VASP" tab for incomming messages. This is working fine.

We attempted the same things for "MMSC Routing", but we still see the Vasp Type listed as "Company A" Even though we deleted that account in the MMSC Routing tab.

In an attmpt to fix this, I deleted all accounts from MMSC Routing, went to the folders where the settings are kept, deleted the one labeled "Company A", and added a new account with the correct info for "Company A".

The VASPQ folder still shows recent .INI files as "TYPE=VASP:Company_A".

Where is it getting that name from?
Des - NowSMS Support
Board Administrator
Username: Desosms

Post Number: 4237
Registered: 08-2008
Posted on Tuesday, December 11, 2012 - 03:06 pm:   

Hi Jeremy,

If an MMS message is already queued, it will not get requeued by a configuration change like this.

However, I assume you are seeing new messages continue to be queued for this "ghost route"?

I think there are two possibilities.

First check MMSC.INI, and look for the [Outbound MMS Routing] section. It might still reference the old route.

Second, do you have an MMSRoutingURL reference in MMSC.INI? If you are using a custom routing callback that routine might be coded to use the old route name. (In that case, it might be easier to rename the route to use the old name.)

--
Des
NowSMS Support
Jeremy Baxendell
New member
Username: Jbaxendell

Post Number: 7
Registered: 12-2012
Posted on Tuesday, December 11, 2012 - 07:23 pm:   

At the end of MMSC.INI here's what the settings look like:

LogDirectory=C:\ProgramData\NowSMS\Records
[Outbound MMS Routing]


There's nothing below [Outbound MMS Routing]. Is this where the reference should go?

The MMSRoutingURL is: MMSRoutingURL=http://localhost:9800/Accounting/Default.aspx
Des - NowSMS Support
Board Administrator
Username: Desosms

Post Number: 4239
Registered: 08-2008
Posted on Tuesday, December 11, 2012 - 07:54 pm:   

The [Outbound MMS Routing] section would contain phone number patterns if you were routing based upon prefix. If this is empty, that type of routing is not being used.

I am not suggesting you need to apply any settings here, I am just asking as this is one mechanism that can be used to route messages. As it is not present, it is not responsible for the misdirection.

As you have an MMSRoutingURL defined, that is an interface for a customer created callback that determines how messages should be routed. Every time the MMSC needs to route a message, it queries this callback URL to ask it how the message should be routed.

Based upon the limited information that I have, I am suspicious that this callback is returning the name of the old route.

We don't provide the callback, this would be something developed by someone else at your organisation.

If messages are continuing to be routed to the old route name, I believe this callback is why. To avoid having to understand how the callback functions, the quickest solution would be to change the new route to reuse the old route name.

Before jumping to this conclusion, is there a DefaultOutboundRoute= setting present? That is settable in the user interface, but if it were still pointing to the ghost route, this would be the problem. I am assuming that this setting is either not present or not pointing to the ghost route...which points us to the MMSRoutingURL callback being responsible.

--
Des
NowSMS Support
Jeremy Baxendell
New member
Username: Jbaxendell

Post Number: 8
Registered: 12-2012
Posted on Tuesday, December 11, 2012 - 10:39 pm:   

Looks like changing the name worked; I'll look around our systems to see where that callback is being made.

Thanks again, Des!
Des - NowSMS Support
Board Administrator
Username: Desosms

Post Number: 4240
Registered: 08-2008
Posted on Tuesday, December 11, 2012 - 11:16 pm:   

Excellent. Here is info on how the MMS routing callbacks work from our perspective: http://www.nowsms.com/mobile-number-portability-mnp-and-the-nowsms-mmsc

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