...

Introduction

The Testmate platform has been designed, to provide tightly integrated and relevant test automation for Cisco Unified Communications. Specific test plans have been built for the following functions:

• Commissioning Testing (new customer)
• Post Migration (new sites)
• Post change (assurance BAU)
• System Accreditation (new CSR)
• Stress Testing
• IP Readiness Assesment (Prattler)

...

Dial plan testing in HCS environments is a complex and time-consuming task, which becomes significantly more complex and time consuming, when new countries and their associated dial plans are added to the HCS solution over time.
The dial plan test plan provides automated testing, that enables a robust and consistent test regime, that ensures a quality user experience, before and after planned updates and changes in the HCS dial plan.
Use Cases

• Testing, to assist with verification of the new dial plan, used by CUCDM 10/VOSS4UC/Kurmi.
• Reduce resources required for testing for the dial plan.
• Minimize potential human errors, by using test automation.

Image Removed

...

The migration capabilities are made of the following components:

• Site Migration

Enables automated testing by deployment engineers during a migration, to automatically test, that the porting has been successful and that media services and basic calling is functioning correctly.

• PSTN Load Test

Enables stress testing with a configurable number of calls between two CTI objects, controlled by Testmate, to ensure sufficient capacity is available, which is not practical to test, using other means.

• Prattler

Providing a mechanism, to test Jabber and media services beyond the network boundary, to support assurance and deployment teams, by testing the required DNS records, certificates and media paths for Jabber.

...

The site migration test plan has been designed for testing and verification of porting and site migration activities. During the setup and execution of this test plan, Testmate takes control of registered devices in the nominated device pool and orchestrates a variety of tests between phones and the JTAPI remote.
This test plan focuses on the test of site specific PSTN and media services and is intended for use by deployment engineers, to be able to quickly perform pre-site commissioning testing in an automated manner.
Use Cases

• Samples DID's from all ranges in device pool(s) under test and verifies, if both in- and outbound calls are correct.
• Basic media service testing (MOH, MTP, CONF, transfer)
• Extension mobility
• Media path verification (packet statistics)
• Re-run test run, following the resolution of issues
• Public work space testing
• Simulated emergency call testing

...

The PSTN load test plan enables load testing and verification of a number of calls, that can be established between two CTI route points. The CTI route points can be located on either two different clusters, connected by either PSTN or private trunks, to determine the maximum number of calls supported on the trunking infrastructure – or for testing Call Admission Control limits between two different locations on the same cluster.
Use Cases

• Verify number of concurrent calls (channels) between two JTAPI remotes (CTI Route Points) – these can either be across the PSTN, internally (CAC testing/AAR) or across private trunks.
• Test SIP Connect Services

Image Removed

...

• Reduce resources, required for troubleshooting Jabber.
• Improve customer satisfaction with soft phones.
• Minimize potential human errors, by using test automation.
• Provide a mechanism for site pre-commissioning testing, for Jabber to ensure, that the environment is configured correctly.

...

• Client-Side Testing (Prattler)

This component provides an application, that can be downloaded by end customers, to perform testing for reactive support. This does not require any infrastructure, to be deployed in the customer network.

• Ad-Hoc Media Probe (Prattler Remote)

Extends the client-side, to enable media testing end to end.

• Problem Report Analytics

Provides a mechanism, to easily provide Jabber problem reports to assurance teams and performs automated log analysis.
Image Removed

...

The PVT test plan is targeted for post change verification testing, that allows for a selection of affected shared services and customer specific systems, to determine, what systems require post change verification testing. This test plan will be modular, which allows adding future extensions, to support additional test cases, as well as backup, health checks and functionality checks of impacted systems.
The first step of the PVT test plan will be, to select customer systems and nominate, what devices to use for testing, then select the test cases required, then select any manual mix-ins, then select the JTAPI remote to use, then start testing.
PVT also has the manual test case, that allows interactive testing with the Testmate users mobile phone or other external destination, to make and receive calls from, as well as verify call statuses.
Use Cases

• Post change verification for operational teams, to standardize the change management process.
• Centralize testing results and metadata.
• Standardize change management pre-change and post-change tasks and verification.

...

The System Acceptance capabilities are made of several modules, that can be added, to extend test coverage. The base and mandatory module is basic calling, that enables control and testing of supplementary services and acts as the primary test integration point for calls to and from other remotes.
Goals and Objectives

• Automate testing activities for testing and accreditation teams.
• Enable automated testing, prior to upgrades in a lab environment, if upgrades are required outside the standard upgrade lifecycle (customer specific bugs).
• Provides the basis of the Orcamate upgrade process, where environments are tested both before and post upgrade.

...

• Dialing discovery, that dynamically works out, what possible ways there are to dial between endpoints (e164 / FNN / Local / onnet / URI / etc).
• Device selection, to ensure, that at least one of each device type is tested for each test case.
• Variable verifications automatically determine the appropriate verification steps for each test case (DTMF / media path / media services / codec).

...

• Internal Calls
• Inter Cluster Calls
• PSTN Calls
• SIP URI Calls

...

• End to end call path verification
• Inbound call testing
• CLIP / CLIR verification
• Call transfer testing
• Call fowarding testing
• DTMF verification
• Call hold and resume testing (MOH)
• Verification of numbers during call states (Called, Connected, Calling and Redirecting)
• Long runnig calls (SIP Refresh)

...

It is possible, to expand the test coverage, using the following remotes, that include other destinations:

• JTAPI Remote

The JTAPI Remote is included with Testmate and utilizes a CTI route point on CUCM as the external party for test calls. This is combined with the Yarnman Terminator service for sending and receiving RTP.

• Video Control Remote

The Video Control Remote enables testing of Cisco TC and CE endpoints for video scenarios, to ensure that video and content streaming functions correctly. This is also required for the video specific test cases.
This remote can be placed in the customers network.

• Polycom Remote

The Polycom Remote enables the incorporation of Polycom VVX phones, registered to TIPT (Broadsoft), for making and receiving calls, using the Polycom webservice API. This will also enable media statistics.
This remote can be placed in the customers network.

• Cloud PSTN Remote

The Cloud PSTN Remote will enable making and receiving calls from a cloud VOIP service (Twilio), to enable testing of various numbers on demand.
This remote would be placed in the model network.

• Mobile Gateway Remote

The Mobile Gateway Remote will enable making and receiving calls, to use the mobile network, multiple SIM cards can be added to the gateway, to enable testing of multiple carrier networks.
This remote would be placed in the model network.
The following diagram provides an overview of how Testmate PVT would be deployed with the various remotes.
Image Removed

...

The remote enables making end to end calls between two separate systems. It can either use CTI RP or dedicated test phone(s), to originate and terminate calls
This enables:

• End to end call path verification
• Inbound call testing
• CLIP/CLIR verification
• DTMF verification
• Verification of numbers during call states (Called, Connected, Calling and Redirecting)

Image Removed

...

Video remote takes control of video endpoints, using the xCommand API via HTTPS, that allows for greater control of video endpoints, which offer functionality, not available via JTAPI.
This enables:

• Making calls and receiving video calls.
• Adjust CUCM configurations, to test different scenarios, such as BW and SIP settings.
• Checking video negotiates and 2 way media.

It will provide a configurable number of endpoints and destinations, that includes DN, FNN, e164 and URI destinations. The following table shows the various video destinations, combined with video specific test cases.
Image Removed
The video control remote requires direct HTTPS connectivity from the Arm to the endpoint.

...

The Polycom VVX uses the phone webservice, to make and receive calls directly from the phone.
Image Removed

...

The cloud PSTN remote enables testing, using any numbers, offered by Twillio or Tropo. These numbers can be added as required.
Image Removed

...

The mobile gateway remote allows for end to end testing of mobile calls; multiple mobile services can be added to the gateway and used for making and receiving calls.
Image Removed

...

The virtual endpoint enables testing registration of SIP services, registering through the service provider NAT to CUCM. This allows for assurance teams, to test customers systems, without requiring the use of customer endpoints. The media path requires the use of an MTP on CUCM, to enable end to end RTP.
Image Removed

...

Testmate Assurance extends the capabilities of Testmate, by enabling scheduling and alerting capabilities for existing test plans.

...

All test plans can be viewed on overview page (click on 'Test Plans' on the left).
Overview shows a few rows (tests), but more rows can be viewed by clicking "Load More Results" or "Load All Results" (directly underneath the overview).
Test plans can be filtered by name, customer (if linked to a certain customer), type, test, last modification user and date. To do so, click on the according arrow next to the field name and select choice from the drop-down bar.
In order to see the test results in excel format, click on "Download Results" underneath the displayed tests. An excel file download will start, which you can then open directly.
Clicking on the Test plans name will bring you directly to that Test plans details.
To create a new Test plan, click on "+ Create Test Plan" in top right corner.
Image Removed

...

Click on "+ Create Test Plan" in top right corner. Following page opens:
Image Removed

• Enter a name for the new test plan.
• Select requested type of test plan "Dialplan" and press 'Submit' underneath the drop-down-menu.
• (Pressing "Cancel" will bring you back to the 'Test Plans Overview'.)
• After clicking 'Submit', the following page opens:

...

• CSS Group
• Number Group
• Geo-Location (optional)

...

• After Connect Failure
• After Connect Success
• JTAPI Connect Command

...

• Pressing "Save" will save all changes made to the Dialplan test plan, that you have made.
• Pressing "Refresh Tests" will update data for this very test, that might have been changed in existing CSS or Number Groups before.
• Pressing "Start" will bring you to the following screen:

...

• First, select a CUCM Instance.
• After that, select the according Device Pool.
• Then select the according Device.
• Select the according Line and pick a date and time for the test (once you have clicked on the 'Schedule Test-Run' field, a calendar will open and after you picked a date, take you to pick a specific time automatically).
• (Pressing 'Cancel' will bring you back to the previous page, where you can select Test Timeout and Test Generation Options.)
• Pressing "Start" will take you to the following screen:

...

• Select "Site Migration" and press 'Submit' underneath the drop-down-menu.
• (Pressing "Cancel" will bring you back to the 'Test Plans Overview'.)
• After clicking 'Submit', the following page opens:

...

• You can also enter, how many devices you want to test (percentage).
• You can then specify (under 'Internal Call Test Cases'), what type of call / action you want to actually test.
• You can also select a Remote Endpoint (External Call Test Cases) or Media Terminator (Test Case Mixins), if required (if you do, you can choose more options for this endpoint).
• You also have several other options to choose from (under Test Case Mixins), if requested.
• Pressing "Save Only" will only save the Site Migration, but not do anything else.
• Pressing "Cancel" will take you back to the Test Plans Overview.
• "Delete Test Plan", marked in red on the right side of the page, will delete the whole Site Migration you created.
• Pressing "Save and Run" will bring you to a review of your Site Migration Test (before you actually run it), that looks as follows:

...

• Enter a name for the new test plan.
• Select requested type of test plan and press 'Submit' underneath the drop-down-menu.
• (Pressing "Cancel" will bring you back to the 'Test Plans Overview'.)

...

• Select the source and target endpoint
• Number of calls
• Codec

Note, that the endpoints (CTI route points) need to be added to Testmate in the CUCM instances configuration.
There are options for:

• Disable DTMF identification
• Continue calls on error
• Timeout for call talking
• Timeout for call identification

Image Removed

...

• Enter a name for the new test plan.
• Select requested type of test plan and press 'Submit' underneath the drop-down-menu.
• (Pressing "Cancel" will bring you back to the 'Test Plans Overview'.)
• After clicking 'Submit', the following page opens:

...

• You can then select your options for Internal Call Test Cases.
• You can also select a Remote Endpoint, if required (if you do, you can choose more options for this endpoint).
• You can also select options for Polycom VVX Phone Test Cases, Mobile Gateway Test Cases, Manual Test Cases and Test Case Mixins.
• You can then select a date and time for the test (once you have clicked on the 'Schedule Test-Run' field, a calendar will open and after you picked a date, take you to pick a specific time automatically).
• "Delete Test Plan", marked in red on the right side of the page, will delete the whole PTSN Load Test Plan, you created.
• (Pressing "Cancel" will bring you back to the 'Test Plans Overview'.)
• Pressing "Save Only" will save the test plan, but not run it. You will already receive an error message here, if you haven't selected enough devices (minimum of 2 devices).

...

• Enter a name for the new test plan.
• Select requested type of test plan and press 'Submit' underneath the drop-down-menu.
• (Pressing "Cancel" will bring you back to the 'Test Plans Overview'.)
• After clicking 'Submit', the following page opens:

Image Removed
Image Removed
You can now select your CUCM Instance and select Included Device Pools (this option will only be selectable, once you have entered a CUCM Instance).

• You can then set options for 'Internal Test Call Cases', 'External Test Call Cases' and 'Test Case Mixins'.
• You can also add a Remote Endpoint. If you do so, several more options will open, which you can then choose.
• "Delete Test Plan", marked in red on the right side of the page, will delete the whole SAT Test Plan, you created.
• (Pressing "Cancel" will bring you back to the 'Test Plans Overview'.)
• Pressing "Save Only" will save the test plan, but not run it.
• Pressing "Save & Run Immediately" will run the according test right away and save the according test plan. It will then take you to the according Test Details (SEE SCREENSHOT BELOW).

• Pressing "Save & Preview" in the SAT Test Plan, will show you a preview of the SAT Test Devices.
• Pressing 'Cancel' in the preview will take you back to the SAT Test Plan.
• Pressing 'Regenerate Devices' in the preview will select new devices from the device pool.
• Pressing "Start Test-Run" will then take you to the according Test Details.

...

• All test run schedules can be viewed on overview page (click on 'Test Run Schedules' on the left).
• Overview now shows all the schedules created.
• Test Run Schedules can be filtered by name, type, total runs and next execution. To do so, click on the according arrow next to the field name and select choice from the drop-down bar.
• In order to see the test run schedules in excel format, click on "Download Results" underneath the displayed schedules. An excel file download will start, which you can then open directly.
• Clicking on the schedules name will bring you directly to that schedule's details.
• To create a new schedule, click on "+ Add Schedule" in top right corner and select the according test
• The following page will open:

...

• You can now give your schedule a name and set a start and end date and time for your schedule.
• You can also enter, how frequently you want your tests to run.
• Under "Configuration", you can select the according test plan, that you are setting the schedule for.
• You can then "Save Changes" in the upper right corner (once saved, a new field "Delete Schedule" will appear on the right, where you can delete the just created schedule).
• On the top right it will now also show the next execution date, that you have just set (where it said 'Not Started / Completed' before).
• You can now also click on "Test Runs" on the upper left, right next to "Schedule":

...

• Here you can see the planned Test Runs.
• In order to see the planned test runs in excel format, click on "Download Results" underneath the displayed test runs. An excel file download will start, which you can then open directly.
• You can also delete the planned test runs, by clicking "Delete Schedule" in the upper right corner.
• Clicking on the Test runs name will bring you directly to that test runs details.

...

Contents

Overview

The Testmate platform has been designed to provide tightly integrated and relevant test automation for Cisco Unified Communications. Specific test plans have been built for the following functions:

• Commissioning Testing (new customer)

• Post Migration (new sites)

• Post change (assurance BAU)

• System Accreditation (new CSR)

• Stress Testing

• IP Readiness Assesment (Prattler)

...

Testplans

Dial Plan

Dial plan testing in HCS environments is a complex and time-consuming task, which becomes significantly more complex and time consuming, when new countries and their associated dial plans are added to the HCS solution over time.
The dial plan test plan provides automated testing, that enables a robust and consistent test regime, that ensures a quality user experience, before and after planned updates and changes in the HCS dial plan.
Use Cases

• Testing, to assist with verification of the new dial plan, used by CUCDM 10/VOSS4UC/Kurmi.

• Reduce resources required for testing for the dial plan.

• Minimize potential human errors, by using test automation.

...

Anchor
_Toc2089485 _Toc2089485

Anchor
_Toc8046517 _Toc8046517

Migration

The migration capabilities are made of the following components:

• Site Migration

Enables automated testing by deployment engineers during a migration, to automatically test, that the porting has been successful and that media services and basic calling is functioning correctly.

• PSTN Load Test

Enables stress testing with a configurable number of calls between two CTI objects, controlled by Testmate, to ensure sufficient capacity is available, which is not practical to test, using other means.

• Prattler

Providing a mechanism, to test Jabber and media services beyond the network boundary, to support assurance and deployment teams, by testing the required DNS records, certificates and media paths for Jabber.

Anchor
_Toc492415616 _Toc492415616

Anchor
_Toc2089486 _Toc2089486

Anchor
_Toc8046518 _Toc8046518

Site Migration Test Plan

The site migration test plan has been designed for testing and verification of porting and site migration activities. During the setup and execution of this test plan, Testmate takes control of registered devices in the nominated device pool and orchestrates a variety of tests between phones and the JTAPI remote.
This test plan focuses on the test of site specific PSTN and media services and is intended for use by deployment engineers, to be able to quickly perform pre-site commissioning testing in an automated manner.
Use Cases

• Samples DID's from all ranges in device pool(s) under test and verifies, if both in- and outbound calls are correct.

• Basic media service testing (MOH, MTP, CONF, transfer)

• Extension mobility

• Media path verification (packet statistics)

• Re-run test run, following the resolution of issues

• Public work space testing

• Simulated emergency call testing

...

Anchor
_Toc492415615 _Toc492415615

Anchor
_Toc2089487 _Toc2089487

Anchor
_Toc8046519 _Toc8046519

PSTN Load Test

The PSTN load test plan enables load testing and verification of a number of calls, that can be established between two CTI route points. The CTI route points can be located on either two different clusters, connected by either PSTN or private trunks, to determine the maximum number of calls supported on the trunking infrastructure – or for testing Call Admission Control limits between two different locations on the same cluster.
Use Cases

• Verify number of concurrent calls (channels) between two JTAPI remotes (CTI Route Points) – these can either be across the PSTN, internally (CAC testing/AAR) or across private trunks.

• Test SIP Connect Services

...

Anchor
_Toc2089488 _Toc2089488

Anchor
_Toc8046520 _Toc8046520

Anchor
_Toc490582096 _Toc490582096

Prattler

Supporting Jabber beyond the network boundary has become a complex and time-consuming task, due to the limited control of the environment. When issues arise, the traditional methods of troubleshooting require a high level of expertise, operational resources and direct involvement by the end user, with issues normally taking several interactions to resolve. This leads to diminished customer satisfaction with the solution.
Providing effective assurance faces the same challenges beyond the network boundary, to determine, if call quality is being affected by network degradation or impairments.

• Reduce resources, required for troubleshooting Jabber.

• Improve customer satisfaction with soft phones.

• Minimize potential human errors, by using test automation.

• Provide a mechanism for site pre-commissioning testing, for Jabber to ensure, that the environment is configured correctly.

The solution is broken down into three separate components:

• Client-Side Testing (Prattler)

This component provides an application, that can be downloaded by end customers, to perform testing for reactive support. This does not require any infrastructure, to be deployed in the customer network.

• Ad-Hoc Media Probe (Prattler Remote)

Extends the client-side, to enable media testing end to end.

• Problem Report Analytics

Provides a mechanism, to easily provide Jabber problem reports to assurance teams and performs automated log analysis.
Image Added

Anchor
_Toc499672196 _Toc499672196

Anchor
_Toc2089489 _Toc2089489

Anchor
_Toc8046521 _Toc8046521

PVT test plan

The PVT test plan is targeted for post change verification testing, that allows for a selection of affected shared services and customer specific systems, to determine, what systems require post change verification testing. This test plan will be modular, which allows adding future extensions, to support additional test cases, as well as backup, health checks and functionality checks of impacted systems.
The first step of the PVT test plan will be, to select customer systems and nominate, what devices to use for testing, then select the test cases required, then select any manual mix-ins, then select the JTAPI remote to use, then start testing.
PVT also has the manual test case, that allows interactive testing with the Testmate users mobile phone or other external destination, to make and receive calls from, as well as verify call statuses.
Use Cases

• Post change verification for operational teams, to standardize the change management process.

• Centralize testing results and metadata.

• Standardize change management pre-change and post-change tasks and verification.

System Acceptance Testing

The System Acceptance capabilities are made of several modules, that can be added, to extend test coverage. The base and mandatory module is basic calling, that enables control and testing of supplementary services and acts as the primary test integration point for calls to and from other remotes.
Goals and Objectives

• Automate testing activities for testing and accreditation teams.

• Enable automated testing, prior to upgrades in a lab environment, if upgrades are required outside the standard upgrade lifecycle (customer specific bugs).

• Provides the basis of the Orcamate upgrade process, where environments are tested both before and post upgrade.

Anchor
_Toc2089491 _Toc2089491

Anchor
_Toc8046523 _Toc8046523

Basic Calling

Testing of phone features for all possible scenarios grows exponentially, as new features are added. Testmate provides a simple interface, to add mix-ins, that add relevant test cases.
These mix-ins include:

• Dialing discovery, that dynamically works out, what possible ways there are to dial between endpoints (e164 / FNN / Local / on-net / URI / etc).

• Device selection, to ensure, that at least one of each device type is tested for each test case.

• Variable verifications automatically determine the appropriate verification steps for each test case (DTMF / media path / media services / codec).

These basis functions can, when combined with targeting remotes on other different CUCM clusters, have test coverage of a large number of scenarios and configurations.

• Internal Calls

• Inter Cluster Calls

• PSTN Calls

• SIP URI Calls

The remote enables making end to end calls between two separate systems. It can either use CTI RP or dedicated test phone(s), to originate and terminate calls.
Use Cases

• End to end call path verification

• Inbound call testing

• CLIP / CLIR verification

• Call transfer testing

• Call forwarding testing (Internal and External)

• DTMF verification

• Call hold and resume testing (MOH)

• Call Park

• Call Pickup

• Verification of numbers during call states (Called, Connected, Calling and Redirecting)

• Long running calls (SIP Refresh)

Anchor
_Toc2089492 _Toc2089492

Anchor
_Toc8046524 _Toc8046524

Remotes

It is possible, to expand the test coverage, using the following remotes, that include other destinations:

• JTAPI Remote

The JTAPI Remote is included with Testmate and utilizes a CTI route point on CUCM as the external party for test calls. This is combined with the Yarnman Terminator service for sending and receiving RTP.

• Video Control Remote

The Video Control Remote enables testing of Cisco TC and CE endpoints for video scenarios, to ensure that video and content streaming functions correctly. This is also required for the video specific test cases.
This remote can be placed in the customers network.

• Polycom Remote

The Polycom Remote enables the incorporation of Polycom VVX phones, registered to TIPT (Broadsoft), for making and receiving calls, using the Polycom webservice API. This will also enable media statistics.
This remote can be placed in the customers network.

• Cloud PSTN Remote

The Cloud PSTN Remote will enable making and receiving calls from a cloud VOIP service (Twilio), to enable testing of various numbers on demand.
This remote would be placed in the model network.

• Mobile Gateway Remote

The Mobile Gateway Remote will enable making and receiving calls, to use the mobile network, multiple SIM cards can be added to the gateway, to enable testing of multiple carrier networks.
This remote would be placed in the model network.
The following diagram provides an overview of how Testmate PVT would be deployed with the various remotes.
Image Added

Anchor
_Toc2089493 _Toc2089493

Anchor
_Toc8046525 _Toc8046525

JTAPI Remote

The remote enables making end to end calls between two separate systems. It can either use CTI RP or dedicated test phone(s), to originate and terminate calls
This enables:

• End to end call path verification

• Inbound call testing

• CLIP/CLIR verification

• DTMF verification

• Verification of numbers during call states (Called, Connected, Calling and Redirecting)

...

Anchor
_Toc493581902 _Toc493581902

Anchor
_Toc499672203 _Toc499672203

Anchor
_Toc2089494 _Toc2089494

Anchor
_Toc8046526 _Toc8046526

Video Control Remote

Video remote takes control of video endpoints, using the xCommand API via HTTPS, that allows for greater control of video endpoints, which offer functionality, not available via JTAPI.
This enables:

• Making calls and receiving video calls.

• Adjust CUCM configurations, to test different scenarios, such as BW and SIP settings.

• Checking video negotiates and 2 way media.

It will provide a configurable number of endpoints and destinations, that includes DN, FNN, e164 and URI destinations. The following table shows the various video destinations, combined with video specific test cases.
Image Added
The video control remote requires direct HTTPS connectivity from the Arm to the endpoint.

Anchor
_Toc499672204 _Toc499672204

Anchor
_Toc2089495 _Toc2089495

Anchor
_Toc8046527 _Toc8046527

Polycom VVX Remote

The Polycom VVX uses the phone webservice, to make and receive calls directly from the phone.
Image Added

Anchor
_Toc2089496 _Toc2089496

Anchor
_Toc8046528 _Toc8046528

Cloud PSTN Remote

The cloud PSTN remote enables testing, using any numbers, offered by Twillio or Tropo. These numbers can be added as required.
Image Added

Anchor
_Toc2089497 _Toc2089497

Anchor
_Toc8046529 _Toc8046529

Mobile Gateway Remote

The mobile gateway remote allows for end to end testing of mobile calls; multiple mobile services can be added to the gateway and used for making and receiving calls.
Image Added

Anchor
_Toc2089498 _Toc2089498

Anchor
_Toc8046530 _Toc8046530

Virtual Endpoint

The virtual endpoint enables testing registration of SIP services, registering through the service provider NAT to CUCM. This allows for assurance teams, to test customers systems, without requiring the use of customer endpoints. The media path requires the use of an MTP on CUCM, to enable end to end RTP.
Image Added