Multiple IP support for MM4 VASPs? | Search |
NowSMS Support Forums ⬆ NowSMS Support - MMS & Advanced Issues ⬆ |
◄ ► |
Author | Message | |||
Robert Barretto New member Username: Barretto Post Number: 19 Registered: 09-2019 |
Hi, Is it possible to have the MMSC bind to multiple addresses and then assign a specific IP address to a VASP? Essentially, there is a current limitation on one of our MM4 providers that each of their customers must point to a unique MM4 server address (i.e., two of their customers can point to the same MM4 server IP). They have this limitation for SMS as well, and we're able to overcome this deficiency by adding a secondary IP on our ESME server that they could use to have a secondary bind to our server. In the definition of an MM4 VASP there's no was to set an local IP, only the remote IP address. Which makes sense, since I'm just defining a VASP based on the IP that it's coming from, not to where it's going (which is just the MMSC itself). Multiple IP support for MM4 VASPs? In the MMSC.INI, I can see: [MMSC] WebPort=80 HostName=37.x.x.99 SMTPPort=25 IPAddress=37.x.x.99 SMTPRequireAuth=No SMTPUseStartTLS=No SMTPUseAuth=No ... I have two MM4 VASPs defined, which are just the two regional MM4 servers from the MMS provider. The configurations are identical except for the "IP Address Restrictions" field which has the IP of the specific regional MM4 VASP server. On the MMSC tab, the IP Address has an "(all available)" option, so this looks promising. However, on the way out for MM4 originations, I don't see a way to select which source IP address to use when going out an "Additional Route", i.e., the MMS Outbound Routing config window, only has the remote server address, no source address. If I can't specify sending IP address (when there are multiple IP addresses on the Windows box), then the only way I think this would work would be to run multiple MMSC Gateway instances. I don't know if that's even doable on a single Windows box. Does this make sense? //Robert | |||
Robert Barretto New member Username: Barretto Post Number: 20 Registered: 09-2019 |
Edit... sorry for the typo... ...(i.e., two of their customers can NOT point to the same MM4 server IP)... that's totally confusing without the NOT there. Sorry about that. | |||
Bryce Norwood - NowSMS Support Board Administrator Username: Bryce Post Number: 8338 Registered: 10-2002 |
Hi Robert, There is an IPAddressOut= setting that can be used in MMSC.INI, but it would apply to all outbound MM4 connections. We do have an ability to set the source IP for outbound SMPP connections. Theoretically, a similar setting could be added for MM4, but I will have to discuss with our engineering team. -bn Bryce Norwood Now SMS/MMS Support | |||
Robert Barretto New member Username: Barretto Post Number: 22 Registered: 09-2019 |
Hi Bryce, Thanks for getting back! Please do discuss with your team. I hope it is something that can be done easily. Cheers! //Robert | |||
Bryce Norwood - NowSMS Support Board Administrator Username: Bryce Post Number: 8339 Registered: 10-2002 |
Hi Robert, We've added a configuration setting that should do what you want. There is a configuration file for each outbound MMS connection, found in VASPOUT/name/VASP.INI. Under the [VASP] header, we have added support for a SourceIP=a.b.c.d setting. The update with support for this setting can be downloaded at https://www.nowsms.com/download/nowsms20191024.zip -bn Bryce Norwood Now SMS/MMS Support | |||
Robert Barretto New member Username: Barretto Post Number: 23 Registered: 09-2019 |
Hi Bryce, Thanks so much for the quick turn around! Exactly what I was looking for! I will begin setting up my secondary IP and the configuration on our MM4 provider to point to it. Cheers! //Robert | |||
Robert Barretto New member Username: Barretto Post Number: 24 Registered: 09-2019 |
Sorry for the late reply. Finally got a chance to reconfigure and add the secondary VASPOUT routes and the additional IP. Everything is working like a champ. I have two IPs on the Windows box, with two VASP connections using IP1 and two other VASP connections using IP2. I use the MMSRouteCheck hook to select which VASPOUT MM4 connections to use for the outgoing route, the MMSC uses the appropriate source IP for the selected VASPOUT MM4 route. Thanks! |