| Ipv6 for MMS not Acking |  Search
|
|
NowSMS Support Forums ⬆ NowSMS Support - MMS & Advanced Issues ⬆ |
◄ ► |
| Author | Message | |||
| Gary Ginter New member Username: Gginterqualcommcom Post Number: 1 Registered: 10-2018 |
 I have enabled ipv6 on the MMSC, configured the ipv6 address on the eth interface, restarted the service, verified routing. selected all available on the ip address tab. I can see the tcp request coming in from the mobile, but I do not see any Ack from the server. Am I missing any steps on the ipv6 config or is there away I can verify the ipv6 is working on the mmsc? not sure what the next step is. | |||
| Des - NowSMS Support Board Administrator Username: Desosms Post Number: 5993 Registered: 08-2008 |
If you’ve just added IPv6 on the Ethernet, it might be a good idea to restart Windows. Then, what does netstat -a -n show about listening on that port? If IP address is set to anything other than “(all available)”, that will block IPv6, but your settings do not show this. — Des NowSMS Support | |||
| Gary Ginter New member Username: Gginterqualcommcom Post Number: 2 Registered: 10-2018 |
I rebooted windows,stop and started the MMSC service under the service tab. attached the netstat output and am seeing the same thing on the wireshark. I see the TCP syn from the mobile and 5 retrasmissions and noting from the mmsc server.  | |||
| Des - NowSMS Support Board Administrator Username: Desosms Post Number: 5994 Registered: 08-2008 |
I am not an expert on ipv6, but what I have noticed is this output from netstat -a -n If listening to port 8800 on ipv4: TCP 0.0.0.0:8800 0.0.0.0:0 LISTENING If listening to port 8800 on ipv6: TCP [::]:8800 [::]:0 LISTENING So you should see both. I may be reading it wrong, but it looks like your config shows MMSC on port 80, but Wireshark looks like connection attempt to 8080? -- Des NowSMS Support | |||
| Gary Ginter New member Username: Gginterqualcommcom Post Number: 3 Registered: 10-2018 |
I was able to modify the mobile to port 80 from the UE and was able to make it past the original issue. Now I am seeing that the m-send-conf packet is sending an unresolved address.  | |||
| Des - NowSMS Support Board Administrator Username: Desosms Post Number: 5996 Registered: 08-2008 |
Hi Gary, Looking at your screen captures, is NowWAP what is listening on port 8080? The MMSC supports ipv6, but NowWAP does not. There has been a shift away from mobile operators using proxies or gateways with HTTP header enrichment performed by the GGSN. The sender address resolution comes from this HTTP header enrichment (e.g., X-MSISDN) I assume you have Radius Accounting feeding NowWAP? Can you get a Wireshark trace of these accounting transactions with IPv6 assignments? We can look at adding ipv6 support to NowWAP...but the trend is moving away from proxies. — Does NowSMS Support | |||
| Gary Ginter New member Username: Gginterqualcommcom Post Number: 4 Registered: 10-2018 |
Yes NowWap is listening on port 8080. When I do a wireshark on the eth interface I do not see any ipv6 radius packets.Our Huawei GGSN only supports ipv4 for Radius accounting. MT is working from our server to the mobile. Not sure what the next step would be. | |||
| Des - NowSMS Support Board Administrator Username: Desosms Post Number: 5998 Registered: 08-2008 |
Clarification ... I expect the Radius accounting packets to be sent over ipv4, but am looking for a packet that is reporting an ipv6 assignment being given to a mobile. Does the GGSN have an option for adding an HTTP header with the MSISDN? — Des NowSMS Support | |||
| Gary Ginter New member Username: Gginterqualcommcom Post Number: 5 Registered: 10-2018 |
When I have the mobile set to ipv6 only I do not see an accounting packet with the ipv6 assignment. When I move to mobile to ipv4 I see the assigned ip. WAP GW ipv4 Accounting-Connect,19/Apr/2019:11:01:23 -0700,NASIP=172.21.114.65,NASPort=0,PhoneNumber=18988452206,SourceIP=172.21.114. 65,AssignedIP=172.21.226.118,3GPP-SGSN-ADDRESS=172.21.114.7,3GPP-IMSI=3100089884 52206 Accounting-Disconnect,19/Apr/2019:11:04:36 -0700,NASIP=172.21.114.65,NASPort=0,PhoneNumber=18988452206,SourceIP=172.21.114. 65,AssignedIP=172.21.226.118,3GPP-SGSN-ADDRESS=172.21.114.7,3GPP-IMSI=3100089884 52206 Accounting-Connect,19/Apr/2019:11:04:42 -0700,NASIP=172.21.114.65,NASPort=0,PhoneNumber=18988452206,SourceIP=172.21.114. 65,AssignedIP=172.21.226.118,3GPP-SGSN-ADDRESS=172.21.114.7,3GPP-IMSI=3100089884 52206 ipv6 Accounting-Connect,19/Apr/2019:10:38:11 -0700,NASIP=172.21.114.65,NASPort=0,PhoneNumber=18988452206,SourceIP=172.21.114. 65,3GPP-SGSN-ADDRESS=172.21.114.7,3GPP-IMSI=310008988452206 Accounting-Disconnect,19/Apr/2019:10:55:01 -0700,NASIP=172.21.114.65,NASPort=0,PhoneNumber=18988452206,SourceIP=172.21.114. 65,3GPP-SGSN-ADDRESS=172.21.114.7,3GPP-IMSI=310008988452206 Accounting-Connect,19/Apr/2019:10:55:57 -0700,NASIP=172.21.114.65,NASPort=0,PhoneNumber=18988452206,SourceIP=172.21.114. 65,3GPP-SGSN-ADDRESS=172.21.114.7,3GPP-IMSI=310008988452206 | |||
| Gary Ginter New member Username: Gginterqualcommcom Post Number: 6 Registered: 10-2018 |
What is the reason from the Accounting stream to have the assigned ip address? What happens if the assigned ip field is empty? we are currently working with out ggsn vendor to see if we can modify our end to add that field. | |||
| Des - NowSMS Support Board Administrator Username: Desosms Post Number: 6000 Registered: 08-2008 |
Can you capture those packets with ipv6 assignments with Wireshark? While we do not have ipv6 support in NowWAP, I want our engineering team to see this to determine if there is a quick way to support it. The MMSC only sees a request as coming from an IP address. It needs another network entity to inform the MSISDN. One way this is done is for NowWAP to monitor these assignments via Radius accounting. — Des NowSMS Support | |||
| Gary Ginter New member Username: Gginterqualcommcom Post Number: 7 Registered: 10-2018 |
Why why do you need add an HTTP header with the MSISDN, is it mandatory for IPv6? Or do you have any alternative solution to avoid HTTP header with the MSISDN.Our current license does not support your request.  | |||
| Des - NowSMS Support Board Administrator Username: Desosms Post Number: 6001 Registered: 08-2008 |
Because the MMS protocol does not define any mechanism for authenticating or identifying a subscriber. The common ways that this is performed is by one of the following: 1) Another network entity (GGSN/SGSN/proxy/gateway) inserts an HTTP header to identify the subscriber. 2) Radius accounting is monitored, which will inform which IP assignments have been issued to which subscriber. Our MMSC supports 1, and also has the option to use the ICAP protocol to request the header from another network entity.. Within our product line, Radius accounting is only supported by NowWAP, and NowWAP only supports IPv4. That is why I am suggesting that the quickest solution is to get the GGSN or SGSN to add the HTTP header. My other queries will not produce a quick solution. The reason I asked to see the Radius accounting packet is because we are evaluating adding Radius accounting support to the MMSC. However, I'm a little confused because instead of Framed-IPv6-Address, your example shows Framed-IPv6-Prefix. I would like to see the raw format of that attribute...I assume it is 00 40 20 02 C0 23 9C 17 67 26? Can you share a raw binary example? -- Des NowSMS Support | |||
| Gary Ginter New member Username: Gginterqualcommcom Post Number: 8 Registered: 10-2018 |
Here you go.  | |||
| Des - NowSMS Support Board Administrator Username: Desosms Post Number: 6002 Registered: 08-2008 |
I've got an engineer investigating and will have a status update later this week. | |||
| Gary Ginter New member Username: Gginterqualcommcom Post Number: 9 Registered: 10-2018 |
Hello, do you have any status on the on the WAP GW issue? | |||
| Des - NowSMS Support Board Administrator Username: Desosms Post Number: 6004 Registered: 08-2008 |
Hi Gary, We've done a preliminary implementation, but are having difficulty testing it, as we do not have live access to a system that is generating Framed-IPv6-Prefix in Radius accounting messages, so we are having to simulate.. Is it feasible to run test versions in your environment? We have an updated NowWAP that tracks this IPV6 address prefix. Then it would be necessary to update configuration settings on the MMSC. On the MMSC, there should currently be an MSISDNHeaderGateways setting which specifies the IP of NowWAP as a trusted gateway (if not, this needs to be added). Add MSISDNICAPServer=ip.addresss:port setting to point the MMSC to the ICAP port on NowWAP...when the MMSC receives a non-proxied IPV6 request from a client directly, it uses ICAP to query NowWAP for the MSISDN. The issue is that it might require a few test updates before we get this right. Is it practical to install test versions in your environment? (They should be stable for existing functionality, it is just a question of getting the new feature working properly.) -- Des NowSMS Support | |||
| Gary Ginter New member Username: Gginterqualcommcom Post Number: 10 Registered: 10-2018 |
Des, Will you or someone from your team be available for realtime support/testing to verify the new feature? I can schedule a upgrade window for a few hours to test in our environment. Our MMSC is actively being utilized and will cause delay in test cases if the service is down outside of a scheduled test window. Thanks, Gary | |||
| Des - NowSMS Support Board Administrator Username: Desosms Post Number: 6007 Registered: 08-2008 |
Hi Gary, Sorry this is taking some time. I don't think real-time assistance is going to be helpful or necessary, just difficult to coordinate, so allow me to explain the procedure I am suggesting. Step 1: Update NowWAP - Plan a short outage (15 minutes) a) Backup the following 4 files from the NowWAP installation: wap3gxs.exe, wap3gxs-wtls.exe, wap3gxs64.exe, wap3gxs64-radius.exe. b) Stop the NowWAP service. c) Replace those 4 files with versions from the update zip file. https://www.nowsms.com/download/wap20190507.zip d) Start the NowWAP service. e) Validate existing IPv4 functionality. There have been no changes to this functionality, so I would not expect any issues. In the unlikely event of a problem, stop service and restore the 4 files that were replaced. Step 2: Preliminary IPv6 test (outage not required) a) Attempt IPv6 connect - transaction will fail, but we are interested in RADIUS logs. Accounting-Connect and Accounting-Disonnect should have AssignedIP= entries for both IPv4 and IPv6 clients. If these do not match what you see in Wireshark, let us know. (It will not be an exact match, Wireshark adds ::/64, but our log just displays the prefix.) Step 3: Enable ICAP interface - Plan a short outage (15 minutes) a) On MSISDN page, enable the ICAP interface and assign a unique port. The MMSC will connect to NowWAP over this port. b) On the MMSC, in MMSC.INI, there should currently be an MSISDNHeaderGateways setting which specifies the IP of NowWAP as a trusted gateway (if this is a wildcard, it needs to be sent to the IP of NowWAP). Add MSISDNICAPServer=ip.addresss:port setting to point the MMSC to the ICAP port on NowWAP...when the MMSC receives a non-proxied IPV6 request from a client directly, it uses ICAP to query NowWAP for the MSISDN. c) Validate existing IPv4 functionality, with clients connecting via proxy/gateway. If this does not work, undo changes to MMSC.INI. Step 4: Test IPv6 client connecting directly to MMSC without proxy (outage not required). If any issues, Wireshark trace of ICAP activity between MMSC and NowWAP would be helpful. Overall, outage requirements should be minimal. The only testing during the outage is to validate existing functionality. And in the event of an issue, rollback to a working configuration. The new functionality (identifying MSISDN of IPv6 client) is where I expect we won't get it right on the first try. This might require further NowWAP or MMSC updates. -- Des NowSMS Support | |||
| Gary Ginter New member Username: Gginterqualcommcom Post Number: 11 Registered: 10-2018 |
Completed step 1 in the process and replaced existing WAP files. Once WAP files were replaced and WAP service was started, ipv4 MMS service was not working. Stop the service replace the old files and started the service and ipv4 is now working. | |||
| Des - NowSMS Support Board Administrator Username: Desosms Post Number: 6008 Registered: 08-2008 |
That is very much a surprise. Can you repeat the attempt, but edit WAPGW.INI to add Debug=Yes under the [WAPGW] header. Collect the WAPDEBUG.LOG/BAK and WRPDEBUG.LOG/BAK. E-mail them to nowsmstech@nowsms.com with Attention: Des in the subject line. -- Des NowSMS Support | |||
| Gary Ginter New member Username: Gginterqualcommcom Post Number: 12 Registered: 10-2018 |
Des, I am not able to schedule an outage until next Tuesday 5/21 7am-9am PDT. Do you want the WAPDEBUG.LOG/BAK and WRPDEBUG.LOG/BAK after I try the process again next week or now from today's attempt? Can you be available next week for support during that time? Thanks, Gary | |||
| Des - NowSMS Support Board Administrator Username: Desosms Post Number: 6009 Registered: 08-2008 |
Gary,, If you have those logs from today’s attempt, please send. I can’t be available during that time window, but my colleague Bryce may be. — Does NowSMS Support | |||
| Gary Ginter New member Username: Gginterqualcommcom Post Number: 13 Registered: 10-2018 |
How do I get a hold of Bryce tomorrow if I have any issues from 07:00am-9:00am PDT? | |||
| Bryce Norwood - NowSMS Support Board Administrator Username: Bryce Post Number: 8330 Registered: 10-2002 |
Hi Gary, In the event you don't make it through step 1, we basically need to figure out what is happening. I'd suggest deleting WAPDEBUG.LOG and WRPDEBUG.LOG after you initially stop the service for the update, so that we can more easily get them after the update. (Side note: Make sure Debug=Yes is set in WAPGW.INI.) Assuming the same IPv4 connection failures occur. Is NowWAP accepting any connections on port 8080? (Look at netstat output like described previously.) Does the task manager show any of these 4 executables running? (I'd expect to see wap3gxs64.exe and wap3gxs64-radius.exe) Try restarting the Windows server to see if this has an impact. The only other thing I can think of is that maybe there is a problem with that previous ZIP file. Use this link for the update instead: https://www.nowsms.com/download/wap20190520.zip I'm sending an email with how to best contact me, and FTP information to upload larger files. -bn Bryce Norwood Now SMS/MMS Support | |||
