Roaming Manager |
 |
|
|
Finally an Easy Way to Monitor Roaming!
- Worried you are losing roamers and never knowing you lost them?
- Need a tool to show you exactly which inbound roamers are chronically failing to register on your network?
- Want an easy way to know when inbound roamers are having problems with their international calls?
- Don’t always have access to the right information when you are troubleshooting?
Special Feature List
- Network wide view of Inbound roamers with drilldown to roamers HLR address
- Network wide view of Outbound roamers with drill down to foreign VLR address
- Network wide view of Authentication requests with drill down to roamers HLR address
- Monitoring of call to international destination (ASR, NER)
- Intelligent alerting based on trends (SMS, E-mail, SNMP)
- Interlinking to alarms, logs and MML
The REWSS Roaming Manager delivers the oversight you crave to shore up your roaming revenue.
Screenshots
Easy to Use - Easy to Implement - Now as a Service
Monitoring roaming doesn’t have to be complicated. The core nodes now provide plenty of information to help with this task. Valuable as probes may be, there are alternatives. We turn statistics, logs, alarms and MML commands from the core nodes into valuable roaming information. Simple, yet powerful when it comes to monitoring and troubleshooting roaming issues.
The uniqueness lies in the ability to drill down to individual affected nodes based on their VLR or HLR address from a network wide view and from there interlink to other relevant information like alarms and MML.
Another important feature is the intelligent based alerting. You don’t have to watch the tool. It will tell you when something is out of the ordinary.
This tool is based around data collected directly from these network elements: MSC / MSS / HLR / SGSN / GGSN. This means easy implementation once a server has been installed and/or a VPN tunnel has been created. Configuring the various nodes to allow REWSS access to the data takes 30 minutes or less. This means you can be up and running with this solution within days.
- Network Wide View
- Automated Alerting
- Drilldown Capabilities
- Historical Trends
REWSS offers 3 ways to get going
- In the Clound
- On-site as a Service
- Enterprise
- Based on nodes and users
- Pay as you go. No long term commitments.
Start up for as low as USD $4,500.00 per month
A Few Functional Examples
Here you'll find a few functional examples of how the REWSS Roaming Manager can be used to monitor and manage roaming on your network.
- Example #1: Send Authentication Information with Drilldown
- Example #2: Total Registered Subscribers with Interlinking
A: Normally the first place you will notice roaming issues are in the MAP messaging. The first MAP message to leave the MSC when a new roamer tries to register is the SAI (Send Authentication Information) message. By counting how many of these messages are sent per roaming partner and how many return can you see if there is any disconnect in the MAP signaling.
A: Yes, this tool is developed specifically for each vendor and each with its unique features. The majority of the vendors are supported.
A: We use different kinds of data but in general statistics is collected every hour and alarms and MML commands are streamed to us or at the latest with a few minutes delay. This depends on the various vendors.
A: Interlinking is a powerful troubleshooting feature. The idea being when you are looking at one type of data and wondering what else happened at that specific time you then have the option to interlink to other data types. This is vendor and operator specific. This feature can be customized per operator to support operator specific databases like trouble ticketing and work order tools.
A: A good portion of international calls are made by roamers calling home or their calls being forwarded back to their network. So keeping an eye on NER (Network Efficiency Rate) and ASR (Answer Seizure Rate) for these destinations are important. A 10% change in the answer seizure rate could mean a carrier in the middle has been changed and the quality is now bad, which in turn could mean the roamer might actively change network just to get a better connection.
A: The fact that it uses information from you nodes and keeps it in a “language” you are used to makes this special. The drilldown and interlinking to other troubleshooting related information is what makes this a powerful tool along with the intelligent trend based alerting. You don’t have to be watching this tool, it will tell you when something is out of the ordinary and when it is you know you have all the information available to you need to take action and get things back on track.
A: Getting this up and running could be done a matter of days, but a requirement from our side is remote access and that traditionally takes a bit. We need data from the core nodes (MSS, HLR, SGSN, GGSN) and to get that normally requires 20 minutes of work per node to get them configured.
A: After the tool is up and running will we provide training. Both on troubleshooting techniques while using the tool but also on the various roaming issues we have come across around the world.
A: No, this is purely based data we get from the various core nodes you have in a wireless network. This is in fact what we believe makes this tool different. Valuable as probes are they can both be expensive and cumbersome to install and maintain. Because we are not probe based and utilize what the vendors provide can we get this up and running quick and provide features that you don’t see in probe based systems.
A: No, but it is a good complement to your probe system.
|
|
 Download PDF (102kb)
|
|
