• No results found

Web-based WS System

From the start of this year, our Web team has designed and a Web – based portal for better accessing and logging Wholesale works. Instead of opening and filling in multiple spreadsheets, it can all be located and done in one site. The portal can be accessed in address 192.168.8.253

For new User, one must create an Account using Create Log-in, and will be prompted for a new username and password. Once finished, you can log in to the portal.

Once in, you may find the above menus; to navigate, simply click one of the items:

Home – will take you to the Asia Telecom Website and company profile page (www.asiatel.com.hk)

10.1 Hourly ASR Alert

This will show all the WS ASR Hourly Alerts Page. In here contain the destinations which need critical monitoring, by setting ASR and ACD threshold with a number of calls. An email alert will be sent to NOC once the stats are below the given threshold in that particular hour. NOC member can check that route if there is a problem and act as necessary.

38 | P a g e

To add up a new alert, click on the New Alert button. User may need to complete the desired parameters.

Status – choose ‘Active’ for new alert. Choose ‘Inactive’ if you want to disable the alert Carrier – input the Carrier name you want to monitor.

Customer ID – input the Customer ID of the Partner. You may find the Customer ID on EBS. 16 Short Name – a drop down menu is displayed with Name of destination or breakout you want to monitor. Short Name is based from the daily ASR report (ex. Malaysia Cellcom mobile is MALAYSIA_CELLMOB short name)

Country ID – a number corresponds to a destination or country breakout. Is based on daily ASR report (MALAYSIA_CELLMOB is country ID 773)

ASR Level %– put in the desired ASR threshold, should be in decimal number (20% ASR = .20).

ASR alert should be realistic, but then should depend on the traffic source. Retail or WS traffic should be considered. WS traffic usually we put lower ASR alert (~ 20%). Premium traffic should have higher ASR provided it is not CC traffic (above 20%). Once we get clear picture of the traffic (we get from the ASR report) we can adjust the parameters accordingly, or upon request of AM.

ACD Level – put in the desired ACD threshold in minutes (ex. 2.50 minutes ACD) should be realistic, but also depend on traffic source. We can adjust accordingly once we study traffic profile.

Call Sample Size – enter the minimum number of call samples, per hour, for ASR and ACD alert computation. Normally we put 100 call samples per hour. If there is little traffic, we can lower to 50 samples per hour.

39 | P a g e

Consec error before alert – put in number of consecutive errors before sending an email alert.

Number may vary depending on traffic profile. Normally we put 3 consecutive errors before sending an email alert.

Description – put in a short description for the alert for reference (New carrier, or Retail traffic etc)

10.2 Blocked Codes List

This menu we keep records of all the codes blocked in SS due to codes unsupported by carrier, codes have higher rate/cost, special services codes, or code mismatches. Rates Team sends us the codes which are to be blocked. Codes can be unblocked also in the future so we keep records on this database to easily keep on track.

To add new blocked Codes click on New Blocked Codes button, than fill in the parameters.

Status – choose either ‘Blocked’ or ‘Unblocked’

Date Blocked – enter the date of effect of the blocked codes.

Carrier - a drop down menu where in to put the carrier affected.

Destination – drop down menu where in to choose the Destination/Country affected.

40 | P a g e

Code – indicate all the codes affected

Action Taken – indicate Blocked or Unblocked on Dial Peers or in Pre-routing translation on SS Reason – indicate the reason the codes are blocked (code mismatched etc.)

10.3 TT Alert

This is where we keep record all the Outgoing trouble tickets to carrier partners. We keep on track the tickets which still not resolved. To create new trouble ticket, click on New TT Alert button, then fill up the following fields:

Status – choose either Open or Close trouble ticket Type – choose either Retail TT or Wholesale TT Date – enter date when ticket is first opened

Destination – enter the destination of breakout which is affected Problem Carrier – indicate the Carrier which is having issues

Carrier Email – indicate the email address of the carrier for sending auto alert Description – put in the body of the message

Action taken – indicate what action was taken (ex, blocked on SS or any particular customer) Remarks – indicate: received time and time replied for retest

41 | P a g e

For the new trouble ticket alerts, follow-up emails are sent after 48 hours of no reply. If Carrier has no reply for two consecutive follow-ups, it will automatically refer to the Account Managers, whether to test once more or drop the route.

For existing trouble tickets with carriers reply for retest, we are only allowed to retest the route two more times at most, from the first time ticket was set. If still failed after two retests, the ticket is referred to the Accounts Manager whether to give one more chance, or to drop the route permanently. Will then closed the trouble ticket as cannot fix.

10.4 WS Swap

In this tab, you can see all the active swap with our customers and vendors. You can refer to this to know which routes or traffic should be monitored on higher priority.

42 | P a g e

11 MVTS-Pro Configurations

Related documents