VoIP.ms Wiki - User contributions [en]

Grandstream UCM6200

2024-01-05T19:05:38Z

B13n:

[[File:Ucm6202.jpg|300px|thumb|left]]

Designed to provide a centralized solution for the communication needs of businesses, the UCM6200 series IP PBX appliance combines enterprise-grade voice, video, data, and mobility features in an easy-to-manage solution. This IP PBX series allows businesses to unify multiple communication technologies, such as voice, video calling, video conferencing, video surveillance, data tools, mobility options, and facility access management onto one common network that can be managed and/or accessed remotely. The secure and reliable UCM6200 series delivers enterprise-grade features without any licensing fees, costs-per-feature or recurring fees.

These boxes typically support a phone system with up to 500 endpoints carrying up to fifty simultaneous calls. There are also a limited number of analogue telephone adapter ports (ranging from two for the UCM6202 to eight for the UCM6208) with provision to use analogue landlines as a fallback. The system is suited for a small to mid-size hotel or commercial office, offering features such as call transfer, conference, forwarding, call recording and toll restriction; there's even an automated wake-up call for hotel clients.

This page covers only basic information to establish a connection between the Grandstream PBX and one or more of the VoIP.ms [[servers]]. It is also necessary to perform many other configuration tasks, such as creating connections from the PBX to each individual extension and [[devices|device]], before this can operate as a usable system. See Grandstream's documentation for more info.

'''Website''': [http://www.grandstream.com/products/ip-pbxs/ucm-series-ip-pbxs/product/ucm6200-series UCM 6200 Series]

<br clear="all" />

== Login into your device ==

#Connect a computer to the same network as the UCM6202
#Ensure the UCM 6202 is properly powered on and displays the IP address on the LCD screen
#Open a web browser on the computer and enter the displayed IP address into the search bar in the following format '''''http(s)://ipaddress:portnumber'''''. The default protocol is HTTPS and the default port number is 8089.
#The Web portal should be shown (see figure below). The default username is "admin". The default password (P/W) is a random string indicated on a sticker on the back of the unit for Grandstream hardware manufactured after 2017; earlier hardware revisions had a default password of "admin".

[[File:UCM main screnn.png|thumb|none|550px|Click to enlarge]]

== Creating a trunk ==
To create a new VoIP.ms trunk head to '''Extension/Trunk>> VoIP trunks''', from the left panel. In this section, you can choose to create a SIP or an IAX trunk.

[[File:UCM-trunk.png|thumb|none|550px|Click to enlarge]]

===SIP Trunk===

To create a SIP trunk you only need to fill some basic information.

* '''''Type''''': Register SIP trunk
* '''''Provider Name''''': VoIP.ms (any name can be used)
* '''''Host Name''''': Type any of our [http://wiki.voip.ms/article/Choosing_Server servers], i.e. toronto5.voip.ms
* '''''Keep trunk CID''''': Enable it, if you want the trunk to send its own CID number or disable it if your extensions are going to send their own CID number
* '''''Username''''': 100000 (replace with your main VoIP.ms account number or sub-account name)
* '''''Password''''': ********* (replace with your main SIP/IAX password or sub-account password)

'''Note:''' Bear in mind to use the same VoIP server your VoIP number is using.
You can check what VoIP server is your VoIP number using, from your VoIP.ms customer portal
at '''DID Numbers>> Manage DIDs''', under '''POP''' column.
You can choose any server you want, as long as the one in your portal and the one in this field matches,
otherwise, incoming calls won't ring.

Click '''Save''' button, do not click '''Apply Changes''' yet.

[[File:New SIP trunk.png|thumb|none|800px|Click to enlarge]]

====Extra SIP settings====

Once your basic SIP trunk has been created we will proceed to improve some settings on it, click on the edit icon for your trunk.

'''SIP Headers'''

To send the SIP '''"FROM"''' header as we require, make:

'''"fromuser:"''' 100000 (replace with your main VoIP.ms account number or sub-account name)

[[File:SIP-basic settings.png|thumb|none|800px|Click to enlarge]]

'''Audio codecs'''

Click at "Advanced Settings" and at "Codec Preference" use only the supported codecs by VoIP.ms: '''G.729''', '''PCMU''' & '''GSM''', in this order.

'''Trunk Caller ID'''

You can use '''PAI (P-Asserted-Identity)''' header if you want to send the CID name & number from your trunk, you only need to use this format:

'''"CallerIDName"<CallerIDNumber>'''

'''Note:''' Enabling the PAI header but leaving the field blank (null) will force the pbx to use the CID priority rules from Grandstream thus enabling you to passthorugh the CID from the extensions

'''Note:''' No Caller ID Number must be set at your VoIP.ms portal or it will override the one sent by your trunk

'''NAT Keep Alive'''

In order to avoid your modem closing your local SIP ports, enable:

'''*Enable Heartbeat Detection:''' Enabled<br>
'''*Heartbeat Frequency:''' 50

[[File:SIP advanced settings.png|thumb|none|550px|Click to enlarge]]

'''Finally''', click '''Save''' button and at this stage, you can also click on '''Apply Changes'''. Your trunk should be shown as '''Registered''' from your VoIP.ms dashboard, however, no calls will work until you set up your outbound and inbound routes.

====Call Encryption TLS/SRTP====
In order to use TLS along with your UCM please follow these steps:

'''1.''' Make sure your Main account or sub-account has '''"Encrypted SIP Traffic"''' enabled.

Bear in mind, if this setting is enabled and your device sends '''UDP/TCP''', '''RTP''' you will be rejected
with error code 488.

Enable this setting for the Main Account at '''Main Menu>> Account settings>> Advanced tab'''.

[[File:Mainacc encryp.png|thumb|none|600px|Click to enlarge]]

For a sub-account enable it at '''Sub accounts>> Manage sub-accounts''' by clicking on the orange icon with a pen and finally click at '''"Advanced Options (Click here to display)"'''.

[[File:Subacc encryp.png|thumb|none|600px|Click to enlarge]]

'''2.''' Now that your account/sub-account has this setting enabled, your device only needs to send '''TLS''' and '''SRTP'''.

Go to '''Extension/Trunk>> VoIP Trunks''' and click on "Edit trunk". In this section make sure you have the following settings:

'''*Host Name:''' toronto5.voip.ms:5061 (Use the same server your phone number is at, you can check it out from your customer portal at Manage DIDs section).

'''*Transport:''' TLS

'''Note:''' When using TLS is very important to specify the number of the server, in case the server's name doesn't have the number "1" included, you need to add it. Adding any of the SIP ports '''5061/5081/42873''' at the end of the '''Hostname''' is also required.

[[File:Ucm trunk tls.png|thumb|none|800px|Click to enlarge]]

Go to '''Advanced Settings''' and set '''SRTP''' to "Enabled and forced"

[[File:Ucm srtp.png|thumb|none|800px|Click to enlarge]]

===IAX2 Trunk===
To create an IAX2 trunk just fill the following information:

* '''''Type''''': Register IAX trunk
* '''''Provider Name''''': VoIP.ms (any name can be used)
* '''''Host Name''''': Type any of our [http://wiki.voip.ms/article/Choosing_Server servers], i.e. toronto5.voip.ms
* '''''Keep trunk CID''''': Enable it, if you want the trunk to send its own CID number or disable it if your extensions are going to send their own CID number
* '''''Caller ID''''': Type the CID number your trunk will be sending.
* '''''Caller ID Name''''': Type the name your trunk will be sending.
* '''''Username''''': 100000 (replace with your main VoIP.ms account number or sub-account name)
* '''''Password''''': ********* (replace with your main SIP/IAX password or sub-account password)

'''Note:''' Bear in mind to use the same VoIP server your VoIP number is using.
You can check what VoIP server is your VoIP number using, from your VoIP.ms customer portal
at '''DID Numbers>> Manage DIDs''', under '''POP''' column.
You can choose any server you want, as long as the one in your portal and the one in this field matches,
otherwise, incoming calls won't ring.

Click '''Save''' button, do not click '''Apply Changes''' yet.

[[File:IAX2 trunk.png|thumb|none|550px|Click to enlarge]]

====Extra IAX settings====
Once your basic IAX trunk has been created we will proceed to improve some settings on it, click on the edit icon for your trunk.

'''Audio codecs'''

Click at "Advanced Settings" and at "Codec Preference" use only the supported codecs by VoIP.ms: '''G.729''', '''PCMU''' & '''GSM''', in this order.

'''NAT Keep Alive'''

In order to avoid your modem closing your local ports, enable:

'''*Enable Heartbeat Detection:''' Enabled<br>
'''*Heartbeat Frequency:''' 50

[[File:IAX advanced settings.png|thumb|none|550px|Click to enlarge]]

'''Finally''', click '''Save''' button and at this stage, you can also click on '''Apply Changes'''. Your trunk should be shown as '''Registered''' from your VoIP.ms dashboard, however, no calls will work until you set up your outbound and inbound routes.

== Creating your outbound route ==
Outbound routes are the ones in charge of making match your dialing pattern and send your call through the proper trunk

'''VoIP.ms suggest to include the following patterns into your outbound route: '''

_1NXXXXXXXXX
_NXXXXXXXXX
_4XXX
_00.
_011.
_033.
_044.

All your different dial patterns must be prefixed by the character "_"

To create your outbound routes click on '''Extension/Trunk>> Outbound routes''', from the left panel and click on "Add"

[[File:Outbound routes general.png|thumb|none|550px|Click to enlarge]]

In this section you only need to fill the following fields:

* '''''Calling Rule Name''''': Any name you want for this route.
* '''''Pattern''''': The desired patter your callers need to dial. You can use the suggested dial pattern by VoIP.ms shown above.
* '''''Trunk''''': Choose your VoIP.ms trunk on where your call will be sent through.
* '''''Privilege Level''''': Choose the desired privilege your extensions must have to be able to use this route. If you use our dial pattern we suggest to set it to "International" since you will be able to place international calls. Bear in mind that an extension with an inferior privilege won't be able to use this route. You can hover over the field's name to gather more information.

[[File:Outbound routes setup.png|thumb|none|800px|Click to enlarge]]

Note: If you want to include a dial-out prefix, you can type it after the "_" character in your dial patterns. This number will need to be stripped off, you can do this by using the "Strip" field, you can choose how many digits you can strip after the "_" character.

<pre>
For example: If you want to use "9" to dial out, then your pattern will need to be _9NXXXXXXXXX
To strip off this number "9" when dialing out, you will need to set the "Strip" field to "1", this way only
one character (in this case number "9") will be stripped off.
</pre>

== Creating your inbound route ==
Thanks to your inbound routes you can use only one single trunk to receive all the incoming calls from all your phone numbers. This way you don't need to use more than one trunk for your phone numbers, inbound routes will receive all of them and route them into the proper destination in your UCM.

'''Note:''' We do not suggest using more than one VoIP.ms trunk on the same device.

From the left panel, head to '''Extension/Trunk>> Inbound Routes''' and click on "Add".

[[File:Inbound routes main.png|thumb|none|550px|Click to enlarge]]

In this section, fill the following fields:

*'''Trunks:''' Choose your VoIP.ms trunk, on where the incoming calls should be sent by us.
*'''Pattern:''' Type your VoIP.ms DID phone number exactly as it is shown under "Manage DIDs" section from your customer portal. This number should be prefixed by the character "_". Please avoid using Wildcards and ensure to use full numbers, otherwise the inbound pattern will have conflicts.
*'''Default Destination:''' Choose the default destination on where your PBX should send your incoming calls to. This could be an internal extension, an IVR, a ring group and so on; managed locally by your PBX.

[[File:Inbound routes setup.png|thumb|none|800px|Click to enlarge]]

'''Note''': Remember to send your phone number in the '''"TO"''' SIP header, this way your PBx will match it with your inbound routes. You can do this very easily by setting '''Device Type''' setting from '''"ATA adapter, IP phone or Softphone"''' to '''"IP PBX Server, Asterisk or Softswitch"'''.

You will find this setting from your VoIP.ms customer portal at '''Main Menu>> Account settings>> Inbound settings''', if you're using the main account or at '''Sub accounts>> Manage Sub accounts''' and by clicking on the orange icon with a pen, if you're using a sub-account

<br clear="all">
;Using the main account:
[[File:PBx setting VoIP panel.png|thumb|left|750px|Click to enlarge]]
[[File:File-PBx setting VoIP panel0.png|thumb|left|750px|Click to enlarge]]

<br clear="all">
;Using a [[Sub Accounts|subaccount]]:
[[File:File-PBx setting VoIP panel1.png|thumb|left|750px|Click to enlarge]]

<br clear="all">

== External links ==
=== Guides and manuals ===
As a PBX, the [https://documentation.grandstream.com/article-categories/ucm6200/ Grandstream UCM6200 series] is a powerful device with a long list of options; the manufacturer's full administrators guide runs more than four hundred pages:
* [https://documentation.grandstream.com/wp-content/uploads/2021/10/ucm6202_quick_installation_guide.pdf Quick installation guide]
* [https://documentation.grandstream.com/wp-content/uploads/2021/11/UCM6xxx_Basic_Configuration_Guide.pdf Basic configuration guide]
* [https://documentation.grandstream.com/wp-content/uploads/2023/04/UCM6200-Series-%E2%80%93-User-Manual.pdf User manual]
* [https://www.grandstream.com/hubfs/Product_Documentation/ucm62xx_usermanual.pdf Full manual]

[[Category:PBXes]]

Acrobits

2023-12-04T16:06:09Z

B13n:

<div><ul>
<li style="display: inline-block;">
[[File:acrobits_logo_horizontal.png|none|600px|link=http://www.counterpath.com/?utm_campaign=itsp-partners&utm_medium=cp-certified-logo&utm_source=voipms]]
</li>

Simplify the way you communicate, whether you’re in the office or on the go. Acrobits Softphone and Groundwire give you the flexibility you need. Available on both the App Store and Google Play.

Visit: https://acrobits.net/sip-client-ios-android/ to download.

==Configuration Details==

* Start the Acrobits App
* Once the Acrobits App has started, click on '''New SIP Account''' to start the configuration.

[[File:Acrobits 1.jpg|thumb|none|200px]]

* You will see VoIP.ms at the list, select it

[[File:Acrobits 2.jpg|thumb|none|200px]]

You will need to fill the information for your account:

*'''Username''': Your Main account or sub account username (six digit number) E.G 123456 / 123456_XX (the underscore has to be used for sub-accounts)
*'''Password''': The password you set for the account / sub account
*'''Domain''': One of VoIP.ms multiple [[Choosing Server#Choosing_a_Server | servers]], you can choose the one closest to your location

Finally click on the '''"Save"''' button and you will be able to start using voip.ms on the Acrobits App.

[[File:Acrobits 3.png|thumb|none|200px]]

In the advanced settings if you would like to setup your '''Display Name''', for your outbound caller ID Name there is some requirements.

- We suggest entering your outbound Caller ID Name must be in '''capital letters'''. This will appears more clearly/visible on some devices.
- You must NOT use any special characters, they will not be displayed.
- Some of regular Canadian providers will not show more than 15 characters. We suggest shrinking or adapt your caller ID.
- Spaces are allowed in a caller id name.

==SMS Related==

In order to use the App for SMS purposes you'll need to make some adjustments for compatibility with how our SMS Through SIP feature works. The steps are the following:

1. Go to "Settings > Accounts > [voip.ms account] > Advanced Settings"
2. Enable "Simple" under "Messaging"
3. Disable "Delivery Notifications" which sends messages as "Message/CPIM". This option only appears after "Simple" is enabled.

==Known Issues==

For Android it's been found that having "Call Integration" can cause audio issues. This can be resolved by heading in the app to:

-Preferences > Call Integration, set as disabled & save.

If you need assistance during the configuration don't hesitate to contact VoIP.ms support.

[[category:guides]]

Call Detail Records

2023-10-06T15:54:55Z

B13n:

{| class="wikitable"
|+
|-
! Article en Français !! Artículo en Español
|-
| [https://wiki.voip.ms/article/D%C3%A9tails_des_appels Français] || [https://wiki.voip.ms/article/Registro_de_Llamadas_(CDR) Español]
|}

The Call Detail Records (CDR) allows you to obtain detailed information of your incoming and outgoing calls. It also contains different filters to sort the call records in order to view the desired information. You can access all the calls from your account without any type of limitation on the original date.

__TOC__

The CDR can be accessed from our Customer Portal at: Finances >> Call Detail Records. You will be presented with the following screen:

[[File:CDR.png|900px]]

== Search Range, Filters & TimeZone ==

The CDR page offers different options to help you sort your records. The first field is the Search Range, followed by the different filters that can help you get the the records of the calls required.

'''The Search Range:''' Under this field you can select a date range up to 92 days at a time to see your Call Detail Records. Please note that you can get records past the 92 days (meaning you can search for calls of any date), but the Search Range itself needs to be 92 or less days.

Under ''Filters and TimeZone'' you will have available the following filters to help you sort your calls:

'''Answered:''' This filter shows or hides calls with ¨Answered¨ status.

'''No Answer:''' This filter shows or hides calls with ¨No Answer¨ status.

'''Busy:''' This filter shows or hides calls with ¨Busy¨ status.

'''Failed:''' This filter shows or hides calls with ¨Failed¨ status.

'''Call Type:''' This filter allows you to choose to show calls with one of the following options:

'''All Calls:''' All Incoming and Outgoing calls will be displayed.
'''Outgoing Calls: All''' Only Outgoing calls of all kind will be displayed.
'''Outgoing Calls: Toll Free''' Only Outgoing calls towards toll free numbers will be displayed.
'''Outgoing Calls: USA''' Only Outgoing calls towards local US numbers will be displayed.
'''Outgoing Calls: CAN''' Only Outgoing calls towards local Canadian numbers will be displayed.
'''Outgoing Calls: USA/Canada''' Only Outgoing calls towards local US and Canadian numbers will be displayed.
'''Outgoing Calls: International''' Only Outgoing calls towards International numbers will be displayed.
'''Incoming Calls: Toll Free''' Only Incoming calls from toll free numbers will be displayed.
'''Incoming Calls: USA''' Only Incoming calls from local US numbers will be displayed.
'''Incoming Calls: CAN''' Only Incoming calls from local Canadian numbers will be displayed.
'''Incoming Calls: CallerID Filtering''' Only incoming calls that have been subject to a CallerID Filtering.
'''Calls to DID:''' Only Inbound calls to DID will be displayed.

'''Call Billing:''' This filter allows you to choose to show calls with one of the following options:

'''All Calls:''' All Free and Billed calls will be displayed.
'''Free Calls:''' Only Free Calls will be displayed.
'''Billed Calls:''' Only Billed calls will be displayed.

'''Account:''' This Filter allows you to choose to show calls with one of the following options:

'''All Accounts:''' Calls from all accounts will be displayed.
'''Main Account:''' Calls from the Main account will be displayed.
'''SubAccounts:''' Calls from Sub Account will be displayed.

'''Time Zone:''' Here you can set the Time Zone to adjust the CDR to your local time.

The entries will be displayed below the filters and in order to assist you to identify your entries. Premium calls will be displayed with a blue asterisk.

'''Gray Arrows:''' The blue arrows on the CDR allow you to sort each field in ascending order.

'''Search:''' With this field, you will be able to search calls per number dialed, number that received the call, description, duration, rate and cost.

== Detail Screen ==

Clicking on the entries will display further details on the call. After clicking on an entry you will be able to see the ''Destination, Description, Caller ID, Account, Disposition, Date, Time, Duration in Seconds, Duration, Rate Type, Rate, Total in US cents, Total in US dollars, and Unique ID''. Please refer to the image below for an example of the details screen:

[[File:CDRDetails.png|500px]]

== CallerID Filtering in CDR ==

When you create a rule using the feature "[[CallerID Filtering]]" and route it to any destination, including those that are routed to '''''"SYSTEM"''''', the arrow [[File:CIDFiltering_Arrow.png]] will appear in the CDR in the description.
<br />
[[File:CDR_CIDFiltering.png|750px|border]]

By clicking on the entry where the [[File:CIDFiltering_Arrow.png]] arrow is, you will be able to see the call details, including the destination it is being routed to. ''(Such as to a specific Ring Group as shown in the example below.)''<br />
[[File:CDR_CIDFiltering-Details.png|750px|border]]

== Block Calls Directly from your Call Detail Record ==

As of 02-07-2023, you can now block undesired incoming calls directly from your call detail records menu. To proceed, simply head into your VoIP.ms portal, CDR and Reports, Call Detail Records and look for the incoming call you wish to block. Press the action button on the right of the entry, confirm you wish to proceed and the number will automatically be blocked as well as the button now turning red to state there is an active block for this number.

[[File:CDRquickBLOCK1.png|border|600px]]

[[File:CDRquickBLOCK2.png|border|600px]]

Lastly, you can also consult callers you are currently blocking under DID Numbers menu, CallerID Filtering.

[[File:CDRquickBLOCK3.png|border|600px]]

[[category:guides]]

Acrobits

2023-10-04T21:42:38Z

B13n:

<div><ul>
<li style="display: inline-block;">
[[File:acrobits_logo_horizontal.png|none|600px|link=http://www.counterpath.com/?utm_campaign=itsp-partners&utm_medium=cp-certified-logo&utm_source=voipms]]
</li>

Simplify the way you communicate, whether you’re in the office or on the go. Acrobits Softphone and Groundwire give you the flexibility you need. Available on both the App Store and Google Play.

Visit: https://acrobits.net/sip-client-ios-android/ to download.

==Configuration Details==

* Start the Acrobits App
* Once the Acrobits App has started, click on '''New SIP Account''' to start the configuration.

[[File:Acrobits 1.jpg|thumb|none|200px]]

* You will see VoIP.ms at the list, select it

[[File:Acrobits 2.jpg|thumb|none|200px]]

You will need to fill the information for your account:

*'''Username''': Your Main account or sub account username (six digit number) E.G 123456 / 123456_XX (the underscore has to be used for sub-accounts)
*'''Password''': The password you set for the account / sub account
*'''Domain''': One of VoIP.ms multiple [[Choosing Server#Choosing_a_Server | servers]], you can choose the one closest to your location

Finally click on the '''"Save"''' button and you will be able to start using voip.ms on the Acrobits App.

[[File:Acrobits 3.png|thumb|none|200px]]

In the advanced settings if you would like to setup your '''Display Name''', for your outbound caller ID Name there is some requirements.

- We suggest entering your outbound Caller ID Name must be in '''capital letters'''. This will appears more clearly/visible on some devices.
- You must NOT use any special characters, they will not be displayed.
- Some of regular Canadian providers will not show more than 15 characters. We suggest shrinking or adapt your caller ID.
- Spaces are allowed in a caller id name.

==SMS Related==

In order to use the App for SMS purposes you'll need to make some adjustments for compatibility with how our SMS Through SIP feature works. The steps are the following:

1. Go to "Settings > Accounts > [voip.ms account] > Advanced Settings"
2. Enable "Simple" under "Messaging"
3. Disable "Delivery Notifications" which sends messages as "Message/CPIM". This option only appears after "Simple" is enabled.

If you need assistance during the configuration don't hesitate to contact VoIP.ms support.

[[category:guides]]

Port Rejection

2022-09-22T14:38:17Z

B13n:

__TOC__

{| class="wikitable"
|+
|-
! Article en Français !! Artículo en Español
|-
| [[Rejet_de_transférabilité | Français]] || [[Rechazo_de_porteo | Español]]
|}

Please note that a port request starts with your paperwork to us, then we submit your request to our CLEC (our CLEC will receive the number when the port is complete). That CLEC then submits the port request to the losing carrier (CLEC). At that point, the ball is in the losing CLEC's court.

We then notify you when our CLEC notifies us of a pending porting date (FOC) or a rejection.

When porting, a number rejection is always a possibility. Rejections are different depending on the situation, they can be for either information missing or information mismatch.

== Where to send my Documentation? ==

There are 3 ways to send your documentation:
: * You can send the missing information and/or documentation by replying to the ticket from your customer portal or your email address and attaching the requested documentation or information.
: * You can send the missing information and/or documentation from our Customer Portal at: -DID Numbers > DID Portability > List of porting numbers > Click on the Blue Upload Cloud button beside the order to add more info/documentation.
: * You can send an email directly at ports@voip.ms with the information and/or documentation requested with the subject containing the number (or one of the numbers) porting.

== Port Rejection ==

As an '''Important Note''' we must say that all rejections for mismatched information always come from the losing carrier. We wish to have every porting number with us as fast as possible, there is no reason why we would reject any order unless some information is missing.

The info that matters is not the info that your provider has listed for you, but rather the info that is listed on record with your provider's CLEC (upstream carrier). Your VoIP provider is probably a reseller and they use a carrier above them (aka CLEC) to provide your number and this is the entity where ports take place.

In case your porting order gets rejected, you must contact the losing carrier. The best way to identify the mismatch and correct it would be to get a CSR (Customer Service Record), which contains the necessary information to complete the request correctly. If the losing carrier is not able to provide the actual copy of the CSR, we will need the information as it is listed on the CSR.

There are many different reasons why a port can get rejected and we can not list them all. However, we will list the most common ones according to our experience:

===Abbreviations===

For ''Canadian numbers'': Abbreviations are Not an exact reason for a rejection e.g. Sending "45 St 1St Av" instead of "45 Street First Avenue" will not clear the rejection since it remains the same address.

For ''US numbers'': The information must match exactly as it is listed on the CSR (Customer Service Records) and not the one on the invoice. In US number cases, the smallest difference will cause a rejection.

===Rejection for SMS Not Answered.===

This rejection occurs when the customer does not answer the SMS that the Losing Carrier sends. All wireless/mobile carriers will send an SMS to approve the port and the customer is obligated to reply to it with approval for the port to occur.

'''As per wireless/mobile carriers rules: The customer has only 90 minutes to reply to the SMS after receiving it.'''

Some carriers mention within the SMS that you do not need to reply to it if you wish to approve, this is a false trail; if the SMS is not replied to, the port will be rejected.

Also, the losing carrier will send the SMS regardless if the phone is off, the number is being used as a landline, you do not have SMS service, etc.

Every time the port is resubmitted, the losing carrier will send a new SMS, this does not depend on our side but the losing carrier and it is also not something that can be avoided/controlled by VoIP.ms

We strongly recommend verifying your options with the losing carrier before submitting your port to avoid rejections. A few carriers will allow customers to pre-approve the port without the SMS, this varies from carrier to carrier.

===Rejection for Mismatch Information (Name, Address, Company Name)===

You might be wondering why was your port rejected if the information matches what it is on your invoice. Please note that most carriers' invoices show the billing address only. In most cases, the billing information is not the same as the Porting information.

For ''Canadian numbers'': Please ask your reseller to contact their CLEC and ask them for the info needed for porting purposes. Please do not accept the same information that was initially submitted since it was already rejected, proving it is not the one the losing CLEC is looking for.

For ''US numbers'': Please ask your reseller to contact the upstream carrier and ask for the CSR copy (Customer Service Records). The CSR is not an invoice and must come from the Upstream carrier, some resellers might provide their own CSR, please note that there is a chance that a Reseller's CSR gets rejected since they usually do not contain the same info as a CSR from their upstream carrier.

A post office box is a guaranteed mismatch as it's not a real address. A landline is installed at a specific physical address, which must match; for inherently nomadic services (such as prepaid mobiles or VoIP), the address may be arbitrary but still needs to look like a valid street address (not a box) with your port request matching your record at the existing provider.

Another common mismatch is the contact person's name on a business account. A carrier will always have a person's name listed in a company as having control of a number even though the bill itself only shows the company name and billing address.

===Disconnected / Inactive Numbers===

This reason simply means that the number you wish to port is disconnected and/or the account status is inactive. Unfortunately disconnected numbers are not portable; therefore, both the number and the account have to be active for the number to be ported. In this case, you will need to reach out to the losing carrier to reactivate the number and/or have the account status set as Active.

===Incorrect Billing Telephone Number (BTN)===

This is probably the most common rejection across the board. The Billing Telephone Number (BTN) is the main telephone number listed on your account. If the BTN you provided us does not match what your phone provider has on file, you will receive this rejection.
To resolve this rejection you will need to contact your current phone provider and ask them what the BTN is for the specified porting number(s). If you are porting more than one number there may be more than one BTN on your account. If this is the case you will need to determine which of the specified porting number(s) falls under which BTN. The least painful way to do this is to request a Customer Service Record (CSR) from your current phone provider.
It is recommended that before submitting your port request to us, you can either request a CSR from your current phone provider or you can call/email them to determine what the BTN(s) is/are.

===Hunt Members / Stranded Services===

If the porting number(s) is/are part of a Hunt Group or if there is any other service/number on the account with the losing carrier, you will receive this rejection. To resolve it, you will need to provide the list of everything on the account and what to do with them (port them, cancel them or keep them active). To avoid this rejection, before starting the porting process, make sure the porting number is left alone (not being attached to any Hunt Group or any other service) or provide the Hunt Group information within the porting notes.

===Account Number, Reseller Mismatch===

The account number provided or the reseller name given on the port, do not match with what the losing CLEC has on record, even though the information appears correct on the bill. Remember that sometimes the information on the losing CLEC's end might be different from the one the losing reseller has. For a successful port, we must always match the CLEC's information.

===Partial Port===

You will receive this rejection if you have remaining services and/or numbers left on your account with your current phone provider. This could be data services or numbers. In this case, you must provide a list of services and/or numbers with the current provider besides the number(s) to port, and if you would like to keep the remaining services active or if you would like them to be disconnected at the time of port.
There are some cases when the losing carrier will advise us that all of your remaining numbers have to port together or be disconnected. If this is the case we will either have to port all of the numbers on your account or you will need to speak with your current phone provider to either disconnect the numbers you do not wish to port.
To avoid this rejection, if you know you will only be porting some of your numbers to us or you have data services attached to your numbers, you can contact your current provider to see if you need to make any account changes before submitting a port request to us

===Freeze on the Account, Pending Order===

You will receive this rejection if there are any open/pending orders on your account with your current provider. This could include feature changes, disconnect orders, or even changes made to other services you may have with your current phone provider. To resolve this rejection you will need to contact your current provider, determine what the open/pending order(s) is/are, and either complete or cancel the order. Once this has been done, you will need to contact us so we can resubmit your port request. Usually, a confirmation number is needed.
To avoid this rejection, make sure there are no open/pending orders on your account before submitting your port request to us; this includes disconnect orders. It would be best to wait to submit a disconnect request until after your numbers have completed porting to us.

===More Recent Authorization===

Sometimes, even when we already have a FOC date, the losing carrier can reject the order, this kind of rejection is called More Recent Authorization. It means that the losing carrier received a more recent authorization than ours to port this number or that the customer contacted the losing carrier and canceled this request or that the losing carrier received a request from another carrier more recently. In this case, you will also need to contact the losing carrier to verify this and then let us know how to proceed.

In every case, our staff will provide as much information as possible to help you understand and clear the rejection.

===Port Out Rejection for PIN===

Please note that numbers that are ported into us, or purchased from our portal, are not assigned any passwords/PINs. This could be a system rejection that the gaining carrier provides before sending the LSR to our underlying carrier.
If this number is being ported to a wireless provider, they may just require the customer to make up a PIN to port the number.

==''IMPORTANT''==

Remember that we have a limited time to reply to our carriers about these rejections. Please have the rejection cleared as soon as possible and reply to us within 7 days of the rejection. Rejections that are not cleared or are replied to after this time might get automatically canceled by our system and you will have to start a new porting order. In some cases, a refund is not applicable since carriers are already paid.

Feel free to contact us if you have any questions about this WikiNote.

[[Category: Guides]]

Port Rejection

2022-09-22T14:37:08Z

B13n:

__TOC__

{| class="wikitable"
|+
|-
! Article en Français !! Artículo en Español
|-
| [[Rejet_de_transférabilité | Français]] || [[Rechazo_de_porteo | Español]]
|}

Please note that a port request starts with your paperwork to us, then we submit your request to our CLEC (our CLEC will receive the number when the port is complete). That CLEC then submits the port request to the losing carrier (CLEC). At that point, the ball is in the losing CLEC's court.

We then notify you when our CLEC notifies us of a pending porting date (FOC) or a rejection.

When porting, a number rejection is always a possibility. Rejections are different depending on the situation, they can be for either information missing or information mismatch.

== Where to send my Documentation? ==

There are 3 ways to send your documentation:
: * You can send the missing information and/or documentation by replying to the ticket from your customer portal or your email address and attaching the requested documentation or information.
: * You can add more details from our Customer Portal at: -DID Numbers > DID Portability > List of porting numbers > Click on the Blue Upload Cloud button beside the order to add more info/documentation.
: * You can send an email directly at ports@voip.ms with the information and/or documentation requested with the subject containing the number (or one of the numbers) porting.

== Port Rejection ==

As an '''Important Note''' we must say that all rejections for mismatched information always come from the losing carrier. We wish to have every porting number with us as fast as possible, there is no reason why we would reject any order unless some information is missing.

The info that matters is not the info that your provider has listed for you, but rather the info that is listed on record with your provider's CLEC (upstream carrier). Your VoIP provider is probably a reseller and they use a carrier above them (aka CLEC) to provide your number and this is the entity where ports take place.

In case your porting order gets rejected, you must contact the losing carrier. The best way to identify the mismatch and correct it would be to get a CSR (Customer Service Record), which contains the necessary information to complete the request correctly. If the losing carrier is not able to provide the actual copy of the CSR, we will need the information as it is listed on the CSR.

There are many different reasons why a port can get rejected and we can not list them all. However, we will list the most common ones according to our experience:

===Abbreviations===

For ''Canadian numbers'': Abbreviations are Not an exact reason for a rejection e.g. Sending "45 St 1St Av" instead of "45 Street First Avenue" will not clear the rejection since it remains the same address.

For ''US numbers'': The information must match exactly as it is listed on the CSR (Customer Service Records) and not the one on the invoice. In US number cases, the smallest difference will cause a rejection.

===Rejection for SMS Not Answered.===

This rejection occurs when the customer does not answer the SMS that the Losing Carrier sends. All wireless/mobile carriers will send an SMS to approve the port and the customer is obligated to reply to it with approval for the port to occur.

'''As per wireless/mobile carriers rules: The customer has only 90 minutes to reply to the SMS after receiving it.'''

Some carriers mention within the SMS that you do not need to reply to it if you wish to approve, this is a false trail; if the SMS is not replied to, the port will be rejected.

Also, the losing carrier will send the SMS regardless if the phone is off, the number is being used as a landline, you do not have SMS service, etc.

Every time the port is resubmitted, the losing carrier will send a new SMS, this does not depend on our side but the losing carrier and it is also not something that can be avoided/controlled by VoIP.ms

We strongly recommend verifying your options with the losing carrier before submitting your port to avoid rejections. A few carriers will allow customers to pre-approve the port without the SMS, this varies from carrier to carrier.

===Rejection for Mismatch Information (Name, Address, Company Name)===

You might be wondering why was your port rejected if the information matches what it is on your invoice. Please note that most carriers' invoices show the billing address only. In most cases, the billing information is not the same as the Porting information.

For ''Canadian numbers'': Please ask your reseller to contact their CLEC and ask them for the info needed for porting purposes. Please do not accept the same information that was initially submitted since it was already rejected, proving it is not the one the losing CLEC is looking for.

For ''US numbers'': Please ask your reseller to contact the upstream carrier and ask for the CSR copy (Customer Service Records). The CSR is not an invoice and must come from the Upstream carrier, some resellers might provide their own CSR, please note that there is a chance that a Reseller's CSR gets rejected since they usually do not contain the same info as a CSR from their upstream carrier.

A post office box is a guaranteed mismatch as it's not a real address. A landline is installed at a specific physical address, which must match; for inherently nomadic services (such as prepaid mobiles or VoIP), the address may be arbitrary but still needs to look like a valid street address (not a box) with your port request matching your record at the existing provider.

Another common mismatch is the contact person's name on a business account. A carrier will always have a person's name listed in a company as having control of a number even though the bill itself only shows the company name and billing address.

===Disconnected / Inactive Numbers===

This reason simply means that the number you wish to port is disconnected and/or the account status is inactive. Unfortunately disconnected numbers are not portable; therefore, both the number and the account have to be active for the number to be ported. In this case, you will need to reach out to the losing carrier to reactivate the number and/or have the account status set as Active.

===Incorrect Billing Telephone Number (BTN)===

This is probably the most common rejection across the board. The Billing Telephone Number (BTN) is the main telephone number listed on your account. If the BTN you provided us does not match what your phone provider has on file, you will receive this rejection.
To resolve this rejection you will need to contact your current phone provider and ask them what the BTN is for the specified porting number(s). If you are porting more than one number there may be more than one BTN on your account. If this is the case you will need to determine which of the specified porting number(s) falls under which BTN. The least painful way to do this is to request a Customer Service Record (CSR) from your current phone provider.
It is recommended that before submitting your port request to us, you can either request a CSR from your current phone provider or you can call/email them to determine what the BTN(s) is/are.

===Hunt Members / Stranded Services===

If the porting number(s) is/are part of a Hunt Group or if there is any other service/number on the account with the losing carrier, you will receive this rejection. To resolve it, you will need to provide the list of everything on the account and what to do with them (port them, cancel them or keep them active). To avoid this rejection, before starting the porting process, make sure the porting number is left alone (not being attached to any Hunt Group or any other service) or provide the Hunt Group information within the porting notes.

===Account Number, Reseller Mismatch===

The account number provided or the reseller name given on the port, do not match with what the losing CLEC has on record, even though the information appears correct on the bill. Remember that sometimes the information on the losing CLEC's end might be different from the one the losing reseller has. For a successful port, we must always match the CLEC's information.

===Partial Port===

You will receive this rejection if you have remaining services and/or numbers left on your account with your current phone provider. This could be data services or numbers. In this case, you must provide a list of services and/or numbers with the current provider besides the number(s) to port, and if you would like to keep the remaining services active or if you would like them to be disconnected at the time of port.
There are some cases when the losing carrier will advise us that all of your remaining numbers have to port together or be disconnected. If this is the case we will either have to port all of the numbers on your account or you will need to speak with your current phone provider to either disconnect the numbers you do not wish to port.
To avoid this rejection, if you know you will only be porting some of your numbers to us or you have data services attached to your numbers, you can contact your current provider to see if you need to make any account changes before submitting a port request to us

===Freeze on the Account, Pending Order===

You will receive this rejection if there are any open/pending orders on your account with your current provider. This could include feature changes, disconnect orders, or even changes made to other services you may have with your current phone provider. To resolve this rejection you will need to contact your current provider, determine what the open/pending order(s) is/are, and either complete or cancel the order. Once this has been done, you will need to contact us so we can resubmit your port request. Usually, a confirmation number is needed.
To avoid this rejection, make sure there are no open/pending orders on your account before submitting your port request to us; this includes disconnect orders. It would be best to wait to submit a disconnect request until after your numbers have completed porting to us.

===More Recent Authorization===

Sometimes, even when we already have a FOC date, the losing carrier can reject the order, this kind of rejection is called More Recent Authorization. It means that the losing carrier received a more recent authorization than ours to port this number or that the customer contacted the losing carrier and canceled this request or that the losing carrier received a request from another carrier more recently. In this case, you will also need to contact the losing carrier to verify this and then let us know how to proceed.

In every case, our staff will provide as much information as possible to help you understand and clear the rejection.

===Port Out Rejection for PIN===

Please note that numbers that are ported into us, or purchased from our portal, are not assigned any passwords/PINs. This could be a system rejection that the gaining carrier provides before sending the LSR to our underlying carrier.
If this number is being ported to a wireless provider, they may just require the customer to make up a PIN to port the number.

==''IMPORTANT''==

Remember that we have a limited time to reply to our carriers about these rejections. Please have the rejection cleared as soon as possible and reply to us within 7 days of the rejection. Rejections that are not cleared or are replied to after this time might get automatically canceled by our system and you will have to start a new porting order. In some cases, a refund is not applicable since carriers are already paid.

Feel free to contact us if you have any questions about this WikiNote.

[[Category: Guides]]

Port Rejection

2022-09-22T14:34:18Z

B13n:

__TOC__

{| class="wikitable"
|+
|-
! Article en Français !! Artículo en Español
|-
| [[Rejet_de_transférabilité | Français]] || [[Rechazo_de_porteo | Español]]
|}

Please note that a port request starts with your paperwork to us, then we submit your request to our CLEC (our CLEC will receive the number when the port is complete). That CLEC then submits the port request to the losing carrier (CLEC). At that point, the ball is in the losing CLEC's court.

We then notify you when our CLEC notifies us of a pending porting date (FOC) or a rejection.

When porting, a number rejection is always a possibility. Rejections are different depending on the situation, they can be for either information missing or information mismatch.

== Where to send my Documentation? ==

There are 3 ways to send your documentation:
: * You can send the missing information and/or documentation by replying to the ticket from your customer portal or your email address and attaching the requested documentation or information.
: * You can add more details from our Customer Portal at: -DID Numbers > DID Portability > List of porting numbers > Click on the blue cloud button beside the order to add more info/documentation.
: * You can send an email directly at ports@voip.ms with the information and/or documentation requested with the subject containing the number (or one of the numbers) porting.

== Port Rejection ==

As an '''Important Note''' we must say that all rejections for mismatched information always come from the losing carrier. We wish to have every porting number with us as fast as possible, there is no reason why we would reject any order unless some information is missing.

The info that matters is not the info that your provider has listed for you, but rather the info that is listed on record with your provider's CLEC (upstream carrier). Your VoIP provider is probably a reseller and they use a carrier above them (aka CLEC) to provide your number and this is the entity where ports take place.

In case your porting order gets rejected, you must contact the losing carrier. The best way to identify the mismatch and correct it would be to get a CSR (Customer Service Record), which contains the necessary information to complete the request correctly. If the losing carrier is not able to provide the actual copy of the CSR, we will need the information as it is listed on the CSR.

There are many different reasons why a port can get rejected and we can not list them all. However, we will list the most common ones according to our experience:

===Abbreviations===

For ''Canadian numbers'': Abbreviations are Not an exact reason for a rejection e.g. Sending "45 St 1St Av" instead of "45 Street First Avenue" will not clear the rejection since it remains the same address.

For ''US numbers'': The information must match exactly as it is listed on the CSR (Customer Service Records) and not the one on the invoice. In US number cases, the smallest difference will cause a rejection.

===Rejection for SMS Not Answered.===

This rejection occurs when the customer does not answer the SMS that the Losing Carrier sends. All wireless/mobile carriers will send an SMS to approve the port and the customer is obligated to reply to it with approval for the port to occur.

'''As per wireless/mobile carriers rules: The customer has only 90 minutes to reply to the SMS after receiving it.'''

Some carriers mention within the SMS that you do not need to reply to it if you wish to approve, this is a false trail; if the SMS is not replied to, the port will be rejected.

Also, the losing carrier will send the SMS regardless if the phone is off, the number is being used as a landline, you do not have SMS service, etc.

Every time the port is resubmitted, the losing carrier will send a new SMS, this does not depend on our side but the losing carrier and it is also not something that can be avoided/controlled by VoIP.ms

We strongly recommend verifying your options with the losing carrier before submitting your port to avoid rejections. A few carriers will allow customers to pre-approve the port without the SMS, this varies from carrier to carrier.

===Rejection for Mismatch Information (Name, Address, Company Name)===

You might be wondering why was your port rejected if the information matches what it is on your invoice. Please note that most carriers' invoices show the billing address only. In most cases, the billing information is not the same as the Porting information.

For ''Canadian numbers'': Please ask your reseller to contact their CLEC and ask them for the info needed for porting purposes. Please do not accept the same information that was initially submitted since it was already rejected, proving it is not the one the losing CLEC is looking for.

For ''US numbers'': Please ask your reseller to contact the upstream carrier and ask for the CSR copy (Customer Service Records). The CSR is not an invoice and must come from the Upstream carrier, some resellers might provide their own CSR, please note that there is a chance that a Reseller's CSR gets rejected since they usually do not contain the same info as a CSR from their upstream carrier.

A post office box is a guaranteed mismatch as it's not a real address. A landline is installed at a specific physical address, which must match; for inherently nomadic services (such as prepaid mobiles or VoIP), the address may be arbitrary but still needs to look like a valid street address (not a box) with your port request matching your record at the existing provider.

Another common mismatch is the contact person's name on a business account. A carrier will always have a person's name listed in a company as having control of a number even though the bill itself only shows the company name and billing address.

===Disconnected / Inactive Numbers===

This reason simply means that the number you wish to port is disconnected and/or the account status is inactive. Unfortunately disconnected numbers are not portable; therefore, both the number and the account have to be active for the number to be ported. In this case, you will need to reach out to the losing carrier to reactivate the number and/or have the account status set as Active.

===Incorrect Billing Telephone Number (BTN)===

This is probably the most common rejection across the board. The Billing Telephone Number (BTN) is the main telephone number listed on your account. If the BTN you provided us does not match what your phone provider has on file, you will receive this rejection.
To resolve this rejection you will need to contact your current phone provider and ask them what the BTN is for the specified porting number(s). If you are porting more than one number there may be more than one BTN on your account. If this is the case you will need to determine which of the specified porting number(s) falls under which BTN. The least painful way to do this is to request a Customer Service Record (CSR) from your current phone provider.
It is recommended that before submitting your port request to us, you can either request a CSR from your current phone provider or you can call/email them to determine what the BTN(s) is/are.

===Hunt Members / Stranded Services===

If the porting number(s) is/are part of a Hunt Group or if there is any other service/number on the account with the losing carrier, you will receive this rejection. To resolve it, you will need to provide the list of everything on the account and what to do with them (port them, cancel them or keep them active). To avoid this rejection, before starting the porting process, make sure the porting number is left alone (not being attached to any Hunt Group or any other service) or provide the Hunt Group information within the porting notes.

===Account Number, Reseller Mismatch===

The account number provided or the reseller name given on the port, do not match with what the losing CLEC has on record, even though the information appears correct on the bill. Remember that sometimes the information on the losing CLEC's end might be different from the one the losing reseller has. For a successful port, we must always match the CLEC's information.

===Partial Port===

You will receive this rejection if you have remaining services and/or numbers left on your account with your current phone provider. This could be data services or numbers. In this case, you must provide a list of services and/or numbers with the current provider besides the number(s) to port, and if you would like to keep the remaining services active or if you would like them to be disconnected at the time of port.
There are some cases when the losing carrier will advise us that all of your remaining numbers have to port together or be disconnected. If this is the case we will either have to port all of the numbers on your account or you will need to speak with your current phone provider to either disconnect the numbers you do not wish to port.
To avoid this rejection, if you know you will only be porting some of your numbers to us or you have data services attached to your numbers, you can contact your current provider to see if you need to make any account changes before submitting a port request to us

===Freeze on the Account, Pending Order===

You will receive this rejection if there are any open/pending orders on your account with your current provider. This could include feature changes, disconnect orders, or even changes made to other services you may have with your current phone provider. To resolve this rejection you will need to contact your current provider, determine what the open/pending order(s) is/are, and either complete or cancel the order. Once this has been done, you will need to contact us so we can resubmit your port request. Usually, a confirmation number is needed.
To avoid this rejection, make sure there are no open/pending orders on your account before submitting your port request to us; this includes disconnect orders. It would be best to wait to submit a disconnect request until after your numbers have completed porting to us.

===More Recent Authorization===

Sometimes, even when we already have a FOC date, the losing carrier can reject the order, this kind of rejection is called More Recent Authorization. It means that the losing carrier received a more recent authorization than ours to port this number or that the customer contacted the losing carrier and canceled this request or that the losing carrier received a request from another carrier more recently. In this case, you will also need to contact the losing carrier to verify this and then let us know how to proceed.

In every case, our staff will provide as much information as possible to help you understand and clear the rejection.

===Port Out Rejection for PIN===

Please note that numbers that are ported into us, or purchased from our portal, are not assigned any passwords/PINs. This could be a system rejection that the gaining carrier provides before sending the LSR to our underlying carrier.
If this number is being ported to a wireless provider, they may just require the customer to make up a PIN to port the number.

==''IMPORTANT''==

Remember that we have a limited time to reply to our carriers about these rejections. Please have the rejection cleared as soon as possible and reply to us within 7 days of the rejection. Rejections that are not cleared or are replied to after this time might get automatically canceled by our system and you will have to start a new porting order. In some cases, a refund is not applicable since carriers are already paid.

Feel free to contact us if you have any questions about this WikiNote.

[[Category: Guides]]

Elegir servidor

2021-06-23T12:58:41Z

B13n:

[[File:ChooseServerImg.png|thumb|none|1280px|VoIP.ms servers]]

{| class="wikitable"
|+
|-
! Article in English !! Article en Français
|-
| [https://wiki.voip.ms/article/Choosing_Server English] ||
[https://wiki.voip.ms/article/Choisir_un_serveur Français]
|}

= Elegir un Servidor =

VoIP.ms le ofrece la posibilidad de conectarse a diferentes servidores, pero ¿cuál es el que debe elegir? Es común pensar que se debe elegir el servidor más cercano a su localidad, sin embargo esto no es necesario en la mayoría de las veces. Si usted está en Estados Unidos, cualquier servidor en EEUU le debe dar un buen resultado en latencia y calidad. También es de utilidad saber que hay una herramienta que le puede ayudar a seleccionar el mejor servidor a usar, este normalmente se llama "ping", el cual le provee la latencia entre usted y el servidor, así usted opcionalmente puede elegir específicamente el servidor que le provea una menor latencia.

'''Nota:''' Tenga en cuenta que es posible que algunos servidores no estén disponibles para que su número DID se utilice como POP (Punto de presencia) en la sección
"Administrar DID". Asegúrese de que su dispositivo SIP / IAX y su número de teléfono apunten al mismo servidor.

=== IPs ===

<div><ul>
<li style="display: inline-block; vertical-align:top;">
'''Canada'''
*Montreal 1, QC ('''montreal.voip.ms''') 192.175.96.73
*Montreal 2, QC ('''montreal2.voip.ms''') 192.175.96.74
*Montreal 3, QC ('''montreal3.voip.ms''') 192.175.96.68
*Montreal 4, QC ('''montreal4.voip.ms''') 67.205.74.179
*Montreal 5, QC ('''montreal5.voip.ms''') 192.175.96.69
*Montreal 6, QC ('''montreal6.voip.ms''') 192.175.96.70
*Montreal 7, QC ('''montreal7.voip.ms''') 192.175.96.71
*Montreal 8, QC ('''montreal8.voip.ms''') 192.175.96.72
*Montreal 9, QC ('''montreal9.voip.ms''') 67.205.74.184
*Montreal 10, QC ('''montreal10.voip.ms''') 67.205.74.187
*Toronto 1, ON ('''toronto.voip.ms''') 158.85.70.148
*Toronto 2, ON ('''toronto2.voip.ms''') 158.85.70.149
*Toronto 3, ON ('''toronto3.voip.ms''') 158.85.70.150
*Toronto 4, ON ('''toronto4.voip.ms''') 158.85.70.151
*Toronto 5, ON ('''toronto5.voip.ms''') 184.75.215.106
*Toronto 6, ON ('''toronto6.voip.ms''') 184.75.215.114
*Toronto 7, ON ('''toronto7.voip.ms''') 184.75.215.146
*Toronto 8, ON ('''toronto8.voip.ms''') 184.75.213.210
*Toronto 9, ON ('''toronto9.voip.ms''') 158.85.70.154
*Toronto 10, ON ('''toronto10.voip.ms''') 158.85.70.158
*Vancouver 1, BC ('''vancouver.voip.ms''') 162.213.157.220
*Vancouver 2, BC ('''vancouver2.voip.ms''') 162.213.157.117
*Vancouver 3, BC ('''vancouver3.voip.ms''') 162.213.157.82
</li>

<li style="display: inline-block; vertical-align:top;">
'''Estados Unidos'''
*Atlanta 1, GA ('''atlanta.voip.ms''') 75.127.65.130
*Atlanta 2, GA ('''atlanta2.voip.ms''') 209.217.224.50
*Chicago 1, IL ('''chicago.voip.ms''') 208.100.39.52
*Chicago 2, IL ('''chicago2.voip.ms''') 208.100.39.53
*Chicago 3, IL ('''chicago3.voip.ms''') 208.100.39.54
*Chicago 4, IL ('''chicago4.voip.ms''') 208.100.39.55
*Chicago 5, IL ('''chicago5.voip.ms''') 50.31.115.149
*Chicago 6, IL ('''chicago6.voip.ms''') 50.31.115.150
*Chicago 7, IL ('''chicago7.voip.ms''') 50.31.115.151
*Dallas, TX ('''dallas.voip.ms''') 158.85.149.162
*Dallas 2, TX ('''dallas2.voip.ms''') 158.85.149.163
*Denver 1, CO ('''denver.voip.ms''') 23.239.211.90
*Denver 2, CO ('''denver2.voip.ms''') 64.27.52.226
*Houston, TX ('''houston.voip.ms''') 205.251.137.130
*Houston 2, TX ('''houston2.voip.ms''') 74.81.95.146
*Los Angeles 1, CA ('''losangeles.voip.ms''') 104.254.128.162
*Los Angeles 2, CA ('''losangeles2.voip.ms''') 104.254.128.2
*Los Angeles 3, CA ('''losangeles3.voip.ms''') 64.188.6.162
*Los Angeles 4, CA ('''losangeles4.voip.ms''') 64.188.6.170
*New York 1, NY ('''newyork.voip.ms''') 72.251.239.196
*New York 2, NY ('''newyork2.voip.ms''') 72.251.239.205
*New York 3, NY ('''newyork3.voip.ms''') 72.251.239.206
*New York 4, NY ('''newyork4.voip.ms''') 72.251.239.207
*New York 5, NY ('''newyork5.voip.ms''') 23.29.136.28
*New York 6, NY ('''newyork6.voip.ms''') 23.29.136.29
*New York 7, NY ('''newyork7.voip.ms''') 23.29.136.38
*New York 8, NY ('''newyork8.voip.ms''') 23.29.136.40
*San Jose, CA ('''sanjose.voip.ms''') 23.246.247.146
*San Jose 2, CA ('''sanjose2.voip.ms''') 23.246.247.147
*Seattle 1, WA ('''seattle.voip.ms''') 50.23.160.53
*Seattle 2, WA ('''seattle2.voip.ms''') 50.23.149.166
*Seattle 3, WA ('''seattle3.voip.ms''') 50.23.160.54
*Tampa, FL ('''tampa.voip.ms''') 162.254.144.173
*Tampa 2, FL ('''tampa2.voip.ms''') 209.133.209.70
*Tampa 3, FL ('''tampa3.voip.ms''') 23.111.187.139
*Tampa 4, FL ('''tampa4.voip.ms''') 23.111.166.202
*Washington 1, DC ('''washington.voip.ms''') 169.62.41.187
*Washington 2, DC ('''washington2.voip.ms''') 169.62.41.189
</li>

<li style="display: inline-block; vertical-align:top;">
'''Internacional'''
*Amsterdam, NL ('''amsterdam.voip.ms''') 66.212.22.42
*London, UK ('''london.voip.ms''') 159.8.157.212
*Paris, FR ('''paris.voip.ms''') 159.8.85.180
</li>
</ul></div>

===Dominios del Servidor===

Para IOS, haga clic aquí [http://wiki.voip.ms/article/Server_Realms Server Realms] para obtener el nombre de dominio para el servidor que planea usar, esto puede diferir del nombre de dominio que se está utilizando.

= ¿Qué es un Ping? =

Ping es la herramienta estándar usada para probar la latencia (demora) en conexiones en red. Normalmente es usada para determinar si un servidor o dispositivo puede ser alcanzado a través de la red y su tiempo de latencia (tiempo que toma en enviarse un paquete a su destino y regresar a su origen) para responder.

La herramienta Ping es parte de Windows, MAC OS y Linux, también se puede encontrar en algunos ruteadores.

== ¿Cómo funciona la herramienta Ping? ==

Esta envía mensajes de petición a un una dirección de red determinada o nombres DNS en ciertos intervalos de tiempo y contabiliza el tiempo que tarda en recibirse un mensaje de respuesta. (mejor conocido como tiempo de latencia)

==¿Cómo hacer un ping en una PC?==

Hacer ping es un comando que le dice si la conexión entre su computadora y un dominio en particular está funcionando correctamente.

En Windows, seleccione Inicio> Programas> Accesorios> Símbolo del sistema. Esto le dará una ventana como la de abajo.

Ingrese la palabra ping, seguida de un espacio, luego el nombre de dominio (montreal.voip.ms) en este caso, el dominio es el nombre de nuestro servidor.

Si los resultados muestran una serie de respuestas, la conexión está funcionando. El tiempo te muestra qué tan rápida es la conexión. Si ves un error de "tiempo de espera agotado" en lugar de una respuesta, hay una falla en algún lugar entre tu computadora y el dominio.

[[File:Ping.gif|thumb|none|600px|Ping]]

== ¿Cómo enviar un ping a una MAC? ==

1- Haga click en el buscador en la barra de herramientas.

2- Haga click en aplicaciones.

3- Haga click en utilidades (usos / configuraciones).

4- Haga doble-click en utilidades de red.*

*En OS X Mavericks (10.9.x), esta aplicación de utilidad cambió de ubicación. En su lugar, inícielo desde Spotlight, presione "comando" + "barra espaciadora" o haga clic en Spotlight directamente (icono de lupa en la parte superior derecha de la pantalla), escriba "utilidad de red" y presione "regresar"

5- En la ventana de utilidades de red, haga click en el el cuadro de ping.

6- En el campo debajo "Ingresese la direccion de red para hacer ping," como montreal.voip.ms

'' Si el ping resulta no ser consistente, puede tener un problema de ''jitter'' (variación del tiempo que tardan en llegar los paquetes debido a una congestión en la red o a diferentes rutas tomadas). Para tratar este problema, puede ajustar el nivel de ''jitter'' en su configuración del dispositivo VoIP (si cuenta con esta opción). Normalmente es recomendado un ping por debajo de 150ms para tener una buena calidad de audio durante la llamada. El tiempo de latencia del servidor es importante, sin embargo hay otros factores importantes a tomar en cuenta para la calidad de las llamadas como son la pérdida de paquetes (las comunicaciones VoIP son muy sensibles a esto) y el nivel de ''jitter'' de su conexión a Internet. ''

El siguiente es el resultado de ejecutar ping con el destino losangeles.voip.ms.

#ping losangeles.voip.ms
Ping to losangeles.voip.ms [67.215.241.250] with 32 bytes de datos:
Response from 67.215.241.250: bytes=32 time=67ms TTL=52
Response from 67.215.241.250: bytes=32 time=69ms TTL=52
Response from 67.215.241.250: bytes=32 time=68ms TTL=52
Response from 67.215.241.250: bytes=32 time=67ms TTL=52
ping statistics from 67.215.241.250:
4 packets transmitted, 4 received, 0% packet lost. rtt min/avg/max/mdev = 67ms, 69ms, 67ms

Ejemplo de salida de ping en Windows:
C:\Windows\system32>ping montreal.voip.ms

Pinging montreal.voip.ms [67.205.74.184] with 32 bytes of data:
Reply from 67.205.74.184: bytes=32 time=85ms TTL=49
Reply from 67.205.74.184: bytes=32 time=86ms TTL=49
Reply from 67.205.74.184: bytes=32 time=86ms TTL=49
Reply from 67.205.74.184: bytes=32 time=85ms TTL=49

Ping statistics for 67.205.74.184:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 85ms, Maximum = 86ms, Average = 85ms

= Scripts de prueba de latencia (enviados por el usuario) =
<p> Todos los siguientes scripts fueron producidos por usuarios de voip.ms que sintieron que otros también podrían beneficiarse del resultado de sus esfuerzos. Se escribieron durante un período de años y probablemente deban ajustarse antes de usarlos, para adaptarse a los cambios en los servidores a lo largo del tiempo y los cambios en las políticas (como no probar servidores muy suscritos que no están abiertos a nuevos registros) </p>
<p> Si no está satisfecho con la seguridad de los scripts o simplemente no le gusta la forma en que aparecen sintácticamente, aún puede hacer ping manualmente a una selección de servidores y elegir un servidor en función de la mejor latencia. Los siguientes scripts son esencialmente envoltorios del comando ping que admiten listas de servidores para enviar a ping y presentar la salida en un formato legible. </p>
<p> Si cree que tiene un script más simple y limpio que funcione para otra plataforma o idioma, agréguelo a este wiki a través de un ticket de soporte.

=== Script de Bash para manejar el formato de salida de ping de Mac ===

Para hacer uso de este script (1) guárdelo como un archivo de texto sin formato (2) establezca los permisos del archivo en ejecutable (3) invoque el script
p.ej. Guarde el script a continuación usando su editor favorito como pingVoipMS.sh (2) chmod u + x pingVoipMS.sh (3) ./pingVoipMS.sh
Este es un script bash 3.x, por lo que también funciona en Linux, simplemente cambie el campo de pérdida de paquetes de ping de 7 a 6 en el ciclo final a continuación (o donde sea que el campo de pérdida esté en su formato de salida de ping). Dependiendo de su distribución, es posible que tenga que cambiar el curl a wget.

</p>
<pre>
#!/bin/bash
# Ping several servers and display Latency, Jitter and Packet Loss
# Usage: [-c <count>][-i <wait time>][-r test restricted servers][<server list file>]
#
# The optional server list text file should be formatted with one host name per line.
# The list of voip.ms servers is available at https://wiki.voip.ms/article/Choosing_Server
# If no args are supplied, this script will scrape a ping server list from voip.ms
#
USER_FILE=""
COUNT=3; INTERVAL=5; RESTRICTED=0
restrictedList=(atlanta.voip.ms chicago.voip.ms
montreal.voip.ms montreal2.voip.ms montreal3.voip.ms montreal4.voip.ms
newyork.voip.ms newyork4.voip.ms seattle.voip.ms
toronto.voip.ms toronto2.voip.ms toronto3.voip.ms toronto4.voip.ms)

# Handle any passed in script arguments
while getopts c:i:r parm
do
case $parm in
c)count_opt=$OPTARG;;
i)interval_opt=$OPTARG;;
r)RESTRICTED=1;;
*)echo -e "Invalid arg\nUsage:\t[ -c <count of ECHO_REQUESTs to Tx, default 3> ] \
\n\t[ -i <wait time (s) between datagrams, default 5> ] \
\n\t[ -r ] Include restricted servers in latency test \
\n\t[FILE <ping server list> ]";exit 1;;
esac
done

# Test if an option was specified and whether it's a +ve non-zero integer
[[ -n $count_opt && ($count_opt =~ ^[[:digit:]]+$) && $count_opt -gt 0 ]] &&
COUNT=$count_opt
[[ -n $interval_opt && ($interval_opt =~ ^[[:digit:]]+$) && $interval_opt -gt 0 ]] &&
INTERVAL=$interval_opt

shift $((OPTIND - 1))

# Validate supplied file (server list)
[[ -n $1 && ! (-f $1 && -r $1) ]] &&
{ echo "\"$1\" file does not exist or is not readable"; exit 1; }
[[ -n $1 && -f $1 && -r $1 ]] && USER_FILE="$1"

if [[ -n $USER_FILE ]]
then
# Bash 3.x in macOS does not support readarray, need to do cumbersome array loops instead
while IFS= read -r servers; do
serverList+=( "$servers" )
done < <(grep -Eo '^\b[[:alpha:]]+?[[:alnum:]]\.voip\.ms\b$' "$USER_FILE" | \
grep -v '^\s*#' | awk NF | sort)
else
# N.B. The script looks for the html boldface tags <b> </b> inside a bracket
# If the website alters and the parse fails, manually create the list and
# supply as a script arg (or perhaps update the parsing to work again :)
while IFS= read -r servers; do
serverList+=( "$servers" )
done < <(curl -sm 10 https://wiki.voip.ms/article/Choosing_Server | \
grep -E '(<b>[[:alpha:]]+?[[:alnum:]]\.voip\.ms</b>)' | \
tr "<>" " " | awk '{print $(NF-3)}' | sort )
fi

# Newer voip.ms clients can't register onto these over-subscribed servers
# Don't test the restricted list unless explicitly asked (with the -r cmd line option)
if [[ $RESTRICTED -eq 0 ]]
then
for server in "${restrictedList[@]}"
do
ix=$(printf "%s\n" "${serverList[@]}" | grep -n "^${server}" | cut -d ":" -f1)
while IFS= read -ra idx; do
keys+=( "${idx[@]}" )
done < <([[ $ix -gt 0 ]] && echo $((ix-1)))
done
for ((i=${#keys[@]} - 1; i >= 0; i--)); do unset "serverList[keys[i]]"; done
fi

if [[ ${#serverList[@]} -eq 0 ]]
then
echo "No unrestricted Voip.ms servers could be found, please supply a server list"
exit 1
fi

runTime=$((COUNT * INTERVAL * ${#serverList[@]}))

echo "PING will send $COUNT packet(s) with a wait of $INTERVAL sec(s) between each packet"
echo "Change the PING options by invoking this script with -c and/or -i, default \"-c 3 -i 5\""
echo "Over $((${#serverList[@]})) server(s) the estimated script Run Time will be $runTime seconds"
echo "================================================================"
printf "%-20s %-18s %7s %8s %6s %s\n" "VoIP Server" "IP Address" "Latency" "Jitter" "Loss" "Countdown"
echo "================================================================ (seconds)"

for myLn in "${serverList[@]}"
do
while IFS=$'\n' read -r pings; do
pingList+=( "$pings" )
printf "%-64s %5d %2d/%-2d\n" "$pings" \
"$((runTime - COUNT * INTERVAL * ${#pingList[@]}))" \
"${#pingList[@]}" "${#serverList[@]}"
done < <( ping -c "$COUNT" -i "$INTERVAL" -q "$myLn" | awk \
'
/^PING / {myH=$2}
/^PING / {
IP = substr($3,2,15)
split(IP,myIP,")") }
/packet loss/ {myPL=$7}
/min\/avg\/max/ {
split($4,myS,"/")
printf("%-20s %-18s %7.3f %8.3f %6s\n",
myH, myIP[1], myS[2], myS[4], myPL ) }
' )
done

echo "================================================================"
echo -e "\nMost appropriate server listed in order of best latency\n"
echo "================================================================"
printf "%-20s %-18s %7s %8s %6s\n" "VoIP Server" "IP Address" "Latency" "Jitter" "Loss"
echo "================================================================"
printf "%s\n" "${pingList[@]}" | LC_ALL=C sort -n -k 3,3 -k 5,5 -k 4,4 | \
awk '{printf("%s $%2d$\n",$0, NR)}'
echo "================================================================"
</pre>

=== Perl Script ===
Lista de ping de servidores voip.ms round robin con archivo csv de salida opcional.

# usage ping_voip.ms.pl <number of times> <seconds in between> <output.csv>
use Net::Ping;
use Time::HiRes;
use strict;

# input list
my @hosts = qw(
atlanta.voip.ms
atlanta2.voip.ms
chicago.voip.ms
chicago2.voip.ms
chicago3.voip.ms
chicago4.voip.ms
dallas.voip.ms
denver.voip.ms
denver2.voip.ms
houston.voip.ms
losangeles.voip.ms
losangeles2.voip.ms
newyork.voip.ms
newyork2.voip.ms
newyork3.voip.ms
newyork4.voip.ms
seattle.voip.ms
seattle2.voip.ms
seattle3.voip.ms
tampa.voip.ms
washington.voip.ms
washington2.voip.ms
montreal.voip.ms
montreal2.voip.ms
montreal3.voip.ms
montreal4.voip.ms
toronto2.voip.ms
toronto3.voip.ms
toronto4.voip.ms
toronto.voip.ms
london.voip.ms
);

$| = 1; #autoflush
# High precision syntax (requires Time::HiRes)
my $p = Net::Ping->new("icmp",1);
$p->hires();
my $max_name_length = (reverse sort { $a <=> $b } map { length($_) } @hosts)[0];
my $count = 4; # number of times to ping
my $interval = 5; # seconds between ping rounds
my $output_file = "";
my @data;

# check for arguments
my $num_args = @ARGV;
if ($num_args >= 1) {$count = $ARGV[0];}
if ($num_args >= 2) {$interval = $ARGV[1];}
if ($num_args >= 3) {$output_file = $ARGV[2];}

# check argument validity
$0 =~ /^.*\\(.*)$/;
my $script = $1;
if ($count !~ /^\d+$/ or $interval !~ /^\d+$/) {die "Usage: $script <number of rounds> <seconds between rounds> <output.csv>\n";}
if (length($output_file) > 0 and $output_file !~ /\.csv$/) {$output_file .= ".csv";}

# main loop
for my $i (1..$count)
{
sleep $interval unless $i == 1;
print "Round $i\n";
my $host_num=0;
foreach my $host (@hosts)
{
(my $ret, my $duration, my $ip) = $p->ping($host);
$ip =~ /(\d+)\.(\d+)\.(\d+)\.(\d+)/;
if ($ret)
{
printf("%*s [ip: %3s.%3s.%3s.%3s] is alive (%6.2f ms)\n", $max_name_length, $host, $1, $2, $3, $4, $duration*1000);
$data[$host_num][$i]=$duration*1000;
}
else
{
printf("%*s [ip: %3s.%3s.%3s.%3s] is dead\n", $max_name_length, $host, $1, $2, $3, $4);
}
$host_num++;
}
print "\n";
}
$p->close();

# if output file name given
if (length($output_file)>0)
{
# print output to file
open FILE, ">$output_file" or die "$!\n";

# print column headers
print FILE "Server\\Round";
for my $i (1..$count)
{
print FILE ", $i";
}
print FILE ", Average\n";

# print data
my $i = 0;
foreach my $host (@hosts)
{
print FILE "$host";
my $sum = 0;
for my $j (1..$count)
{
$sum += $data[$i][$j];
printf FILE ", %8.4f",$data[$i][$j];
}
printf FILE ", %8.4f\n",$sum/$count;
$i++;
}

close FILE;
print "Data written to $output_file\n";
}

# print summary to screen
my $i = 0;
printf("%-*s Average (ms)\n", $max_name_length, "Server");
foreach my $host (@hosts)
{
my $sum = 0;
for my $j (1..$count)
{
$sum += $data[$i][$j];
}
printf("%-*s %8.4f\n", $max_name_length+1, $host, $sum/$count);
$i++;
}

Salidas:
Round 1
atlanta.voip.ms [ip: 174. 34.146.162] is alive ( 88.97 ms)
atlanta2.voip.ms [ip: 72. 9.246.170] is alive ( 92.99 ms)
chicago.voip.ms [ip: 208.100. 39. 52] is alive ( 49.70 ms)
chicago2.voip.ms [ip: 208.100. 39. 53] is alive ( 59.76 ms)
chicago3.voip.ms [ip: 208.100. 39. 54] is alive ( 59.53 ms)
chicago4.voip.ms [ip: 208.100. 39. 55] is alive ( 49.73 ms)
dallas.voip.ms [ip: 74. 54. 54.178] is alive ( 94.99 ms)
denver.voip.ms [ip: 173.248.161. 90] is alive ( 94.05 ms)
denver2.voip.ms [ip: 173.248.159.210] is alive ( 85.13 ms)
houston.voip.ms [ip: 209. 62. 1. 2] is alive (102.87 ms)
losangeles.voip.ms [ip: 96. 44.149.186] is alive ( 64.92 ms)
losangeles2.voip.ms [ip: 96. 44.149.202] is alive ( 63.41 ms)
newyork.voip.ms [ip: 74. 63. 41.218] is alive (131.75 ms)
newyork2.voip.ms [ip: 107. 6. 67.236] is alive (120.64 ms)
newyork3.voip.ms [ip: 107. 6. 67.237] is alive (120.49 ms)
newyork4.voip.ms [ip: 107. 6. 67.238] is alive (111.43 ms)
seattle.voip.ms [ip: 50. 23.160. 50] is alive ( 94.25 ms)
seattle2.voip.ms [ip: 50. 23.160. 51] is alive ( 95.86 ms)
seattle3.voip.ms [ip: 50. 23.160. 52] is alive ( 90.85 ms)
tampa.voip.ms [ip: 68.233.226. 97] is alive (123.29 ms)
washington.voip.ms [ip: 208. 43.234.226] is alive ( 98.71 ms)
washington2.voip.ms [ip: 208. 43.234.227] is alive (101.19 ms)
montreal.voip.ms [ip: 67.205. 74.184] is alive ( 81.82 ms)
montreal2.voip.ms [ip: 67.205. 74.187] is alive ( 86.13 ms)
montreal3.voip.ms [ip: 72. 55.168. 18] is alive ( 77.09 ms)
montreal4.voip.ms [ip: 67.205. 74.179] is alive ( 96.18 ms)
toronto2.voip.ms [ip: 184. 75.215.114] is alive (103.70 ms)
toronto3.voip.ms [ip: 184. 75.215.146] is alive (131.27 ms)
toronto4.voip.ms [ip: 184. 75.213.210] is alive (125.13 ms)
toronto.voip.ms [ip: 184. 75.215.106] is alive (103.26 ms)
london.voip.ms [ip: 5. 77. 36.136] is alive (152.77 ms)

Round 2
atlanta.voip.ms [ip: 174. 34.146.162] is alive ( 88.14 ms)
atlanta2.voip.ms [ip: 72. 9.246.170] is alive ( 92.86 ms)
chicago.voip.ms [ip: 208.100. 39. 52] is alive ( 50.03 ms)
chicago2.voip.ms [ip: 208.100. 39. 53] is alive ( 59.44 ms)
chicago3.voip.ms [ip: 208.100. 39. 54] is alive ( 59.33 ms)
chicago4.voip.ms [ip: 208.100. 39. 55] is alive ( 50.22 ms)
dallas.voip.ms [ip: 74. 54. 54.178] is alive ( 95.58 ms)
denver.voip.ms [ip: 173.248.161. 90] is alive ( 95.94 ms)
denver2.voip.ms [ip: 173.248.159.210] is alive ( 85.29 ms)
houston.voip.ms [ip: 209. 62. 1. 2] is alive (102.73 ms)
losangeles.voip.ms [ip: 96. 44.149.186] is alive ( 65.59 ms)
losangeles2.voip.ms [ip: 96. 44.149.202] is alive ( 64.27 ms)
newyork.voip.ms [ip: 74. 63. 41.218] is alive (112.74 ms)
newyork2.voip.ms [ip: 107. 6. 67.236] is alive (121.22 ms)
newyork3.voip.ms [ip: 107. 6. 67.237] is alive (121.34 ms)
newyork4.voip.ms [ip: 107. 6. 67.238] is alive (110.75 ms)
seattle.voip.ms [ip: 50. 23.160. 50] is alive ( 94.06 ms)
seattle2.voip.ms [ip: 50. 23.160. 51] is alive ( 95.33 ms)
seattle3.voip.ms [ip: 50. 23.160. 52] is alive ( 91.58 ms)
tampa.voip.ms [ip: 68.233.226. 97] is alive (122.94 ms)
washington.voip.ms [ip: 208. 43.234.226] is alive ( 98.28 ms)
washington2.voip.ms [ip: 208. 43.234.227] is alive (101.40 ms)
montreal.voip.ms [ip: 67.205. 74.184] is alive ( 81.91 ms)
montreal2.voip.ms [ip: 67.205. 74.187] is alive ( 85.64 ms)
montreal3.voip.ms [ip: 72. 55.168. 18] is alive ( 75.15 ms)
montreal4.voip.ms [ip: 67.205. 74.179] is alive ( 96.79 ms)
toronto2.voip.ms [ip: 184. 75.215.114] is alive (103.10 ms)
toronto3.voip.ms [ip: 184. 75.215.146] is alive (150.85 ms)
toronto4.voip.ms [ip: 184. 75.213.210] is alive (138.40 ms)
toronto.voip.ms [ip: 184. 75.215.106] is alive (103.45 ms)
london.voip.ms [ip: 5. 77. 36.136] is alive (170.79 ms)

Round 3
atlanta.voip.ms [ip: 174. 34.146.162] is alive ( 88.76 ms)
atlanta2.voip.ms [ip: 72. 9.246.170] is alive ( 92.86 ms)
chicago.voip.ms [ip: 208.100. 39. 52] is alive ( 49.65 ms)
chicago2.voip.ms [ip: 208.100. 39. 53] is alive ( 60.01 ms)
chicago3.voip.ms [ip: 208.100. 39. 54] is alive ( 59.05 ms)
chicago4.voip.ms [ip: 208.100. 39. 55] is alive ( 49.53 ms)
dallas.voip.ms [ip: 74. 54. 54.178] is alive ( 95.82 ms)
denver.voip.ms [ip: 173.248.161. 90] is alive ( 95.02 ms)
denver2.voip.ms [ip: 173.248.159.210] is alive ( 85.60 ms)
houston.voip.ms [ip: 209. 62. 1. 2] is alive (103.35 ms)
losangeles.voip.ms [ip: 96. 44.149.186] is alive ( 65.79 ms)
losangeles2.voip.ms [ip: 96. 44.149.202] is alive ( 64.05 ms)
newyork.voip.ms [ip: 74. 63. 41.218] is alive (113.01 ms)
newyork2.voip.ms [ip: 107. 6. 67.236] is alive (121.41 ms)
newyork3.voip.ms [ip: 107. 6. 67.237] is alive (122.23 ms)
newyork4.voip.ms [ip: 107. 6. 67.238] is alive (110.62 ms)
seattle.voip.ms [ip: 50. 23.160. 50] is alive ( 93.65 ms)
seattle2.voip.ms [ip: 50. 23.160. 51] is alive ( 95.19 ms)
seattle3.voip.ms [ip: 50. 23.160. 52] is alive ( 90.75 ms)
tampa.voip.ms [ip: 68.233.226. 97] is alive (125.12 ms)
washington.voip.ms [ip: 208. 43.234.226] is alive ( 98.19 ms)
washington2.voip.ms [ip: 208. 43.234.227] is alive (101.98 ms)
montreal.voip.ms [ip: 67.205. 74.184] is alive ( 80.16 ms)
montreal2.voip.ms [ip: 67.205. 74.187] is alive ( 87.16 ms)
montreal3.voip.ms [ip: 72. 55.168. 18] is alive ( 76.54 ms)
montreal4.voip.ms [ip: 67.205. 74.179] is alive ( 97.51 ms)
toronto2.voip.ms [ip: 184. 75.215.114] is alive (104.18 ms)
toronto3.voip.ms [ip: 184. 75.215.146] is alive (142.81 ms)
toronto4.voip.ms [ip: 184. 75.213.210] is alive (138.95 ms)
toronto.voip.ms [ip: 184. 75.215.106] is alive (103.78 ms)
london.voip.ms [ip: 5. 77. 36.136] is alive (153.14 ms)

Round 4
atlanta.voip.ms [ip: 174. 34.146.162] is alive ( 89.19 ms)
atlanta2.voip.ms [ip: 72. 9.246.170] is alive ( 92.98 ms)
chicago.voip.ms [ip: 208.100. 39. 52] is alive ( 49.21 ms)
chicago2.voip.ms [ip: 208.100. 39. 53] is alive ( 60.50 ms)
chicago3.voip.ms [ip: 208.100. 39. 54] is alive ( 59.68 ms)
chicago4.voip.ms [ip: 208.100. 39. 55] is alive ( 50.18 ms)
dallas.voip.ms [ip: 74. 54. 54.178] is alive ( 93.93 ms)
denver.voip.ms [ip: 173.248.161. 90] is alive ( 94.22 ms)
denver2.voip.ms [ip: 173.248.159.210] is alive ( 85.10 ms)
houston.voip.ms [ip: 209. 62. 1. 2] is alive (103.67 ms)
losangeles.voip.ms [ip: 96. 44.149.186] is alive ( 65.58 ms)
losangeles2.voip.ms [ip: 96. 44.149.202] is alive ( 63.60 ms)
newyork.voip.ms [ip: 74. 63. 41.218] is alive (114.76 ms)
newyork2.voip.ms [ip: 107. 6. 67.236] is alive (120.44 ms)
newyork3.voip.ms [ip: 107. 6. 67.237] is alive (121.05 ms)
newyork4.voip.ms [ip: 107. 6. 67.238] is alive (110.51 ms)
seattle.voip.ms [ip: 50. 23.160. 50] is alive ( 94.04 ms)
seattle2.voip.ms [ip: 50. 23.160. 51] is alive ( 96.92 ms)
seattle3.voip.ms [ip: 50. 23.160. 52] is alive ( 91.23 ms)
tampa.voip.ms [ip: 68.233.226. 97] is alive (123.28 ms)
washington.voip.ms [ip: 208. 43.234.226] is alive ( 98.45 ms)
washington2.voip.ms [ip: 208. 43.234.227] is alive (100.94 ms)
montreal.voip.ms [ip: 67.205. 74.184] is alive ( 82.33 ms)
montreal2.voip.ms [ip: 67.205. 74.187] is alive ( 85.02 ms)
montreal3.voip.ms [ip: 72. 55.168. 18] is alive ( 76.85 ms)
montreal4.voip.ms [ip: 67.205. 74.179] is alive ( 96.32 ms)
toronto2.voip.ms [ip: 184. 75.215.114] is alive (104.22 ms)
toronto3.voip.ms [ip: 184. 75.215.146] is alive (148.33 ms)
toronto4.voip.ms [ip: 184. 75.213.210] is alive (141.61 ms)
toronto.voip.ms [ip: 184. 75.215.106] is alive (105.91 ms)
london.voip.ms [ip: 5. 77. 36.136] is alive (152.85 ms)

Server Average (ms)
atlanta.voip.ms 88.7630
atlanta2.voip.ms 92.9233
chicago.voip.ms 49.6477
chicago2.voip.ms 59.9305
chicago3.voip.ms 59.3972
chicago4.voip.ms 49.9152
dallas.voip.ms 95.0790
denver.voip.ms 94.8077
denver2.voip.ms 85.2797
houston.voip.ms 103.1562
losangeles.voip.ms 65.4693
losangeles2.voip.ms 63.8347
newyork.voip.ms 118.0643
newyork2.voip.ms 120.9265
newyork3.voip.ms 121.2778
newyork4.voip.ms 110.8275
seattle.voip.ms 93.9993
seattle2.voip.ms 95.8267
seattle3.voip.ms 91.1035
tampa.voip.ms 123.6570
washington.voip.ms 98.4065
washington2.voip.ms 101.3774
montreal.voip.ms 81.5525
montreal2.voip.ms 85.9863
montreal3.voip.ms 76.4058
montreal4.voip.ms 96.7013
toronto2.voip.ms 103.7986
toronto3.voip.ms 143.3156
toronto4.voip.ms 136.0254
toronto.voip.ms 104.1012
london.voip.ms 157.3885

=== Powershell ===

Diciembre 2017 - Un problema en el codigo del dominio washington2.voip.ms lo mostraba como el mejor servidor, esto fue corregido.
<pre>
# Usage: Copy and paste the following code into a powershell window
# To run it from a command prompt, save this file with extension ps1.
# Then run Powershell.exe -file "pathtothisscript.ps1"
Clear-Variable best* -Scope Global #Clear the best* variables in case you run it more than once...
#Get the list of servers into an array
$Servers =
@("amsterdam.voip.ms","atlanta.voip.ms","atlanta2.voip.ms","chicago.voip.ms","chicago2.voip.ms","chicago3.voip.ms",
"chicago4.voip.ms","dallas.voip.ms","dallas2.voip.ms","denver.voip.ms","denver2.voip.ms","houston.voip.ms",
"houston2.voip.ms","london.voip.ms","losangeles.voip.ms","losangeles2.voip.ms","montreal.voip.ms",
"montreal2.voip.ms","montreal3.voip.ms","montreal4.voip.ms","montreal5.voip.ms","montreal6.voip.ms","montreal7.voip.ms",
"montreal8.voip.ms","newyork.voip.ms","newyork2.voip.ms","newyork3.voip.ms","newyork4.voip.ms","newyork5.voip.ms",
"newyork6.voip.ms","newyork7.voip.ms","newyork8.voip.ms","paris.voip.ms","sanjose.voip.ms","sanjose2.voip.ms",
"seattle.voip.ms","seattle2.voip.ms","seattle3.voip.ms","tampa.voip.ms","tampa2.voip.ms","toronto.voip.ms",
"toronto2.voip.ms","toronto3.voip.ms","toronto4.voip.ms","toronto5.voip.ms","toronto6.voip.ms","toronto7.voip.ms",
"toronto8.voip.ms","vancouver.voip.ms","vancouver2.voip.ms","washington.voip.ms","washington2.voip.ms")
$k = 0 #Counting variable so we know what server number we are testing
#num of servers to test
$servercount = $servers.length
#Do the following code for each server in our array
ForEach($server in $servers)
{
#Add one to the counting variable....we are on server #1...then server 2, then server 3 etc...
$k++
#Update the progress bar
Write-Progress -Activity "Testing Server: ${server}" -status "Testing Server $k out of $servercount" -percentComplete ($k / $servercount*100)
#Counting variable for number of times we tried to ping a given server
$i = 0
Do{
#assume a failure
$pingsuccess = $false
$i++ #Add one to the counting variable.....1st try....2nd try....3rd try etc...
Try{
#Try to ping
$currentping = (test-connection $server -count 1 -ErrorAction Stop).responsetime
#If success full, set success variable
$pingsuccess = $true
}
#Catch the failure and set the success variable to false
Catch {
$pingsuccess = $false
}
}
#Try everything between Do and While up to 5 times, or while $pingsuccess is not true
While($pingsuccess -eq $false -and $i -le 5)
#Compare the last ping test with the best known ping test....if there is no known best ping test, assume this one is the best $bestping = $currentping
If($pingsuccess -and ($currentping -lt $bestping -or (!($bestping)))){
#If this is the best ping...save it
$bestserver = $server #Save the best server
$bestping = $currentping #Save the best ping results
}
write-host "tested: $server at $currentping ms after $i attempts" #write the results of the test for this server
}
write-host "`r`n The server with the best ping is: $bestserver at $bestping ms`r`n" #write the end result
Pause
</pre>

=== Linux Shell Script ===
Hace ping a varios servidores voip.ms

#!/bin/sh
# Ping several servers and display Latency, Jitter and Packet Loss
#
# First, create a text file with all servers you want to ping - one host name per line.
# The list of voip.ms servers is available at http://wiki.voip.ms/article/Choosing_Server
myHF="voip_ping_hosts.txt"
# Sample file:
# toronto.voip.ms
# montreal.voip.ms
# seattle.voip.ms
# chicago.voip.ms
# newyork.voip.ms
#
echo "============================================"
printf "%-20s %7s %8s %6s\n" "VoIP Server" "Latency" "Jitter" "Loss"
echo "============================================"
cat ${myHF} |\
while read myLn
do
ping -c 3 -i 5 -q $myLn |\
awk '/^PING / {myH=$2}
/packet loss/ {myPL=$6}
/min\/avg\/max/ {
split($4,myS,"/")
printf( "%-20s %3.1f %1.3f %4s\n", myH, myS[2], myS[4], myPL)
}'
done
echo "============================================"

Salidas:

============================================
VoIP Server Latency Jitter Loss
============================================
toronto.voip.ms 68.3 0.439 0%
montreal.voip.ms 89.6 0.197 0%
seattle.voip.ms 71.2 0.387 0%
chicago.voip.ms 71.6 0.084 0%
newyork.voip.ms 79.1 0.411 0%
============================================

= La Latencia y su importancia =

La latencia es muy importante para Voip, esto determinará el tiempo que tardará la transmisión del paquete de datos en llegar al destino. Una latencia alta provocará un retraso y ecos en la comunicación.

La latencia se mide en milisegundos (ms) Por ejemplo: una latencia de 150 ms es apenas perceptible, por lo que es aceptable. Más alto que eso, la calidad comienza a sufrir. Cuando supera los 300 ms, se vuelve inaceptable.

[[category:Guías]]

Choisir un serveur

2021-06-23T12:58:10Z

B13n:

[[File:ChooseServerImg.png|thumb|none|1280px|VoIP.ms servers]]

{| class="wikitable"
|+
|-
! Article in English !! Artículo en Español
|-
| [https://wiki.voip.ms/article/Choosing_Server English] || [https://wiki.voip.ms/article/Elegir_servidor Español]
|}

= Choisir un serveur =

[http://www.voip.ms VoIP.ms] propose de nombreux serveurs PoP différents, mais lequel choisir? Une des conceptions erronées est que vous devriez choisir le serveur PoP le plus proche de votre emplacement, mais cela n'est pas nécessaire la plupart du temps.

Par exemple, si vous êtes aux États-Unis, l'un des serveurs américains fournira une très bonne latence et une très bonne qualité de service. Le serveur le plus récent d'une ville est indiqué par le numéro le plus élevé associé au nom du serveur, car ils sont classés par ordre croissant.

Il convient également de noter qu'il existe un outil réseau qui vous aidera à choisir le serveur que vous souhaitez utiliser, généralement appelé "ping", qui vous fournira la latence entre vous et le serveur. Par conséquent, le serveur qui vous offre le moins de latence doit être utilisé.

'''Note:''' Veuillez garder à l'esprit que certains serveurs peuvent ne pas être disponibles pour que votre numéro DID soit utilisé comme POP (point de présence) dans la section
'''Gestion des DID'''. Assurez-vous aussi que votre appareil SIP/IAX et votre numéro DID pointent vers le même serveur POP.

=== Adresses IPs ===

<div><ul>
<li style="display: inline-block; vertical-align:top;">
'''Canada'''
*Montreal 1, QC ('''montreal.voip.ms''') 192.175.96.73
*Montreal 2, QC ('''montreal2.voip.ms''') 192.175.96.74
*Montreal 3, QC ('''montreal3.voip.ms''') 192.175.96.68
*Montreal 4, QC ('''montreal4.voip.ms''') 67.205.74.179
*Montreal 5, QC ('''montreal5.voip.ms''') 192.175.96.69
*Montreal 6, QC ('''montreal6.voip.ms''') 192.175.96.70
*Montreal 7, QC ('''montreal7.voip.ms''') 192.175.96.71
*Montreal 8, QC ('''montreal8.voip.ms''') 192.175.96.72
*Montreal 9, QC ('''montreal9.voip.ms''') 67.205.74.184
*Montreal 10, QC ('''montreal10.voip.ms''') 67.205.74.187
*Toronto 1, ON ('''toronto.voip.ms''') 158.85.70.148
*Toronto 2, ON ('''toronto2.voip.ms''') 158.85.70.149
*Toronto 3, ON ('''toronto3.voip.ms''') 158.85.70.150
*Toronto 4, ON ('''toronto4.voip.ms''') 158.85.70.151
*Toronto 5, ON ('''toronto5.voip.ms''') 184.75.215.106
*Toronto 6, ON ('''toronto6.voip.ms''') 184.75.215.114
*Toronto 7, ON ('''toronto7.voip.ms''') 184.75.215.146
*Toronto 8, ON ('''toronto8.voip.ms''') 184.75.213.210
*Toronto 9, ON ('''toronto9.voip.ms''') 158.85.70.154
*Toronto 10, ON ('''toronto10.voip.ms''') 158.85.70.158
*Vancouver 1, BC ('''vancouver.voip.ms''') 162.213.157.220
*Vancouver 2, BC ('''vancouver2.voip.ms''') 162.213.157.117
*Vancouver 3, BC ('''vancouver3.voip.ms''') 162.213.157.82
</li>

<li style="display: inline-block; vertical-align:top;">
'''États-Unis'''
*Atlanta 1, GA ('''atlanta.voip.ms''') 75.127.65.130
*Atlanta 2, GA ('''atlanta2.voip.ms''') 209.217.224.50
*Chicago 1, IL ('''chicago.voip.ms''') 69.162.175.27
*Chicago 2, IL ('''chicago2.voip.ms''') 69.162.175.28
*Chicago 3, IL ('''chicago3.voip.ms''') 69.162.175.29
*Chicago 4, IL ('''chicago4.voip.ms''') 208.100.39.55
*Chicago 5, IL ('''chicago5.voip.ms''') 50.31.115.149
*Chicago 6, IL ('''chicago6.voip.ms''') 50.31.115.150
*Chicago 7, IL ('''chicago7.voip.ms''') 50.31.115.151
*Dallas, TX ('''dallas.voip.ms''') 158.85.149.162
*Dallas 2, TX ('''dallas2.voip.ms''') 158.85.149.163
*Denver 1, CO ('''denver.voip.ms''') 23.239.211.90
*Denver 2, CO ('''denver2.voip.ms''') 64.27.52.226
*Houston, TX ('''houston.voip.ms''') 205.251.137.130
*Houston 2, TX ('''houston2.voip.ms''') 74.81.95.146
*Los Angeles 1, CA ('''losangeles.voip.ms''') 104.254.128.162
*Los Angeles 2, CA ('''losangeles2.voip.ms''') 104.254.128.2
*Los Angeles 3, CA ('''losangeles3.voip.ms''') 64.188.6.162
*Los Angeles 4, CA ('''losangeles4.voip.ms''') 64.188.6.170
*New York 1, NY ('''newyork.voip.ms''') 72.251.239.196
*New York 2, NY ('''newyork2.voip.ms''') 72.251.239.205
*New York 3, NY ('''newyork3.voip.ms''') 72.251.239.206
*New York 4, NY ('''newyork4.voip.ms''') 72.251.239.207
*New York 5, NY ('''newyork5.voip.ms''') 23.29.136.28
*New York 6, NY ('''newyork6.voip.ms''') 23.29.136.29
*New York 7, NY ('''newyork7.voip.ms''') 23.29.136.38
*New York 8, NY ('''newyork8.voip.ms''') 23.29.136.40
*San Jose, CA ('''sanjose.voip.ms''') 23.246.247.146
*San Jose 2, CA ('''sanjose2.voip.ms''') 23.246.247.147
*Seattle 1, WA ('''seattle.voip.ms''') 50.23.160.53
*Seattle 2, WA ('''seattle2.voip.ms''') 50.23.149.166
*Seattle 3, WA ('''seattle3.voip.ms''') 50.23.160.54
*Tampa, FL ('''tampa.voip.ms''') 162.254.144.173
*Tampa 2, FL ('''tampa2.voip.ms''') 209.133.209.70
*Tampa 3, FL ('''tampa3.voip.ms''') 23.111.187.139
*Tampa 4, FL ('''tampa4.voip.ms''') 23.111.166.202
*Washington 1, DC ('''washington.voip.ms''') 169.62.41.187
*Washington 2, DC ('''washington2.voip.ms''') 169.62.41.189
</li>

<li style="display: inline-block; vertical-align:top;">
'''Internationaux'''
*Amsterdam, NL ('''amsterdam.voip.ms''') 66.212.22.42
*London, UK ('''london.voip.ms''') 159.8.157.212
*Paris, FR ('''paris.voip.ms''') 159.8.85.180
</li>
</ul></div>

=== Serveur Realms ===

Pour IOS, s'il vous plaît utiliser le lien [http://wiki.voip.ms/article/Server_Realms Serveur Realms] pour obtenir le nom du serveur Realms que vous prévoyez utiliser, cela peut être différent du nom de domaine utilisé.

= Qu'est-ce qu'un ping? =

Un Ping est un outil standard utilisé pour tester les connexions réseau. Il est principalement utilisé pour déterminer si un serveur ou un périphérique peut être atteint sur le réseau et la latence de la réponse (le temps qu'il faut pour envoyer un paquet à la destination souhaitée et pour qu'il vous revienne sur votre ordinateur).

Les outils Ping font partie de Windows, Mac OS X et Linux ainsi que de certains routeurs.

== Comment fonctionne le ping? ==

Il envoie des messages de demande à une adresse réseau cible ou à des noms DNS à intervalle régulier et mesure le temps nécessaire à un message pour s'y rendre et revenir (mieux connu sous le nom de latence).

= La latence et son importance =

La latence est très importante pour la Voix sur IP, cela déterminera le temps nécessaire à la transmission du paquet de données pour atteindre la destination. Une latence élevée entraînera un retard et des échos dans la communication.

La latence se mesure en millisecondes (ms) Par exemple: une latence de 150ms est à peine perceptible, donc acceptable. Avec une valeur plus haute que celle-ci, la qualité de l'appel commence à être affectée. Lorsqu'elle dépasse 300 ms, cela devient inacceptable.

[[category:guides]]

Choosing Server

2021-06-23T12:57:38Z

B13n:

[[File:ChooseServerImg.png|thumb|none|1280px|VoIP.ms servers]]

{| class="wikitable"
|+
|-
! Article en Français !! Artículo en Español
|-
| [https://wiki.voip.ms/article/Choisir_un_serveur Français] ||
[https://wiki.voip.ms/article/Elegir_servidor Español]
|}

= Choosing a Server =

[http://www.voip.ms VoIP.ms] offers many different servers, but which one should you choose? One misconception is that you should pick the closest to your location, however this is not needed most of the time. For example, if you are in the USA, any of the US servers will provide a really good latency and service quality. The newest server within a city is indicated with the highest number attached to the name, as they are classified in ascending order. Also worth noting is that there is a network tool that will help you when deciding which server you want to use, generally named a "ping", which will provide you the latency between you and the server. Therefore the server which provides you less latency should be used.

'''Note:''' Please bear in mind that some servers might not be available for your DID number to be used as POP (Point of presence) at the ''Manage DIDs'' section.
Make sure that your SIP/IAX device and your phone number are pointing to the same server.

=== IPs ===

<div><ul>
<li style="display: inline-block; vertical-align:top;">
'''Canada'''
*Montreal 1, QC ('''montreal.voip.ms''') 192.175.96.73
*Montreal 2, QC ('''montreal2.voip.ms''') 192.175.96.74
*Montreal 3, QC ('''montreal3.voip.ms''') 192.175.96.68
*Montreal 4, QC ('''montreal4.voip.ms''') 67.205.74.179
*Montreal 5, QC ('''montreal5.voip.ms''') 192.175.96.69
*Montreal 6, QC ('''montreal6.voip.ms''') 192.175.96.70
*Montreal 7, QC ('''montreal7.voip.ms''') 192.175.96.71
*Montreal 8, QC ('''montreal8.voip.ms''') 192.175.96.72
*Montreal 9, QC ('''montreal9.voip.ms''') 67.205.74.184
*Montreal 10, QC ('''montreal10.voip.ms''') 67.205.74.187
*Toronto 1, ON ('''toronto.voip.ms''') 158.85.70.148
*Toronto 2, ON ('''toronto2.voip.ms''') 158.85.70.149
*Toronto 3, ON ('''toronto3.voip.ms''') 158.85.70.150
*Toronto 4, ON ('''toronto4.voip.ms''') 158.85.70.151
*Toronto 5, ON ('''toronto5.voip.ms''') 184.75.215.106
*Toronto 6, ON ('''toronto6.voip.ms''') 184.75.215.114
*Toronto 7, ON ('''toronto7.voip.ms''') 184.75.215.146
*Toronto 8, ON ('''toronto8.voip.ms''') 184.75.213.210
*Toronto 9, ON ('''toronto9.voip.ms''') 158.85.70.154
*Toronto 10, ON ('''toronto10.voip.ms''') 158.85.70.158
*Vancouver 1, BC ('''vancouver.voip.ms''') 162.213.157.220
*Vancouver 2, BC ('''vancouver2.voip.ms''') 162.213.157.117
*Vancouver 3, BC ('''vancouver3.voip.ms''') 162.213.157.82
</li>

<li style="display: inline-block; vertical-align:top;">
'''United States'''
*Atlanta 1, GA ('''atlanta.voip.ms''') 75.127.65.130
*Atlanta 2, GA ('''atlanta2.voip.ms''') 209.217.224.50
*Chicago 1, IL ('''chicago.voip.ms''') 69.162.175.27
*Chicago 2, IL ('''chicago2.voip.ms''') 69.162.175.28
*Chicago 3, IL ('''chicago3.voip.ms''') 69.162.175.29
*Chicago 4, IL ('''chicago4.voip.ms''') 208.100.39.55
*Chicago 5, IL ('''chicago5.voip.ms''') 50.31.115.149
*Chicago 6, IL ('''chicago6.voip.ms''') 50.31.115.150
*Chicago 7, IL ('''chicago7.voip.ms''') 50.31.115.151
*Dallas, TX ('''dallas.voip.ms''') 158.85.149.162
*Dallas 2, TX ('''dallas2.voip.ms''') 158.85.149.163
*Denver 1, CO ('''denver.voip.ms''') 23.239.211.90
*Denver 2, CO ('''denver2.voip.ms''') 64.27.52.226
*Houston, TX ('''houston.voip.ms''') 205.251.137.130
*Houston 2, TX ('''houston2.voip.ms''') 74.81.95.146
*Los Angeles 1, CA ('''losangeles.voip.ms''') 104.254.128.162
*Los Angeles 2, CA ('''losangeles2.voip.ms''') 104.254.128.2
*Los Angeles 3, CA ('''losangeles3.voip.ms''') 64.188.6.162
*Los Angeles 4, CA ('''losangeles4.voip.ms''') 64.188.6.170
*New York 1, NY ('''newyork.voip.ms''') 72.251.239.196
*New York 2, NY ('''newyork2.voip.ms''') 72.251.239.205
*New York 3, NY ('''newyork3.voip.ms''') 72.251.239.206
*New York 4, NY ('''newyork4.voip.ms''') 72.251.239.207
*New York 5, NY ('''newyork5.voip.ms''') 23.29.136.28
*New York 6, NY ('''newyork6.voip.ms''') 23.29.136.29
*New York 7, NY ('''newyork7.voip.ms''') 23.29.136.38
*New York 8, NY ('''newyork8.voip.ms''') 23.29.136.40
*San Jose, CA ('''sanjose.voip.ms''') 23.246.247.146
*San Jose 2, CA ('''sanjose2.voip.ms''') 23.246.247.147
*Seattle 1, WA ('''seattle.voip.ms''') 104.129.57.250
*Seattle 2, WA ('''seattle2.voip.ms''') 173.205.93.122
*Seattle 3, WA ('''seattle3.voip.ms''') 173.205.93.226
*Tampa, FL ('''tampa.voip.ms''') 162.254.144.173
*Tampa 2, FL ('''tampa2.voip.ms''') 209.133.209.70
*Tampa 3, FL ('''tampa3.voip.ms''') 23.111.187.139
*Tampa 4, FL ('''tampa4.voip.ms''') 23.111.166.202
*Washington 1, DC ('''washington.voip.ms''') 169.62.41.189
*Washington 2, DC ('''washington2.voip.ms''') 169.62.41.187
</li>

<li style="display: inline-block; vertical-align:top;">
'''International'''
*Amsterdam, NL ('''amsterdam.voip.ms''') 66.212.22.42
*London, UK ('''london.voip.ms''') 159.8.157.212
*Sydney, AU ('''sydney1.voip.ms''') 168.1.73.84
*Paris, FR ('''paris.voip.ms''') 159.8.85.180
</li>
</ul></div>

===Server Realms===

For IOS, Please click here [http://wiki.voip.ms/article/Server_Realms Server Realms] to get the Realm Name for the server you plan on using, this can differ from the Domain Name being used.

= What is a Ping? =

Ping is a standard tool used to test network connections. It is mostly used to determine if a server or device can be reached across the network and the latency of the response(the time it takes to send a packet to the destination and for it to return to your computer).

Ping tools are part of Windows, Mac OS X and Linux as well as some routers.

== How does the ping work? ==

It sends request messages to a target network address or DNS names at periodic intervals and measures the time it takes for a response message to arrive and return(better known as latency).

==How to ping on a PC==

Pinging is a command which tells you if the connection between your computer and a particular domain is working correctly.

In Windows, select Start > Programs > Accessories > Command Prompt. This will give you a window like the one below.

Enter the word ping, followed by a space, then the domain name.(montreal.voip.ms) in this case domain is our server name.

If the results show a series of replies, the connection is working. The time shows you how fast the connection is. If you see a "timed out" error instead of a reply, there is a breakdown somewhere between your computer and the domain.

[[File:Ping.gif|thumb|none|600px|Ping]]

==How to ping on a Mac Computer==

1- Click on Finder in the dock.

2- Click on Applications.

3- Click on Utilities.

4- Double-click on Network Utility. *

* In OS X Mavericks (10.9.x) this utility app changed location. Launch it from spotlight instead, either press "command"+"space bar" or click on spotlight directly (magnifying glass icon at top right of screen), type "network utility" and hit "return"

5- In the Network Utility window, click on the Ping tab

6- In the field under "Please enter the network address to ping," like montreal.voip.ms

''If pings results are not consistent, you may have an issue with Jitter. You can work on this issue by adjusting the "Network Jitter Level" setting on your VoIP device. Usually a ping of under 150 ms is recommended in order to have good quality. The latency time to the server is important, however there are also other factors that could affect the quality of the calls such as packet loss (VoIP communications are very sensitive to this), and the Jitter level of your Internet connection.''

The following is the output of running ping with the target losangeles.voip.ms.

#ping losangeles.voip.ms
Ping to losangeles.voip.ms [67.215.241.250] with 32 bytes de datos:
Response from 67.215.241.250: bytes=32 time=67ms TTL=52
Response from 67.215.241.250: bytes=32 time=69ms TTL=52
Response from 67.215.241.250: bytes=32 time=68ms TTL=52
Response from 67.215.241.250: bytes=32 time=67ms TTL=52
ping statistics from 67.215.241.250:
4 packets transmitted, 4 received, 0% packet lost. rtt min/avg/max/mdev = 67ms, 69ms, 67ms

Sample ping output in windows:
C:\Windows\system32>ping montreal.voip.ms

Pinging montreal.voip.ms [67.205.74.184] with 32 bytes of data:
Reply from 67.205.74.184: bytes=32 time=85ms TTL=49
Reply from 67.205.74.184: bytes=32 time=86ms TTL=49
Reply from 67.205.74.184: bytes=32 time=86ms TTL=49
Reply from 67.205.74.184: bytes=32 time=85ms TTL=49

Ping statistics for 67.205.74.184:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 85ms, Maximum = 86ms, Average = 85ms

= Latency Testing Scripts (User Submitted) =
<p>All the following scripts were produced by voip.ms users who felt others might also benefit from the output of their efforts. They were written over a span of Years and probably need adjusting before you use them, to cater for changes in servers over time and changes in policies (like not testing heavily subscribed servers which are not open to new registrations)</p>
<p>If you aren't satisfied that the scripts are safe or simply don’t like the way they syntactically appear, you can still manually ping a selection of servers and choose a server based on the best latency. The following scripts are essentially just wrappers around the ping command which support lists of servers to feed to ping and present the output in a readable format.</p>
<p>If you feel you have a simpler cleaner script that works for another platform or language, please do add it to this wiki via a support ticket.
</p>
=== Bash Script To Handle The Mac Ping Output Format ===

<p>To make use of this script (1) save as a plain text file (2) set permissions on the file to executable (3) invoke script
e.g. Save script below using your favourite editor as pingVoipMS.sh (2) chmod u+x pingVoipMS.sh (3) ./pingVoipMS.sh
This is a bash 3.x script, so it also works in Linux, just change the ping packet loss field from 7 to 6 in the final loop below (or wherever the loss field is in your ping output format). Depending upon your distro curl might need to change to wget.
</p>
<pre>
#!/bin/bash
# Ping several servers and display Latency, Jitter and Packet Loss
# Usage: [-c <count>][-i <wait time>][-r test restricted servers][<server list file>]
#
# The optional server list text file should be formatted with one host name per line.
# The list of voip.ms servers is available at https://wiki.voip.ms/article/Choosing_Server
# If no args are supplied, this script will scrape a ping server list from voip.ms
#
USER_FILE=""
COUNT=3; INTERVAL=5; RESTRICTED=0
restrictedList=(atlanta.voip.ms chicago.voip.ms
montreal.voip.ms montreal2.voip.ms montreal3.voip.ms montreal4.voip.ms
newyork.voip.ms newyork4.voip.ms seattle.voip.ms
toronto.voip.ms toronto2.voip.ms toronto3.voip.ms toronto4.voip.ms)

# Handle any passed in script arguments
while getopts c:i:r parm
do
case $parm in
c)count_opt=$OPTARG;;
i)interval_opt=$OPTARG;;
r)RESTRICTED=1;;
*)echo -e "Invalid arg\nUsage:\t[ -c <count of ECHO_REQUESTs to Tx, default 3> ] \
\n\t[ -i <wait time (s) between datagrams, default 5> ] \
\n\t[ -r ] Include restricted servers in latency test \
\n\t[FILE <ping server list> ]";exit 1;;
esac
done

# Test if an option was specified and whether it's a +ve non-zero integer
[[ -n $count_opt && ($count_opt =~ ^[[:digit:]]+$) && $count_opt -gt 0 ]] &&
COUNT=$count_opt
[[ -n $interval_opt && ($interval_opt =~ ^[[:digit:]]+$) && $interval_opt -gt 0 ]] &&
INTERVAL=$interval_opt

shift $((OPTIND - 1))

# Validate supplied file (server list)
[[ -n $1 && ! (-f $1 && -r $1) ]] &&
{ echo "\"$1\" file does not exist or is not readable"; exit 1; }
[[ -n $1 && -f $1 && -r $1 ]] && USER_FILE="$1"

if [[ -n $USER_FILE ]]
then
# Bash 3.x in macOS does not support readarray, need to do cumbersome array loops instead
while IFS= read -r servers; do
serverList+=( "$servers" )
done < <(grep -Eo '^\b[[:alpha:]]+?[[:alnum:]]\.voip\.ms\b$' "$USER_FILE" | \
grep -v '^\s*#' | awk NF | sort)
else
# N.B. The script looks for the html boldface tags <b> </b> inside a bracket
# If the website alters and the parse fails, manually create the list and
# supply as a script arg (or perhaps update the parsing to work again :)
while IFS= read -r servers; do
serverList+=( "$servers" )
done < <(curl -sm 10 https://wiki.voip.ms/article/Choosing_Server | \
grep -E '(<b>[[:alpha:]]+?[[:alnum:]]\.voip\.ms</b>)' | \
tr "<>" " " | awk '{print $(NF-3)}' | sort )
fi

# Newer voip.ms clients can't register onto these over-subscribed servers
# Don't test the restricted list unless explicitly asked (with the -r cmd line option)
if [[ $RESTRICTED -eq 0 ]]
then
for server in "${restrictedList[@]}"
do
ix=$(printf "%s\n" "${serverList[@]}" | grep -n "^${server}" | cut -d ":" -f1)
while IFS= read -ra idx; do
keys+=( "${idx[@]}" )
done < <([[ $ix -gt 0 ]] && echo $((ix-1)))
done
for ((i=${#keys[@]} - 1; i >= 0; i--)); do unset "serverList[keys[i]]"; done
fi

if [[ ${#serverList[@]} -eq 0 ]]
then
echo "No unrestricted Voip.ms servers could be found, please supply a server list"
exit 1
fi

runTime=$((COUNT * INTERVAL * ${#serverList[@]}))

echo "PING will send $COUNT packet(s) with a wait of $INTERVAL sec(s) between each packet"
echo "Change the PING options by invoking this script with -c and/or -i, default \"-c 3 -i 5\""
echo "Over $((${#serverList[@]})) server(s) the estimated script Run Time will be $runTime seconds"
echo "================================================================"
printf "%-20s %-18s %7s %8s %6s %s\n" "VoIP Server" "IP Address" "Latency" "Jitter" "Loss" "Countdown"
echo "================================================================ (seconds)"

for myLn in "${serverList[@]}"
do
while IFS=$'\n' read -r pings; do
pingList+=( "$pings" )
printf "%-64s %5d %2d/%-2d\n" "$pings" \
"$((runTime - COUNT * INTERVAL * ${#pingList[@]}))" \
"${#pingList[@]}" "${#serverList[@]}"
done < <( ping -c "$COUNT" -i "$INTERVAL" -q "$myLn" | awk \
'
/^PING / {myH=$2}
/^PING / {
IP = substr($3,2,15)
split(IP,myIP,")") }
/packet loss/ {myPL=$7}
/min\/avg\/max/ {
split($4,myS,"/")
printf("%-20s %-18s %7.3f %8.3f %6s\n",
myH, myIP[1], myS[2], myS[4], myPL ) }
' )
done

echo "================================================================"
echo -e "\nMost appropriate server listed in order of best latency\n"
echo "================================================================"
printf "%-20s %-18s %7s %8s %6s\n" "VoIP Server" "IP Address" "Latency" "Jitter" "Loss"
echo "================================================================"
printf "%s\n" "${pingList[@]}" | LC_ALL=C sort -n -k 3,3 -k 5,5 -k 4,4 | \
awk '{printf("%s $%2d$\n",$0, NR)}'
echo "================================================================"
</pre>

=== Perl Script ===
Pings list of voip.ms servers round robin with optional output csv file.

# usage ping_voip.ms.pl <number of times> <seconds in between> <output.csv>
use Net::Ping;
use Time::HiRes;
use strict;

# input list
my @hosts = qw(
atlanta.voip.ms
atlanta2.voip.ms
chicago.voip.ms
chicago2.voip.ms
chicago3.voip.ms
chicago4.voip.ms
dallas.voip.ms
denver.voip.ms
denver2.voip.ms
houston.voip.ms
losangeles.voip.ms
losangeles2.voip.ms
newyork.voip.ms
newyork2.voip.ms
newyork3.voip.ms
newyork4.voip.ms
seattle.voip.ms
seattle2.voip.ms
seattle3.voip.ms
tampa.voip.ms
washington.voip.ms
washington2.voip.ms
montreal.voip.ms
montreal2.voip.ms
montreal3.voip.ms
montreal4.voip.ms
toronto2.voip.ms
toronto3.voip.ms
toronto4.voip.ms
toronto.voip.ms
london.voip.ms
);

$| = 1; #autoflush
# High precision syntax (requires Time::HiRes)
my $p = Net::Ping->new("icmp",1);
$p->hires();
my $max_name_length = (reverse sort { $a <=> $b } map { length($_) } @hosts)[0];
my $count = 4; # number of times to ping
my $interval = 5; # seconds between ping rounds
my $output_file = "";
my @data;

# check for arguments
my $num_args = @ARGV;
if ($num_args >= 1) {$count = $ARGV[0];}
if ($num_args >= 2) {$interval = $ARGV[1];}
if ($num_args >= 3) {$output_file = $ARGV[2];}

# check argument validity
$0 =~ /^.*\\(.*)$/;
my $script = $1;
if ($count !~ /^\d+$/ or $interval !~ /^\d+$/) {die "Usage: $script <number of rounds> <seconds between rounds> <output.csv>\n";}
if (length($output_file) > 0 and $output_file !~ /\.csv$/) {$output_file .= ".csv";}

# main loop
for my $i (1..$count)
{
sleep $interval unless $i == 1;
print "Round $i\n";
my $host_num=0;
foreach my $host (@hosts)
{
(my $ret, my $duration, my $ip) = $p->ping($host);
$ip =~ /(\d+)\.(\d+)\.(\d+)\.(\d+)/;
if ($ret)
{
printf("%*s [ip: %3s.%3s.%3s.%3s] is alive (%6.2f ms)\n", $max_name_length, $host, $1, $2, $3, $4, $duration*1000);
$data[$host_num][$i]=$duration*1000;
}
else
{
printf("%*s [ip: %3s.%3s.%3s.%3s] is dead\n", $max_name_length, $host, $1, $2, $3, $4);
}
$host_num++;
}
print "\n";
}
$p->close();

# if output file name given
if (length($output_file)>0)
{
# print output to file
open FILE, ">$output_file" or die "$!\n";

# print column headers
print FILE "Server\\Round";
for my $i (1..$count)
{
print FILE ", $i";
}
print FILE ", Average\n";

# print data
my $i = 0;
foreach my $host (@hosts)
{
print FILE "$host";
my $sum = 0;
for my $j (1..$count)
{
$sum += $data[$i][$j];
printf FILE ", %8.4f",$data[$i][$j];
}
printf FILE ", %8.4f\n",$sum/$count;
$i++;
}

close FILE;
print "Data written to $output_file\n";
}

# print summary to screen
my $i = 0;
printf("%-*s Average (ms)\n", $max_name_length, "Server");
foreach my $host (@hosts)
{
my $sum = 0;
for my $j (1..$count)
{
$sum += $data[$i][$j];
}
printf("%-*s %8.4f\n", $max_name_length+1, $host, $sum/$count);
$i++;
}

Output:
Round 1
atlanta.voip.ms [ip: 174. 34.146.162] is alive ( 88.97 ms)
atlanta2.voip.ms [ip: 72. 9.246.170] is alive ( 92.99 ms)
chicago.voip.ms [ip: 208.100. 39. 52] is alive ( 49.70 ms)
chicago2.voip.ms [ip: 208.100. 39. 53] is alive ( 59.76 ms)
chicago3.voip.ms [ip: 208.100. 39. 54] is alive ( 59.53 ms)
chicago4.voip.ms [ip: 208.100. 39. 55] is alive ( 49.73 ms)
dallas.voip.ms [ip: 74. 54. 54.178] is alive ( 94.99 ms)
denver.voip.ms [ip: 173.248.161. 90] is alive ( 94.05 ms)
denver2.voip.ms [ip: 173.248.159.210] is alive ( 85.13 ms)
houston.voip.ms [ip: 209. 62. 1. 2] is alive (102.87 ms)
losangeles.voip.ms [ip: 96. 44.149.186] is alive ( 64.92 ms)
losangeles2.voip.ms [ip: 96. 44.149.202] is alive ( 63.41 ms)
newyork.voip.ms [ip: 74. 63. 41.218] is alive (131.75 ms)
newyork2.voip.ms [ip: 107. 6. 67.236] is alive (120.64 ms)
newyork3.voip.ms [ip: 107. 6. 67.237] is alive (120.49 ms)
newyork4.voip.ms [ip: 107. 6. 67.238] is alive (111.43 ms)
seattle.voip.ms [ip: 50. 23.160. 50] is alive ( 94.25 ms)
seattle2.voip.ms [ip: 50. 23.160. 51] is alive ( 95.86 ms)
seattle3.voip.ms [ip: 50. 23.160. 52] is alive ( 90.85 ms)
tampa.voip.ms [ip: 68.233.226. 97] is alive (123.29 ms)
washington.voip.ms [ip: 208. 43.234.226] is alive ( 98.71 ms)
washington2.voip.ms [ip: 208. 43.234.227] is alive (101.19 ms)
montreal.voip.ms [ip: 67.205. 74.184] is alive ( 81.82 ms)
montreal2.voip.ms [ip: 67.205. 74.187] is alive ( 86.13 ms)
montreal3.voip.ms [ip: 72. 55.168. 18] is alive ( 77.09 ms)
montreal4.voip.ms [ip: 67.205. 74.179] is alive ( 96.18 ms)
toronto2.voip.ms [ip: 184. 75.215.114] is alive (103.70 ms)
toronto3.voip.ms [ip: 184. 75.215.146] is alive (131.27 ms)
toronto4.voip.ms [ip: 184. 75.213.210] is alive (125.13 ms)
toronto.voip.ms [ip: 184. 75.215.106] is alive (103.26 ms)
london.voip.ms [ip: 5. 77. 36.136] is alive (152.77 ms)

Round 2
atlanta.voip.ms [ip: 174. 34.146.162] is alive ( 88.14 ms)
atlanta2.voip.ms [ip: 72. 9.246.170] is alive ( 92.86 ms)
chicago.voip.ms [ip: 208.100. 39. 52] is alive ( 50.03 ms)
chicago2.voip.ms [ip: 208.100. 39. 53] is alive ( 59.44 ms)
chicago3.voip.ms [ip: 208.100. 39. 54] is alive ( 59.33 ms)
chicago4.voip.ms [ip: 208.100. 39. 55] is alive ( 50.22 ms)
dallas.voip.ms [ip: 74. 54. 54.178] is alive ( 95.58 ms)
denver.voip.ms [ip: 173.248.161. 90] is alive ( 95.94 ms)
denver2.voip.ms [ip: 173.248.159.210] is alive ( 85.29 ms)
houston.voip.ms [ip: 209. 62. 1. 2] is alive (102.73 ms)
losangeles.voip.ms [ip: 96. 44.149.186] is alive ( 65.59 ms)
losangeles2.voip.ms [ip: 96. 44.149.202] is alive ( 64.27 ms)
newyork.voip.ms [ip: 74. 63. 41.218] is alive (112.74 ms)
newyork2.voip.ms [ip: 107. 6. 67.236] is alive (121.22 ms)
newyork3.voip.ms [ip: 107. 6. 67.237] is alive (121.34 ms)
newyork4.voip.ms [ip: 107. 6. 67.238] is alive (110.75 ms)
seattle.voip.ms [ip: 50. 23.160. 50] is alive ( 94.06 ms)
seattle2.voip.ms [ip: 50. 23.160. 51] is alive ( 95.33 ms)
seattle3.voip.ms [ip: 50. 23.160. 52] is alive ( 91.58 ms)
tampa.voip.ms [ip: 68.233.226. 97] is alive (122.94 ms)
washington.voip.ms [ip: 169.62.41.189] is alive ( 98.28 ms)
washington2.voip.ms [ip: 169.62.41.187] is alive (101.40 ms)
montreal.voip.ms [ip: 67.205. 74.184] is alive ( 81.91 ms)
montreal2.voip.ms [ip: 67.205. 74.187] is alive ( 85.64 ms)
montreal3.voip.ms [ip: 72. 55.168. 18] is alive ( 75.15 ms)
montreal4.voip.ms [ip: 67.205. 74.179] is alive ( 96.79 ms)
toronto2.voip.ms [ip: 184. 75.215.114] is alive (103.10 ms)
toronto3.voip.ms [ip: 184. 75.215.146] is alive (150.85 ms)
toronto4.voip.ms [ip: 184. 75.213.210] is alive (138.40 ms)
toronto.voip.ms [ip: 184. 75.215.106] is alive (103.45 ms)
london.voip.ms [ip: 5. 77. 36.136] is alive (170.79 ms)

Round 3
atlanta.voip.ms [ip: 174. 34.146.162] is alive ( 88.76 ms)
atlanta2.voip.ms [ip: 72. 9.246.170] is alive ( 92.86 ms)
chicago.voip.ms [ip: 208.100. 39. 52] is alive ( 49.65 ms)
chicago2.voip.ms [ip: 208.100. 39. 53] is alive ( 60.01 ms)
chicago3.voip.ms [ip: 208.100. 39. 54] is alive ( 59.05 ms)
chicago4.voip.ms [ip: 208.100. 39. 55] is alive ( 49.53 ms)
dallas.voip.ms [ip: 74. 54. 54.178] is alive ( 95.82 ms)
denver.voip.ms [ip: 173.248.161. 90] is alive ( 95.02 ms)
denver2.voip.ms [ip: 173.248.159.210] is alive ( 85.60 ms)
houston.voip.ms [ip: 209. 62. 1. 2] is alive (103.35 ms)
losangeles.voip.ms [ip: 96. 44.149.186] is alive ( 65.79 ms)
losangeles2.voip.ms [ip: 96. 44.149.202] is alive ( 64.05 ms)
newyork.voip.ms [ip: 74. 63. 41.218] is alive (113.01 ms)
newyork2.voip.ms [ip: 107. 6. 67.236] is alive (121.41 ms)
newyork3.voip.ms [ip: 107. 6. 67.237] is alive (122.23 ms)
newyork4.voip.ms [ip: 107. 6. 67.238] is alive (110.62 ms)
seattle.voip.ms [ip: 50. 23.160. 50] is alive ( 93.65 ms)
seattle2.voip.ms [ip: 50. 23.160. 51] is alive ( 95.19 ms)
seattle3.voip.ms [ip: 50. 23.160. 52] is alive ( 90.75 ms)
tampa.voip.ms [ip: 68.233.226. 97] is alive (125.12 ms)
washington.voip.ms [ip: 208. 43.234.226] is alive ( 98.19 ms)
washington2.voip.ms [ip: 208. 43.234.227] is alive (101.98 ms)
montreal.voip.ms [ip: 67.205. 74.184] is alive ( 80.16 ms)
montreal2.voip.ms [ip: 67.205. 74.187] is alive ( 87.16 ms)
montreal3.voip.ms [ip: 72. 55.168. 18] is alive ( 76.54 ms)
montreal4.voip.ms [ip: 67.205. 74.179] is alive ( 97.51 ms)
toronto2.voip.ms [ip: 184. 75.215.114] is alive (104.18 ms)
toronto3.voip.ms [ip: 184. 75.215.146] is alive (142.81 ms)
toronto4.voip.ms [ip: 184. 75.213.210] is alive (138.95 ms)
toronto.voip.ms [ip: 184. 75.215.106] is alive (103.78 ms)
london.voip.ms [ip: 5. 77. 36.136] is alive (153.14 ms)

Round 4
atlanta.voip.ms [ip: 174. 34.146.162] is alive ( 89.19 ms)
atlanta2.voip.ms [ip: 72. 9.246.170] is alive ( 92.98 ms)
chicago.voip.ms [ip: 208.100. 39. 52] is alive ( 49.21 ms)
chicago2.voip.ms [ip: 208.100. 39. 53] is alive ( 60.50 ms)
chicago3.voip.ms [ip: 208.100. 39. 54] is alive ( 59.68 ms)
chicago4.voip.ms [ip: 208.100. 39. 55] is alive ( 50.18 ms)
dallas.voip.ms [ip: 74. 54. 54.178] is alive ( 93.93 ms)
denver.voip.ms [ip: 173.248.161. 90] is alive ( 94.22 ms)
denver2.voip.ms [ip: 173.248.159.210] is alive ( 85.10 ms)
houston.voip.ms [ip: 209. 62. 1. 2] is alive (103.67 ms)
losangeles.voip.ms [ip: 96. 44.149.186] is alive ( 65.58 ms)
losangeles2.voip.ms [ip: 96. 44.149.202] is alive ( 63.60 ms)
newyork.voip.ms [ip: 74. 63. 41.218] is alive (114.76 ms)
newyork2.voip.ms [ip: 107. 6. 67.236] is alive (120.44 ms)
newyork3.voip.ms [ip: 107. 6. 67.237] is alive (121.05 ms)
newyork4.voip.ms [ip: 107. 6. 67.238] is alive (110.51 ms)
seattle.voip.ms [ip: 50. 23.160. 50] is alive ( 94.04 ms)
seattle2.voip.ms [ip: 50. 23.160. 51] is alive ( 96.92 ms)
seattle3.voip.ms [ip: 50. 23.160. 52] is alive ( 91.23 ms)
tampa.voip.ms [ip: 68.233.226. 97] is alive (123.28 ms)
washington.voip.ms [ip: 208. 43.234.226] is alive ( 98.45 ms)
washington2.voip.ms [ip: 208. 43.234.227] is alive (100.94 ms)
montreal.voip.ms [ip: 67.205. 74.184] is alive ( 82.33 ms)
montreal2.voip.ms [ip: 67.205. 74.187] is alive ( 85.02 ms)
montreal3.voip.ms [ip: 72. 55.168. 18] is alive ( 76.85 ms)
montreal4.voip.ms [ip: 67.205. 74.179] is alive ( 96.32 ms)
toronto2.voip.ms [ip: 184. 75.215.114] is alive (104.22 ms)
toronto3.voip.ms [ip: 184. 75.215.146] is alive (148.33 ms)
toronto4.voip.ms [ip: 184. 75.213.210] is alive (141.61 ms)
toronto.voip.ms [ip: 184. 75.215.106] is alive (105.91 ms)
london.voip.ms [ip: 5. 77. 36.136] is alive (152.85 ms)

Server Average (ms)
atlanta.voip.ms 88.7630
atlanta2.voip.ms 92.9233
chicago.voip.ms 49.6477
chicago2.voip.ms 59.9305
chicago3.voip.ms 59.3972
chicago4.voip.ms 49.9152
dallas.voip.ms 95.0790
denver.voip.ms 94.8077
denver2.voip.ms 85.2797
houston.voip.ms 103.1562
losangeles.voip.ms 65.4693
losangeles2.voip.ms 63.8347
newyork.voip.ms 118.0643
newyork2.voip.ms 120.9265
newyork3.voip.ms 121.2778
newyork4.voip.ms 110.8275
seattle.voip.ms 93.9993
seattle2.voip.ms 95.8267
seattle3.voip.ms 91.1035
tampa.voip.ms 123.6570
washington.voip.ms 98.4065
washington2.voip.ms 101.3774
montreal.voip.ms 81.5525
montreal2.voip.ms 85.9863
montreal3.voip.ms 76.4058
montreal4.voip.ms 96.7013
toronto2.voip.ms 103.7986
toronto3.voip.ms 143.3156
toronto4.voip.ms 136.0254
toronto.voip.ms 104.1012
london.voip.ms 157.3885

=== Powershell ===

Dec 2017 - A bug in the code shown washington2.voip.ms as the best server, this was corrected.

<pre>
# Usage: Copy and paste the following code into a powershell window
# To run it from a command prompt, save this file with extension ps1.
# Then run Powershell.exe -file "pathtothisscript.ps1"
Clear-Variable best* -Scope Global #Clear the best* variables in case you run it more than once...
#Get the list of servers into an array
$Servers =
@("amsterdam.voip.ms","atlanta.voip.ms","atlanta2.voip.ms","chicago.voip.ms","chicago2.voip.ms","chicago3.voip.ms",
"chicago4.voip.ms","dallas.voip.ms","dallas2.voip.ms","denver.voip.ms","denver2.voip.ms","houston.voip.ms",
"houston2.voip.ms","london.voip.ms","losangeles.voip.ms","losangeles2.voip.ms","montreal.voip.ms",
"montreal2.voip.ms","montreal3.voip.ms","montreal4.voip.ms","montreal5.voip.ms","montreal6.voip.ms","montreal7.voip.ms",
"montreal8.voip.ms","newyork.voip.ms","newyork2.voip.ms","newyork3.voip.ms","newyork4.voip.ms","newyork5.voip.ms",
"newyork6.voip.ms","newyork7.voip.ms","newyork8.voip.ms","paris.voip.ms","sanjose.voip.ms","sanjose2.voip.ms",
"seattle.voip.ms","seattle2.voip.ms","seattle3.voip.ms","tampa.voip.ms","tampa2.voip.ms","toronto.voip.ms",
"toronto2.voip.ms","toronto3.voip.ms","toronto4.voip.ms","toronto5.voip.ms","toronto6.voip.ms","toronto7.voip.ms",
"toronto8.voip.ms","vancouver.voip.ms","vancouver2.voip.ms","washington.voip.ms","washington2.voip.ms")
$k = 0 #Counting variable so we know what server number we are testing
#num of servers to test
$servercount = $servers.length
#Do the following code for each server in our array
ForEach($server in $servers)
{
#Add one to the counting variable....we are on server #1...then server 2, then server 3 etc...
$k++
#Update the progress bar
Write-Progress -Activity "Testing Server: ${server}" -status "Testing Server $k out of $servercount" -percentComplete ($k / $servercount*100)
#Counting variable for number of times we tried to ping a given server
$i = 0
Do{
#assume a failure
$pingsuccess = $false
$i++ #Add one to the counting variable.....1st try....2nd try....3rd try etc...
Try{
#Try to ping
$currentping = (test-connection $server -count 1 -ErrorAction Stop).responsetime
#If success full, set success variable
$pingsuccess = $true
}
#Catch the failure and set the success variable to false
Catch {
$pingsuccess = $false
}
}
#Try everything between Do and While up to 5 times, or while $pingsuccess is not true
While($pingsuccess -eq $false -and $i -le 5)
#Compare the last ping test with the best known ping test....if there is no known best ping test, assume this one is the best $bestping = $currentping
If($pingsuccess -and ($currentping -lt $bestping -or (!($bestping)))){
#If this is the best ping...save it
$bestserver = $server #Save the best server
$bestping = $currentping #Save the best ping results
}
write-host "tested: $server at $currentping ms after $i attempts" #write the results of the test for this server
}
write-host "`r`n The server with the best ping is: $bestserver at $bestping ms`r`n" #write the end result
Pause
</pre>

=== Linux Shell Script ===
Pings several voip.ms servers

#!/bin/sh
# Ping several servers and display Latency, Jitter and Packet Loss
#
# First, create a text file with all servers you want to ping - one host name per line.
# The list of voip.ms servers is available at http://wiki.voip.ms/article/Choosing_Server
myHF="voip_ping_hosts.txt"
# Sample file:
# toronto.voip.ms
# montreal.voip.ms
# seattle.voip.ms
# chicago.voip.ms
# newyork.voip.ms
#
echo "============================================"
printf "%-20s %7s %8s %6s\n" "VoIP Server" "Latency" "Jitter" "Loss"
echo "============================================"
cat ${myHF} |\
while read myLn
do
ping -c 3 -i 5 -q $myLn |\
awk '/^PING / {myH=$2}
/packet loss/ {myPL=$6}
/min\/avg\/max/ {
split($4,myS,"/")
printf( "%-20s %3.1f %1.3f %4s\n", myH, myS[2], myS[4], myPL)
}'
done
echo "============================================"

Output:

============================================
VoIP Server Latency Jitter Loss
============================================
toronto.voip.ms 68.3 0.439 0%
montreal.voip.ms 89.6 0.197 0%
seattle.voip.ms 71.2 0.387 0%
chicago.voip.ms 71.6 0.084 0%
newyork.voip.ms 79.1 0.411 0%
============================================

=== Using PingInfoView (Freeware, Windows Only) ===
PingInfoView is a tool that allows you to ping multiple servers at once which can be quite useful given the extended list of servers provided by Voip.ms. The tool can be found [https://www.nirsoft.net/utils/multiple_ping_tool.html here] (no affiliation with the author or voip.ms; direct download link [https://www.nirsoft.net/utils/pinginfoview.zip here]) and requires no installation, you can execute it directly from the zip file.

Server list (same as the list above, but simplified for easier copy/paste into the tool):
<div><ul>
<li style="display: inline-block; vertical-align:top;">
'''Canada'''
*montreal.voip.ms
*montreal2.voip.ms
*montreal3.voip.ms
*montreal4.voip.ms
*montreal5.voip.ms
*montreal6.voip.ms
*montreal7.voip.ms
*montreal8.voip.ms
*montreal9.voip.ms
*montreal10.voip.ms
*toronto.voip.ms
*toronto2.voip.ms
*toronto3.voip.ms
*toronto4.voip.ms
*toronto5.voip.ms
*toronto6.voip.ms
*toronto7.voip.ms
*toronto8.voip.ms
*toronto9.voip.ms
*toronto10.voip.ms
*vancouver.voip.ms
*vancouver2.voip.ms
*vancouver3.voip.ms
</li>

<li style="display: inline-block; vertical-align:top;">
'''United States'''
*atlanta.voip.ms
*atlanta2.voip.ms
*chicago.voip.ms
*chicago2.voip.ms
*chicago3.voip.ms
*chicago4.voip.ms
*chicago5.voip.ms
*chicago6.voip.ms
*chicago7.voip.ms
*dallas.voip.ms
*dallas2.voip.ms
*denver.voip.ms
*denver2.voip.ms
*houston.voip.ms
*houston2.voip.ms
*losangeles.voip.ms
*losangeles2.voip.ms
*losangeles3.voip.ms
*losangeles4.voip.ms
*newyork.voip.ms
*newyork2.voip.ms
*newyork3.voip.ms
*newyork4.voip.ms
*newyork5.voip.ms
*newyork6.voip.ms
*newyork7.voip.ms
*newyork8.voip.ms
*sanjose.voip.ms
*sanjose2.voip.ms
*seattle.voip.ms
*seattle2.voip.ms
*seattle3.voip.ms
*tampa.voip.ms
*tampa2.voip.ms
*tampa3.voip.ms
*tampa4.voip.ms
*washington.voip.ms
*washington2.voip.ms
</li>

<li style="display: inline-block; vertical-align:top;">
'''International'''
*amsterdam.voip.ms
*london.voip.ms
*sydney1.voip.ms
*paris.voip.ms
</li>
</ul></div>

Output:

[[File:PingInfoView_screenshot.png]]

= Latency and its importance =

Latency is very important for Voip, this will determine the time that will take for the data package transmission to reach the destination. A high latency will lead to a delay and echoes in the communication.

Latency is measured in milliseconds (ms) For example: a latency of 150ms is barely noticeable, thus acceptable. Higher than that, quality starts to suffer. When it gets higher than 300 ms, it becomes unacceptable.

[[category:guides]]

Grandstream DP750/DP720

2021-06-17T14:33:34Z

B13n:

== Grandstream DP750 Configuration Detail (Applies to model DP752 too) ==

[[File:DP750-720.png|thumb|none|600px]]

1. Type the DP715 Base Station IP address in your PC browser e.g. ''http://192.168.2.1''

2. Log in using username and password of "admin" to configure the DP750 Base Station.

3. Navigate to the Profiles > Profiles 1, and select ' '''General Settings''' '.

[[File:DP750-Profile1-General.png|thumb|none|600px]]

* Select a name. This is only for your own use.
* One of VoIP.ms multiple [[Choosing Server | servers]], you can choose the one closest to your location. Please note that in order for inbound calls to work the server chosen must match the one used by your DID Number.
* Click on the '''Save and Apply''' button.

4. Navigate to the SIP Settings > Basic Settings menu on the left.

[[File:Sip_-_Basic_Settings_-_1.png|thumb|none|600px]]

* Select either '''UDP''', or if your account is configured to use [[Call_Encryption_-_TLS/SRTP | SRTP encryption]], select '''TLS/TCP'''.
* Set the Local SIP Port to 5060 for UDP, if your account is configured to use [[Call_Encryption_-_TLS/SRTP | SRTP encryption]], use the port 5061.
* Click on the '''Save and Apply''' button.

[[File:Profile_1_sip_basic_2.png|thumb|none|600px]]

5. Navigate to the Profiles > Profile 1 > '''Audio Settings'''.

[[File:Profile_1_Audio_Settings.png|thumb|none|600px]]

* Select both '''In-Audio''' and '''via RTP''' for the send DTMF option.

[[File:Profile_1_Audio_2.png|thumb|none|600px]]

* If you are using '''SRTP / TLS/TCP''', ensure the '''SRTP Mode''' option is set to '''Enabled and Forced'''.
* Click on the '''Save and Apply''' button.

6. Navigate to '''DECT''' > '''Sip Account Settings'''.

[[File:Sip_Account_Settings.png|thumb|none|600px]]

* In the Account 1 line, enter your SIP User ID into both the '''SIP User ID''' and '''Authenticate ID''' fields.
* Enter the password for the SIP account in the password field.
* For the '''Name''' field. '''See the requirements below.''' ''This your '''Outbound Caller ID Name''' when you call a Canadian number which will be displayed on the Display screen.''

'''IMPORTANT INFO FOR CALLER ID NAME''':
- We suggest entering your outbound Caller ID Name must be in '''capital letters'''. This will appears more clearly/visible on some devices.
- You must NOT use any special characters, they will not be displayed.
- Some of regular Canadian providers will not show more than 15 characters. We suggest shrinking or adapt your caller ID.
- Spaces are allowed in a caller id name.

* Click on the '''Save and Apply''' button.

7. Navigate to '''DECT''' > '''Handset Line Settings'''.

[[File:Handset_Line_Settings.png|thumb|none|600px]]

* Ensure the SIP account that you created in step 6 is select in the '''Line 1''' column for each handset.
* Click on the '''Save and Apply''' button.

==Guide Links==
In the event where you need the guides directly from Grandstream, you may find the user and admin manual guides below:

User Manual : [http://www.grandstream.com/sites/default/files/Resources/DP750_DP720_User_Guide.pdf Download PDF]

Admin Manual : [http://www.grandstream.com/sites/default/files/Resources/DP750_DP720_Administration_Guide.pdf Download PDF]

Elegir servidor

2021-05-26T13:08:18Z

B13n:

[[File:ChooseServerImg.png|thumb|none|1280px|VoIP.ms servers]]

{| class="wikitable"
|+
|-
! Article in English !! Article en Français
|-
| [https://wiki.voip.ms/article/Choosing_Server English] ||
[https://wiki.voip.ms/article/Choisir_un_serveur Français]
|}

= Elegir un Servidor =

VoIP.ms le ofrece la posibilidad de conectarse a diferentes servidores, pero ¿cuál es el que debe elegir? Es común pensar que se debe elegir el servidor más cercano a su localidad, sin embargo esto no es necesario en la mayoría de las veces. Si usted está en Estados Unidos, cualquier servidor en EEUU le debe dar un buen resultado en latencia y calidad. También es de utilidad saber que hay una herramienta que le puede ayudar a seleccionar el mejor servidor a usar, este normalmente se llama "ping", el cual le provee la latencia entre usted y el servidor, así usted opcionalmente puede elegir específicamente el servidor que le provea una menor latencia.

'''Nota:''' Tenga en cuenta que es posible que algunos servidores no estén disponibles para que su número DID se utilice como POP (Punto de presencia) en la sección
"Administrar DID". Asegúrese de que su dispositivo SIP / IAX y su número de teléfono apunten al mismo servidor.

=== IPs ===

<div><ul>
<li style="display: inline-block; vertical-align:top;">
'''Canada'''
*Montreal 1, QC ('''montreal.voip.ms''') 192.175.96.73
*Montreal 2, QC ('''montreal2.voip.ms''') 192.175.96.74
*Montreal 3, QC ('''montreal3.voip.ms''') 192.175.96.68
*Montreal 4, QC ('''montreal4.voip.ms''') 67.205.74.179
*Montreal 5, QC ('''montreal5.voip.ms''') 192.175.96.69
*Montreal 6, QC ('''montreal6.voip.ms''') 192.175.96.70
*Montreal 7, QC ('''montreal7.voip.ms''') 192.175.96.71
*Montreal 8, QC ('''montreal8.voip.ms''') 192.175.96.72
*Montreal 9, QC ('''montreal9.voip.ms''') 67.205.74.184
*Montreal 10, QC ('''montreal10.voip.ms''') 67.205.74.187
*Toronto 1, ON ('''toronto.voip.ms''') 158.85.70.148
*Toronto 2, ON ('''toronto2.voip.ms''') 158.85.70.149
*Toronto 3, ON ('''toronto3.voip.ms''') 158.85.70.150
*Toronto 4, ON ('''toronto4.voip.ms''') 158.85.70.151
*Toronto 5, ON ('''toronto5.voip.ms''') 184.75.215.106
*Toronto 6, ON ('''toronto6.voip.ms''') 184.75.215.114
*Toronto 7, ON ('''toronto7.voip.ms''') 184.75.215.146
*Toronto 8, ON ('''toronto8.voip.ms''') 184.75.213.210
*Toronto 9, ON ('''toronto9.voip.ms''') 158.85.70.154
*Toronto 10, ON ('''toronto10.voip.ms''') 158.85.70.158
*Vancouver 1, BC ('''vancouver.voip.ms''') 162.213.157.220
*Vancouver 2, BC ('''vancouver2.voip.ms''') 162.213.157.117
*Vancouver 3, BC ('''vancouver3.voip.ms''') 162.213.157.82
</li>

<li style="display: inline-block; vertical-align:top;">
'''Estados Unidos'''
*Atlanta 1, GA ('''atlanta.voip.ms''') 75.127.65.130
*Atlanta 2, GA ('''atlanta2.voip.ms''') 209.217.224.50
*Chicago 1, IL ('''chicago.voip.ms''') 208.100.39.52
*Chicago 2, IL ('''chicago2.voip.ms''') 208.100.39.53
*Chicago 3, IL ('''chicago3.voip.ms''') 208.100.39.54
*Chicago 4, IL ('''chicago4.voip.ms''') 208.100.39.55
*Chicago 5, IL ('''chicago5.voip.ms''') 50.31.115.149
*Chicago 6, IL ('''chicago6.voip.ms''') 50.31.115.150
*Chicago 7, IL ('''chicago7.voip.ms''') 50.31.115.151
*Dallas, TX ('''dallas.voip.ms''') 158.85.149.162
*Dallas 2, TX ('''dallas2.voip.ms''') 158.85.149.163
*Denver 1, CO ('''denver.voip.ms''') 23.239.211.90
*Denver 2, CO ('''denver2.voip.ms''') 64.27.52.226
*Houston, TX ('''houston.voip.ms''') 205.251.137.130
*Houston 2, TX ('''houston2.voip.ms''') 74.81.95.146
*Los Angeles 1, CA ('''losangeles.voip.ms''') 96.44.149.186
*Los Angeles 2, CA ('''losangeles2.voip.ms''') 96.44.149.202
*Los Angeles 3, CA ('''losangeles3.voip.ms''') 64.188.6.162
*Los Angeles 4, CA ('''losangeles4.voip.ms''') 64.188.6.170
*New York 1, NY ('''newyork.voip.ms''') 72.251.239.196
*New York 2, NY ('''newyork2.voip.ms''') 72.251.239.205
*New York 3, NY ('''newyork3.voip.ms''') 72.251.239.206
*New York 4, NY ('''newyork4.voip.ms''') 72.251.239.207
*New York 5, NY ('''newyork5.voip.ms''') 23.29.136.28
*New York 6, NY ('''newyork6.voip.ms''') 23.29.136.29
*New York 7, NY ('''newyork7.voip.ms''') 23.29.136.38
*New York 8, NY ('''newyork8.voip.ms''') 23.29.136.40
*San Jose, CA ('''sanjose.voip.ms''') 23.246.247.146
*San Jose 2, CA ('''sanjose2.voip.ms''') 23.246.247.147
*Seattle 1, WA ('''seattle.voip.ms''') 50.23.160.53
*Seattle 2, WA ('''seattle2.voip.ms''') 50.23.149.166
*Seattle 3, WA ('''seattle3.voip.ms''') 50.23.160.54
*Tampa, FL ('''tampa.voip.ms''') 162.254.144.173
*Tampa 2, FL ('''tampa2.voip.ms''') 209.133.209.70
*Tampa 3, FL ('''tampa3.voip.ms''') 23.111.187.139
*Tampa 4, FL ('''tampa4.voip.ms''') 23.111.166.202
*Washington 1, DC ('''washington.voip.ms''') 169.62.41.187
*Washington 2, DC ('''washington2.voip.ms''') 169.62.41.189
</li>

<li style="display: inline-block; vertical-align:top;">
'''Internacional'''
*Amsterdam, NL ('''amsterdam.voip.ms''') 66.212.22.42
*London, UK ('''london.voip.ms''') 159.8.157.212
*Paris, FR ('''paris.voip.ms''') 159.8.85.180
</li>
</ul></div>

===Dominios del Servidor===

Para IOS, haga clic aquí [http://wiki.voip.ms/article/Server_Realms Server Realms] para obtener el nombre de dominio para el servidor que planea usar, esto puede diferir del nombre de dominio que se está utilizando.

= ¿Qué es un Ping? =

Ping es la herramienta estándar usada para probar la latencia (demora) en conexiones en red. Normalmente es usada para determinar si un servidor o dispositivo puede ser alcanzado a través de la red y su tiempo de latencia (tiempo que toma en enviarse un paquete a su destino y regresar a su origen) para responder.

La herramienta Ping es parte de Windows, MAC OS y Linux, también se puede encontrar en algunos ruteadores.

== ¿Cómo funciona la herramienta Ping? ==

Esta envía mensajes de petición a un una dirección de red determinada o nombres DNS en ciertos intervalos de tiempo y contabiliza el tiempo que tarda en recibirse un mensaje de respuesta. (mejor conocido como tiempo de latencia)

==¿Cómo hacer un ping en una PC?==

Hacer ping es un comando que le dice si la conexión entre su computadora y un dominio en particular está funcionando correctamente.

En Windows, seleccione Inicio> Programas> Accesorios> Símbolo del sistema. Esto le dará una ventana como la de abajo.

Ingrese la palabra ping, seguida de un espacio, luego el nombre de dominio (montreal.voip.ms) en este caso, el dominio es el nombre de nuestro servidor.

Si los resultados muestran una serie de respuestas, la conexión está funcionando. El tiempo te muestra qué tan rápida es la conexión. Si ves un error de "tiempo de espera agotado" en lugar de una respuesta, hay una falla en algún lugar entre tu computadora y el dominio.

[[File:Ping.gif|thumb|none|600px|Ping]]

== ¿Cómo enviar un ping a una MAC? ==

1- Haga click en el buscador en la barra de herramientas.

2- Haga click en aplicaciones.

3- Haga click en utilidades (usos / configuraciones).

4- Haga doble-click en utilidades de red.*

*En OS X Mavericks (10.9.x), esta aplicación de utilidad cambió de ubicación. En su lugar, inícielo desde Spotlight, presione "comando" + "barra espaciadora" o haga clic en Spotlight directamente (icono de lupa en la parte superior derecha de la pantalla), escriba "utilidad de red" y presione "regresar"

5- En la ventana de utilidades de red, haga click en el el cuadro de ping.

6- En el campo debajo "Ingresese la direccion de red para hacer ping," como montreal.voip.ms

'' Si el ping resulta no ser consistente, puede tener un problema de ''jitter'' (variación del tiempo que tardan en llegar los paquetes debido a una congestión en la red o a diferentes rutas tomadas). Para tratar este problema, puede ajustar el nivel de ''jitter'' en su configuración del dispositivo VoIP (si cuenta con esta opción). Normalmente es recomendado un ping por debajo de 150ms para tener una buena calidad de audio durante la llamada. El tiempo de latencia del servidor es importante, sin embargo hay otros factores importantes a tomar en cuenta para la calidad de las llamadas como son la pérdida de paquetes (las comunicaciones VoIP son muy sensibles a esto) y el nivel de ''jitter'' de su conexión a Internet. ''

El siguiente es el resultado de ejecutar ping con el destino losangeles.voip.ms.

#ping losangeles.voip.ms
Ping to losangeles.voip.ms [67.215.241.250] with 32 bytes de datos:
Response from 67.215.241.250: bytes=32 time=67ms TTL=52
Response from 67.215.241.250: bytes=32 time=69ms TTL=52
Response from 67.215.241.250: bytes=32 time=68ms TTL=52
Response from 67.215.241.250: bytes=32 time=67ms TTL=52
ping statistics from 67.215.241.250:
4 packets transmitted, 4 received, 0% packet lost. rtt min/avg/max/mdev = 67ms, 69ms, 67ms

Ejemplo de salida de ping en Windows:
C:\Windows\system32>ping montreal.voip.ms

Pinging montreal.voip.ms [67.205.74.184] with 32 bytes of data:
Reply from 67.205.74.184: bytes=32 time=85ms TTL=49
Reply from 67.205.74.184: bytes=32 time=86ms TTL=49
Reply from 67.205.74.184: bytes=32 time=86ms TTL=49
Reply from 67.205.74.184: bytes=32 time=85ms TTL=49

Ping statistics for 67.205.74.184:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 85ms, Maximum = 86ms, Average = 85ms

= Scripts de prueba de latencia (enviados por el usuario) =
<p> Todos los siguientes scripts fueron producidos por usuarios de voip.ms que sintieron que otros también podrían beneficiarse del resultado de sus esfuerzos. Se escribieron durante un período de años y probablemente deban ajustarse antes de usarlos, para adaptarse a los cambios en los servidores a lo largo del tiempo y los cambios en las políticas (como no probar servidores muy suscritos que no están abiertos a nuevos registros) </p>
<p> Si no está satisfecho con la seguridad de los scripts o simplemente no le gusta la forma en que aparecen sintácticamente, aún puede hacer ping manualmente a una selección de servidores y elegir un servidor en función de la mejor latencia. Los siguientes scripts son esencialmente envoltorios del comando ping que admiten listas de servidores para enviar a ping y presentar la salida en un formato legible. </p>
<p> Si cree que tiene un script más simple y limpio que funcione para otra plataforma o idioma, agréguelo a este wiki a través de un ticket de soporte.

=== Script de Bash para manejar el formato de salida de ping de Mac ===

Para hacer uso de este script (1) guárdelo como un archivo de texto sin formato (2) establezca los permisos del archivo en ejecutable (3) invoque el script
p.ej. Guarde el script a continuación usando su editor favorito como pingVoipMS.sh (2) chmod u + x pingVoipMS.sh (3) ./pingVoipMS.sh
Este es un script bash 3.x, por lo que también funciona en Linux, simplemente cambie el campo de pérdida de paquetes de ping de 7 a 6 en el ciclo final a continuación (o donde sea que el campo de pérdida esté en su formato de salida de ping). Dependiendo de su distribución, es posible que tenga que cambiar el curl a wget.

</p>
<pre>
#!/bin/bash
# Ping several servers and display Latency, Jitter and Packet Loss
# Usage: [-c <count>][-i <wait time>][-r test restricted servers][<server list file>]
#
# The optional server list text file should be formatted with one host name per line.
# The list of voip.ms servers is available at https://wiki.voip.ms/article/Choosing_Server
# If no args are supplied, this script will scrape a ping server list from voip.ms
#
USER_FILE=""
COUNT=3; INTERVAL=5; RESTRICTED=0
restrictedList=(atlanta.voip.ms chicago.voip.ms
montreal.voip.ms montreal2.voip.ms montreal3.voip.ms montreal4.voip.ms
newyork.voip.ms newyork4.voip.ms seattle.voip.ms
toronto.voip.ms toronto2.voip.ms toronto3.voip.ms toronto4.voip.ms)

# Handle any passed in script arguments
while getopts c:i:r parm
do
case $parm in
c)count_opt=$OPTARG;;
i)interval_opt=$OPTARG;;
r)RESTRICTED=1;;
*)echo -e "Invalid arg\nUsage:\t[ -c <count of ECHO_REQUESTs to Tx, default 3> ] \
\n\t[ -i <wait time (s) between datagrams, default 5> ] \
\n\t[ -r ] Include restricted servers in latency test \
\n\t[FILE <ping server list> ]";exit 1;;
esac
done

# Test if an option was specified and whether it's a +ve non-zero integer
[[ -n $count_opt && ($count_opt =~ ^[[:digit:]]+$) && $count_opt -gt 0 ]] &&
COUNT=$count_opt
[[ -n $interval_opt && ($interval_opt =~ ^[[:digit:]]+$) && $interval_opt -gt 0 ]] &&
INTERVAL=$interval_opt

shift $((OPTIND - 1))

# Validate supplied file (server list)
[[ -n $1 && ! (-f $1 && -r $1) ]] &&
{ echo "\"$1\" file does not exist or is not readable"; exit 1; }
[[ -n $1 && -f $1 && -r $1 ]] && USER_FILE="$1"

if [[ -n $USER_FILE ]]
then
# Bash 3.x in macOS does not support readarray, need to do cumbersome array loops instead
while IFS= read -r servers; do
serverList+=( "$servers" )
done < <(grep -Eo '^\b[[:alpha:]]+?[[:alnum:]]\.voip\.ms\b$' "$USER_FILE" | \
grep -v '^\s*#' | awk NF | sort)
else
# N.B. The script looks for the html boldface tags <b> </b> inside a bracket
# If the website alters and the parse fails, manually create the list and
# supply as a script arg (or perhaps update the parsing to work again :)
while IFS= read -r servers; do
serverList+=( "$servers" )
done < <(curl -sm 10 https://wiki.voip.ms/article/Choosing_Server | \
grep -E '(<b>[[:alpha:]]+?[[:alnum:]]\.voip\.ms</b>)' | \
tr "<>" " " | awk '{print $(NF-3)}' | sort )
fi

# Newer voip.ms clients can't register onto these over-subscribed servers
# Don't test the restricted list unless explicitly asked (with the -r cmd line option)
if [[ $RESTRICTED -eq 0 ]]
then
for server in "${restrictedList[@]}"
do
ix=$(printf "%s\n" "${serverList[@]}" | grep -n "^${server}" | cut -d ":" -f1)
while IFS= read -ra idx; do
keys+=( "${idx[@]}" )
done < <([[ $ix -gt 0 ]] && echo $((ix-1)))
done
for ((i=${#keys[@]} - 1; i >= 0; i--)); do unset "serverList[keys[i]]"; done
fi

if [[ ${#serverList[@]} -eq 0 ]]
then
echo "No unrestricted Voip.ms servers could be found, please supply a server list"
exit 1
fi

runTime=$((COUNT * INTERVAL * ${#serverList[@]}))

echo "PING will send $COUNT packet(s) with a wait of $INTERVAL sec(s) between each packet"
echo "Change the PING options by invoking this script with -c and/or -i, default \"-c 3 -i 5\""
echo "Over $((${#serverList[@]})) server(s) the estimated script Run Time will be $runTime seconds"
echo "================================================================"
printf "%-20s %-18s %7s %8s %6s %s\n" "VoIP Server" "IP Address" "Latency" "Jitter" "Loss" "Countdown"
echo "================================================================ (seconds)"

for myLn in "${serverList[@]}"
do
while IFS=$'\n' read -r pings; do
pingList+=( "$pings" )
printf "%-64s %5d %2d/%-2d\n" "$pings" \
"$((runTime - COUNT * INTERVAL * ${#pingList[@]}))" \
"${#pingList[@]}" "${#serverList[@]}"
done < <( ping -c "$COUNT" -i "$INTERVAL" -q "$myLn" | awk \
'
/^PING / {myH=$2}
/^PING / {
IP = substr($3,2,15)
split(IP,myIP,")") }
/packet loss/ {myPL=$7}
/min\/avg\/max/ {
split($4,myS,"/")
printf("%-20s %-18s %7.3f %8.3f %6s\n",
myH, myIP[1], myS[2], myS[4], myPL ) }
' )
done

echo "================================================================"
echo -e "\nMost appropriate server listed in order of best latency\n"
echo "================================================================"
printf "%-20s %-18s %7s %8s %6s\n" "VoIP Server" "IP Address" "Latency" "Jitter" "Loss"
echo "================================================================"
printf "%s\n" "${pingList[@]}" | LC_ALL=C sort -n -k 3,3 -k 5,5 -k 4,4 | \
awk '{printf("%s $%2d$\n",$0, NR)}'
echo "================================================================"
</pre>

=== Perl Script ===
Lista de ping de servidores voip.ms round robin con archivo csv de salida opcional.

# usage ping_voip.ms.pl <number of times> <seconds in between> <output.csv>
use Net::Ping;
use Time::HiRes;
use strict;

# input list
my @hosts = qw(
atlanta.voip.ms
atlanta2.voip.ms
chicago.voip.ms
chicago2.voip.ms
chicago3.voip.ms
chicago4.voip.ms
dallas.voip.ms
denver.voip.ms
denver2.voip.ms
houston.voip.ms
losangeles.voip.ms
losangeles2.voip.ms
newyork.voip.ms
newyork2.voip.ms
newyork3.voip.ms
newyork4.voip.ms
seattle.voip.ms
seattle2.voip.ms
seattle3.voip.ms
tampa.voip.ms
washington.voip.ms
washington2.voip.ms
montreal.voip.ms
montreal2.voip.ms
montreal3.voip.ms
montreal4.voip.ms
toronto2.voip.ms
toronto3.voip.ms
toronto4.voip.ms
toronto.voip.ms
london.voip.ms
);

$| = 1; #autoflush
# High precision syntax (requires Time::HiRes)
my $p = Net::Ping->new("icmp",1);
$p->hires();
my $max_name_length = (reverse sort { $a <=> $b } map { length($_) } @hosts)[0];
my $count = 4; # number of times to ping
my $interval = 5; # seconds between ping rounds
my $output_file = "";
my @data;

# check for arguments
my $num_args = @ARGV;
if ($num_args >= 1) {$count = $ARGV[0];}
if ($num_args >= 2) {$interval = $ARGV[1];}
if ($num_args >= 3) {$output_file = $ARGV[2];}

# check argument validity
$0 =~ /^.*\\(.*)$/;
my $script = $1;
if ($count !~ /^\d+$/ or $interval !~ /^\d+$/) {die "Usage: $script <number of rounds> <seconds between rounds> <output.csv>\n";}
if (length($output_file) > 0 and $output_file !~ /\.csv$/) {$output_file .= ".csv";}

# main loop
for my $i (1..$count)
{
sleep $interval unless $i == 1;
print "Round $i\n";
my $host_num=0;
foreach my $host (@hosts)
{
(my $ret, my $duration, my $ip) = $p->ping($host);
$ip =~ /(\d+)\.(\d+)\.(\d+)\.(\d+)/;
if ($ret)
{
printf("%*s [ip: %3s.%3s.%3s.%3s] is alive (%6.2f ms)\n", $max_name_length, $host, $1, $2, $3, $4, $duration*1000);
$data[$host_num][$i]=$duration*1000;
}
else
{
printf("%*s [ip: %3s.%3s.%3s.%3s] is dead\n", $max_name_length, $host, $1, $2, $3, $4);
}
$host_num++;
}
print "\n";
}
$p->close();

# if output file name given
if (length($output_file)>0)
{
# print output to file
open FILE, ">$output_file" or die "$!\n";

# print column headers
print FILE "Server\\Round";
for my $i (1..$count)
{
print FILE ", $i";
}
print FILE ", Average\n";

# print data
my $i = 0;
foreach my $host (@hosts)
{
print FILE "$host";
my $sum = 0;
for my $j (1..$count)
{
$sum += $data[$i][$j];
printf FILE ", %8.4f",$data[$i][$j];
}
printf FILE ", %8.4f\n",$sum/$count;
$i++;
}

close FILE;
print "Data written to $output_file\n";
}

# print summary to screen
my $i = 0;
printf("%-*s Average (ms)\n", $max_name_length, "Server");
foreach my $host (@hosts)
{
my $sum = 0;
for my $j (1..$count)
{
$sum += $data[$i][$j];
}
printf("%-*s %8.4f\n", $max_name_length+1, $host, $sum/$count);
$i++;
}

Salidas:
Round 1
atlanta.voip.ms [ip: 174. 34.146.162] is alive ( 88.97 ms)
atlanta2.voip.ms [ip: 72. 9.246.170] is alive ( 92.99 ms)
chicago.voip.ms [ip: 208.100. 39. 52] is alive ( 49.70 ms)
chicago2.voip.ms [ip: 208.100. 39. 53] is alive ( 59.76 ms)
chicago3.voip.ms [ip: 208.100. 39. 54] is alive ( 59.53 ms)
chicago4.voip.ms [ip: 208.100. 39. 55] is alive ( 49.73 ms)
dallas.voip.ms [ip: 74. 54. 54.178] is alive ( 94.99 ms)
denver.voip.ms [ip: 173.248.161. 90] is alive ( 94.05 ms)
denver2.voip.ms [ip: 173.248.159.210] is alive ( 85.13 ms)
houston.voip.ms [ip: 209. 62. 1. 2] is alive (102.87 ms)
losangeles.voip.ms [ip: 96. 44.149.186] is alive ( 64.92 ms)
losangeles2.voip.ms [ip: 96. 44.149.202] is alive ( 63.41 ms)
newyork.voip.ms [ip: 74. 63. 41.218] is alive (131.75 ms)
newyork2.voip.ms [ip: 107. 6. 67.236] is alive (120.64 ms)
newyork3.voip.ms [ip: 107. 6. 67.237] is alive (120.49 ms)
newyork4.voip.ms [ip: 107. 6. 67.238] is alive (111.43 ms)
seattle.voip.ms [ip: 50. 23.160. 50] is alive ( 94.25 ms)
seattle2.voip.ms [ip: 50. 23.160. 51] is alive ( 95.86 ms)
seattle3.voip.ms [ip: 50. 23.160. 52] is alive ( 90.85 ms)
tampa.voip.ms [ip: 68.233.226. 97] is alive (123.29 ms)
washington.voip.ms [ip: 208. 43.234.226] is alive ( 98.71 ms)
washington2.voip.ms [ip: 208. 43.234.227] is alive (101.19 ms)
montreal.voip.ms [ip: 67.205. 74.184] is alive ( 81.82 ms)
montreal2.voip.ms [ip: 67.205. 74.187] is alive ( 86.13 ms)
montreal3.voip.ms [ip: 72. 55.168. 18] is alive ( 77.09 ms)
montreal4.voip.ms [ip: 67.205. 74.179] is alive ( 96.18 ms)
toronto2.voip.ms [ip: 184. 75.215.114] is alive (103.70 ms)
toronto3.voip.ms [ip: 184. 75.215.146] is alive (131.27 ms)
toronto4.voip.ms [ip: 184. 75.213.210] is alive (125.13 ms)
toronto.voip.ms [ip: 184. 75.215.106] is alive (103.26 ms)
london.voip.ms [ip: 5. 77. 36.136] is alive (152.77 ms)

Round 2
atlanta.voip.ms [ip: 174. 34.146.162] is alive ( 88.14 ms)
atlanta2.voip.ms [ip: 72. 9.246.170] is alive ( 92.86 ms)
chicago.voip.ms [ip: 208.100. 39. 52] is alive ( 50.03 ms)
chicago2.voip.ms [ip: 208.100. 39. 53] is alive ( 59.44 ms)
chicago3.voip.ms [ip: 208.100. 39. 54] is alive ( 59.33 ms)
chicago4.voip.ms [ip: 208.100. 39. 55] is alive ( 50.22 ms)
dallas.voip.ms [ip: 74. 54. 54.178] is alive ( 95.58 ms)
denver.voip.ms [ip: 173.248.161. 90] is alive ( 95.94 ms)
denver2.voip.ms [ip: 173.248.159.210] is alive ( 85.29 ms)
houston.voip.ms [ip: 209. 62. 1. 2] is alive (102.73 ms)
losangeles.voip.ms [ip: 96. 44.149.186] is alive ( 65.59 ms)
losangeles2.voip.ms [ip: 96. 44.149.202] is alive ( 64.27 ms)
newyork.voip.ms [ip: 74. 63. 41.218] is alive (112.74 ms)
newyork2.voip.ms [ip: 107. 6. 67.236] is alive (121.22 ms)
newyork3.voip.ms [ip: 107. 6. 67.237] is alive (121.34 ms)
newyork4.voip.ms [ip: 107. 6. 67.238] is alive (110.75 ms)
seattle.voip.ms [ip: 50. 23.160. 50] is alive ( 94.06 ms)
seattle2.voip.ms [ip: 50. 23.160. 51] is alive ( 95.33 ms)
seattle3.voip.ms [ip: 50. 23.160. 52] is alive ( 91.58 ms)
tampa.voip.ms [ip: 68.233.226. 97] is alive (122.94 ms)
washington.voip.ms [ip: 208. 43.234.226] is alive ( 98.28 ms)
washington2.voip.ms [ip: 208. 43.234.227] is alive (101.40 ms)
montreal.voip.ms [ip: 67.205. 74.184] is alive ( 81.91 ms)
montreal2.voip.ms [ip: 67.205. 74.187] is alive ( 85.64 ms)
montreal3.voip.ms [ip: 72. 55.168. 18] is alive ( 75.15 ms)
montreal4.voip.ms [ip: 67.205. 74.179] is alive ( 96.79 ms)
toronto2.voip.ms [ip: 184. 75.215.114] is alive (103.10 ms)
toronto3.voip.ms [ip: 184. 75.215.146] is alive (150.85 ms)
toronto4.voip.ms [ip: 184. 75.213.210] is alive (138.40 ms)
toronto.voip.ms [ip: 184. 75.215.106] is alive (103.45 ms)
london.voip.ms [ip: 5. 77. 36.136] is alive (170.79 ms)

Round 3
atlanta.voip.ms [ip: 174. 34.146.162] is alive ( 88.76 ms)
atlanta2.voip.ms [ip: 72. 9.246.170] is alive ( 92.86 ms)
chicago.voip.ms [ip: 208.100. 39. 52] is alive ( 49.65 ms)
chicago2.voip.ms [ip: 208.100. 39. 53] is alive ( 60.01 ms)
chicago3.voip.ms [ip: 208.100. 39. 54] is alive ( 59.05 ms)
chicago4.voip.ms [ip: 208.100. 39. 55] is alive ( 49.53 ms)
dallas.voip.ms [ip: 74. 54. 54.178] is alive ( 95.82 ms)
denver.voip.ms [ip: 173.248.161. 90] is alive ( 95.02 ms)
denver2.voip.ms [ip: 173.248.159.210] is alive ( 85.60 ms)
houston.voip.ms [ip: 209. 62. 1. 2] is alive (103.35 ms)
losangeles.voip.ms [ip: 96. 44.149.186] is alive ( 65.79 ms)
losangeles2.voip.ms [ip: 96. 44.149.202] is alive ( 64.05 ms)
newyork.voip.ms [ip: 74. 63. 41.218] is alive (113.01 ms)
newyork2.voip.ms [ip: 107. 6. 67.236] is alive (121.41 ms)
newyork3.voip.ms [ip: 107. 6. 67.237] is alive (122.23 ms)
newyork4.voip.ms [ip: 107. 6. 67.238] is alive (110.62 ms)
seattle.voip.ms [ip: 50. 23.160. 50] is alive ( 93.65 ms)
seattle2.voip.ms [ip: 50. 23.160. 51] is alive ( 95.19 ms)
seattle3.voip.ms [ip: 50. 23.160. 52] is alive ( 90.75 ms)
tampa.voip.ms [ip: 68.233.226. 97] is alive (125.12 ms)
washington.voip.ms [ip: 208. 43.234.226] is alive ( 98.19 ms)
washington2.voip.ms [ip: 208. 43.234.227] is alive (101.98 ms)
montreal.voip.ms [ip: 67.205. 74.184] is alive ( 80.16 ms)
montreal2.voip.ms [ip: 67.205. 74.187] is alive ( 87.16 ms)
montreal3.voip.ms [ip: 72. 55.168. 18] is alive ( 76.54 ms)
montreal4.voip.ms [ip: 67.205. 74.179] is alive ( 97.51 ms)
toronto2.voip.ms [ip: 184. 75.215.114] is alive (104.18 ms)
toronto3.voip.ms [ip: 184. 75.215.146] is alive (142.81 ms)
toronto4.voip.ms [ip: 184. 75.213.210] is alive (138.95 ms)
toronto.voip.ms [ip: 184. 75.215.106] is alive (103.78 ms)
london.voip.ms [ip: 5. 77. 36.136] is alive (153.14 ms)

Round 4
atlanta.voip.ms [ip: 174. 34.146.162] is alive ( 89.19 ms)
atlanta2.voip.ms [ip: 72. 9.246.170] is alive ( 92.98 ms)
chicago.voip.ms [ip: 208.100. 39. 52] is alive ( 49.21 ms)
chicago2.voip.ms [ip: 208.100. 39. 53] is alive ( 60.50 ms)
chicago3.voip.ms [ip: 208.100. 39. 54] is alive ( 59.68 ms)
chicago4.voip.ms [ip: 208.100. 39. 55] is alive ( 50.18 ms)
dallas.voip.ms [ip: 74. 54. 54.178] is alive ( 93.93 ms)
denver.voip.ms [ip: 173.248.161. 90] is alive ( 94.22 ms)
denver2.voip.ms [ip: 173.248.159.210] is alive ( 85.10 ms)
houston.voip.ms [ip: 209. 62. 1. 2] is alive (103.67 ms)
losangeles.voip.ms [ip: 96. 44.149.186] is alive ( 65.58 ms)
losangeles2.voip.ms [ip: 96. 44.149.202] is alive ( 63.60 ms)
newyork.voip.ms [ip: 74. 63. 41.218] is alive (114.76 ms)
newyork2.voip.ms [ip: 107. 6. 67.236] is alive (120.44 ms)
newyork3.voip.ms [ip: 107. 6. 67.237] is alive (121.05 ms)
newyork4.voip.ms [ip: 107. 6. 67.238] is alive (110.51 ms)
seattle.voip.ms [ip: 50. 23.160. 50] is alive ( 94.04 ms)
seattle2.voip.ms [ip: 50. 23.160. 51] is alive ( 96.92 ms)
seattle3.voip.ms [ip: 50. 23.160. 52] is alive ( 91.23 ms)
tampa.voip.ms [ip: 68.233.226. 97] is alive (123.28 ms)
washington.voip.ms [ip: 208. 43.234.226] is alive ( 98.45 ms)
washington2.voip.ms [ip: 208. 43.234.227] is alive (100.94 ms)
montreal.voip.ms [ip: 67.205. 74.184] is alive ( 82.33 ms)
montreal2.voip.ms [ip: 67.205. 74.187] is alive ( 85.02 ms)
montreal3.voip.ms [ip: 72. 55.168. 18] is alive ( 76.85 ms)
montreal4.voip.ms [ip: 67.205. 74.179] is alive ( 96.32 ms)
toronto2.voip.ms [ip: 184. 75.215.114] is alive (104.22 ms)
toronto3.voip.ms [ip: 184. 75.215.146] is alive (148.33 ms)
toronto4.voip.ms [ip: 184. 75.213.210] is alive (141.61 ms)
toronto.voip.ms [ip: 184. 75.215.106] is alive (105.91 ms)
london.voip.ms [ip: 5. 77. 36.136] is alive (152.85 ms)

Server Average (ms)
atlanta.voip.ms 88.7630
atlanta2.voip.ms 92.9233
chicago.voip.ms 49.6477
chicago2.voip.ms 59.9305
chicago3.voip.ms 59.3972
chicago4.voip.ms 49.9152
dallas.voip.ms 95.0790
denver.voip.ms 94.8077
denver2.voip.ms 85.2797
houston.voip.ms 103.1562
losangeles.voip.ms 65.4693
losangeles2.voip.ms 63.8347
newyork.voip.ms 118.0643
newyork2.voip.ms 120.9265
newyork3.voip.ms 121.2778
newyork4.voip.ms 110.8275
seattle.voip.ms 93.9993
seattle2.voip.ms 95.8267
seattle3.voip.ms 91.1035
tampa.voip.ms 123.6570
washington.voip.ms 98.4065
washington2.voip.ms 101.3774
montreal.voip.ms 81.5525
montreal2.voip.ms 85.9863
montreal3.voip.ms 76.4058
montreal4.voip.ms 96.7013
toronto2.voip.ms 103.7986
toronto3.voip.ms 143.3156
toronto4.voip.ms 136.0254
toronto.voip.ms 104.1012
london.voip.ms 157.3885

=== Powershell ===

Diciembre 2017 - Un problema en el codigo del dominio washington2.voip.ms lo mostraba como el mejor servidor, esto fue corregido.
<pre>
# Usage: Copy and paste the following code into a powershell window
# To run it from a command prompt, save this file with extension ps1.
# Then run Powershell.exe -file "pathtothisscript.ps1"
Clear-Variable best* -Scope Global #Clear the best* variables in case you run it more than once...
#Get the list of servers into an array
$Servers =
@("amsterdam.voip.ms","atlanta.voip.ms","atlanta2.voip.ms","chicago.voip.ms","chicago2.voip.ms","chicago3.voip.ms",
"chicago4.voip.ms","dallas.voip.ms","dallas2.voip.ms","denver.voip.ms","denver2.voip.ms","houston.voip.ms",
"houston2.voip.ms","london.voip.ms","losangeles.voip.ms","losangeles2.voip.ms","montreal.voip.ms",
"montreal2.voip.ms","montreal3.voip.ms","montreal4.voip.ms","montreal5.voip.ms","montreal6.voip.ms","montreal7.voip.ms",
"montreal8.voip.ms","newyork.voip.ms","newyork2.voip.ms","newyork3.voip.ms","newyork4.voip.ms","newyork5.voip.ms",
"newyork6.voip.ms","newyork7.voip.ms","newyork8.voip.ms","paris.voip.ms","sanjose.voip.ms","sanjose2.voip.ms",
"seattle.voip.ms","seattle2.voip.ms","seattle3.voip.ms","tampa.voip.ms","tampa2.voip.ms","toronto.voip.ms",
"toronto2.voip.ms","toronto3.voip.ms","toronto4.voip.ms","toronto5.voip.ms","toronto6.voip.ms","toronto7.voip.ms",
"toronto8.voip.ms","vancouver.voip.ms","vancouver2.voip.ms","washington.voip.ms","washington2.voip.ms")
$k = 0 #Counting variable so we know what server number we are testing
#num of servers to test
$servercount = $servers.length
#Do the following code for each server in our array
ForEach($server in $servers)
{
#Add one to the counting variable....we are on server #1...then server 2, then server 3 etc...
$k++
#Update the progress bar
Write-Progress -Activity "Testing Server: ${server}" -status "Testing Server $k out of $servercount" -percentComplete ($k / $servercount*100)
#Counting variable for number of times we tried to ping a given server
$i = 0
Do{
#assume a failure
$pingsuccess = $false
$i++ #Add one to the counting variable.....1st try....2nd try....3rd try etc...
Try{
#Try to ping
$currentping = (test-connection $server -count 1 -ErrorAction Stop).responsetime
#If success full, set success variable
$pingsuccess = $true
}
#Catch the failure and set the success variable to false
Catch {
$pingsuccess = $false
}
}
#Try everything between Do and While up to 5 times, or while $pingsuccess is not true
While($pingsuccess -eq $false -and $i -le 5)
#Compare the last ping test with the best known ping test....if there is no known best ping test, assume this one is the best $bestping = $currentping
If($pingsuccess -and ($currentping -lt $bestping -or (!($bestping)))){
#If this is the best ping...save it
$bestserver = $server #Save the best server
$bestping = $currentping #Save the best ping results
}
write-host "tested: $server at $currentping ms after $i attempts" #write the results of the test for this server
}
write-host "`r`n The server with the best ping is: $bestserver at $bestping ms`r`n" #write the end result
Pause
</pre>

=== Linux Shell Script ===
Hace ping a varios servidores voip.ms

#!/bin/sh
# Ping several servers and display Latency, Jitter and Packet Loss
#
# First, create a text file with all servers you want to ping - one host name per line.
# The list of voip.ms servers is available at http://wiki.voip.ms/article/Choosing_Server
myHF="voip_ping_hosts.txt"
# Sample file:
# toronto.voip.ms
# montreal.voip.ms
# seattle.voip.ms
# chicago.voip.ms
# newyork.voip.ms
#
echo "============================================"
printf "%-20s %7s %8s %6s\n" "VoIP Server" "Latency" "Jitter" "Loss"
echo "============================================"
cat ${myHF} |\
while read myLn
do
ping -c 3 -i 5 -q $myLn |\
awk '/^PING / {myH=$2}
/packet loss/ {myPL=$6}
/min\/avg\/max/ {
split($4,myS,"/")
printf( "%-20s %3.1f %1.3f %4s\n", myH, myS[2], myS[4], myPL)
}'
done
echo "============================================"

Salidas:

============================================
VoIP Server Latency Jitter Loss
============================================
toronto.voip.ms 68.3 0.439 0%
montreal.voip.ms 89.6 0.197 0%
seattle.voip.ms 71.2 0.387 0%
chicago.voip.ms 71.6 0.084 0%
newyork.voip.ms 79.1 0.411 0%
============================================

= La Latencia y su importancia =

La latencia es muy importante para Voip, esto determinará el tiempo que tardará la transmisión del paquete de datos en llegar al destino. Una latencia alta provocará un retraso y ecos en la comunicación.

La latencia se mide en milisegundos (ms) Por ejemplo: una latencia de 150 ms es apenas perceptible, por lo que es aceptable. Más alto que eso, la calidad comienza a sufrir. Cuando supera los 300 ms, se vuelve inaceptable.

[[category:Guías]]

Choisir un serveur

2021-05-26T13:07:56Z

B13n:

[[File:ChooseServerImg.png|thumb|none|1280px|VoIP.ms servers]]

{| class="wikitable"
|+
|-
! Article in English !! Artículo en Español
|-
| [https://wiki.voip.ms/article/Choosing_Server English] || [https://wiki.voip.ms/article/Elegir_servidor Español]
|}

= Choisir un serveur =

[http://www.voip.ms VoIP.ms] propose de nombreux serveurs PoP différents, mais lequel choisir? Une des conceptions erronées est que vous devriez choisir le serveur PoP le plus proche de votre emplacement, mais cela n'est pas nécessaire la plupart du temps.

Par exemple, si vous êtes aux États-Unis, l'un des serveurs américains fournira une très bonne latence et une très bonne qualité de service. Le serveur le plus récent d'une ville est indiqué par le numéro le plus élevé associé au nom du serveur, car ils sont classés par ordre croissant.

Il convient également de noter qu'il existe un outil réseau qui vous aidera à choisir le serveur que vous souhaitez utiliser, généralement appelé "ping", qui vous fournira la latence entre vous et le serveur. Par conséquent, le serveur qui vous offre le moins de latence doit être utilisé.

'''Note:''' Veuillez garder à l'esprit que certains serveurs peuvent ne pas être disponibles pour que votre numéro DID soit utilisé comme POP (point de présence) dans la section
'''Gestion des DID'''. Assurez-vous aussi que votre appareil SIP/IAX et votre numéro DID pointent vers le même serveur POP.

=== Adresses IPs ===

<div><ul>
<li style="display: inline-block; vertical-align:top;">
'''Canada'''
*Montreal 1, QC ('''montreal.voip.ms''') 192.175.96.73
*Montreal 2, QC ('''montreal2.voip.ms''') 192.175.96.74
*Montreal 3, QC ('''montreal3.voip.ms''') 192.175.96.68
*Montreal 4, QC ('''montreal4.voip.ms''') 67.205.74.179
*Montreal 5, QC ('''montreal5.voip.ms''') 192.175.96.69
*Montreal 6, QC ('''montreal6.voip.ms''') 192.175.96.70
*Montreal 7, QC ('''montreal7.voip.ms''') 192.175.96.71
*Montreal 8, QC ('''montreal8.voip.ms''') 192.175.96.72
*Montreal 9, QC ('''montreal9.voip.ms''') 67.205.74.184
*Montreal 10, QC ('''montreal10.voip.ms''') 67.205.74.187
*Toronto 1, ON ('''toronto.voip.ms''') 158.85.70.148
*Toronto 2, ON ('''toronto2.voip.ms''') 158.85.70.149
*Toronto 3, ON ('''toronto3.voip.ms''') 158.85.70.150
*Toronto 4, ON ('''toronto4.voip.ms''') 158.85.70.151
*Toronto 5, ON ('''toronto5.voip.ms''') 184.75.215.106
*Toronto 6, ON ('''toronto6.voip.ms''') 184.75.215.114
*Toronto 7, ON ('''toronto7.voip.ms''') 184.75.215.146
*Toronto 8, ON ('''toronto8.voip.ms''') 184.75.213.210
*Toronto 9, ON ('''toronto9.voip.ms''') 158.85.70.154
*Toronto 10, ON ('''toronto10.voip.ms''') 158.85.70.158
*Vancouver 1, BC ('''vancouver.voip.ms''') 162.213.157.220
*Vancouver 2, BC ('''vancouver2.voip.ms''') 162.213.157.117
*Vancouver 3, BC ('''vancouver3.voip.ms''') 162.213.157.82
</li>

<li style="display: inline-block; vertical-align:top;">
'''États-Unis'''
*Atlanta 1, GA ('''atlanta.voip.ms''') 75.127.65.130
*Atlanta 2, GA ('''atlanta2.voip.ms''') 209.217.224.50
*Chicago 1, IL ('''chicago.voip.ms''') 69.162.175.27
*Chicago 2, IL ('''chicago2.voip.ms''') 69.162.175.28
*Chicago 3, IL ('''chicago3.voip.ms''') 69.162.175.29
*Chicago 4, IL ('''chicago4.voip.ms''') 208.100.39.55
*Chicago 5, IL ('''chicago5.voip.ms''') 50.31.115.149
*Chicago 6, IL ('''chicago6.voip.ms''') 50.31.115.150
*Chicago 7, IL ('''chicago7.voip.ms''') 50.31.115.151
*Dallas, TX ('''dallas.voip.ms''') 158.85.149.162
*Dallas 2, TX ('''dallas2.voip.ms''') 158.85.149.163
*Denver 1, CO ('''denver.voip.ms''') 23.239.211.90
*Denver 2, CO ('''denver2.voip.ms''') 64.27.52.226
*Houston, TX ('''houston.voip.ms''') 205.251.137.130
*Houston 2, TX ('''houston2.voip.ms''') 74.81.95.146
*Los Angeles 1, CA ('''losangeles.voip.ms''') 96.44.149.186
*Los Angeles 2, CA ('''losangeles2.voip.ms''') 96.44.149.202
*Los Angeles 3, CA ('''losangeles3.voip.ms''') 64.188.6.162
*Los Angeles 4, CA ('''losangeles4.voip.ms''') 64.188.6.170
*New York 1, NY ('''newyork.voip.ms''') 72.251.239.196
*New York 2, NY ('''newyork2.voip.ms''') 72.251.239.205
*New York 3, NY ('''newyork3.voip.ms''') 72.251.239.206
*New York 4, NY ('''newyork4.voip.ms''') 72.251.239.207
*New York 5, NY ('''newyork5.voip.ms''') 23.29.136.28
*New York 6, NY ('''newyork6.voip.ms''') 23.29.136.29
*New York 7, NY ('''newyork7.voip.ms''') 23.29.136.38
*New York 8, NY ('''newyork8.voip.ms''') 23.29.136.40
*San Jose, CA ('''sanjose.voip.ms''') 23.246.247.146
*San Jose 2, CA ('''sanjose2.voip.ms''') 23.246.247.147
*Seattle 1, WA ('''seattle.voip.ms''') 50.23.160.53
*Seattle 2, WA ('''seattle2.voip.ms''') 50.23.149.166
*Seattle 3, WA ('''seattle3.voip.ms''') 50.23.160.54
*Tampa, FL ('''tampa.voip.ms''') 162.254.144.173
*Tampa 2, FL ('''tampa2.voip.ms''') 209.133.209.70
*Tampa 3, FL ('''tampa3.voip.ms''') 23.111.187.139
*Tampa 4, FL ('''tampa4.voip.ms''') 23.111.166.202
*Washington 1, DC ('''washington.voip.ms''') 169.62.41.187
*Washington 2, DC ('''washington2.voip.ms''') 169.62.41.189
</li>

<li style="display: inline-block; vertical-align:top;">
'''Internationaux'''
*Amsterdam, NL ('''amsterdam.voip.ms''') 66.212.22.42
*London, UK ('''london.voip.ms''') 159.8.157.212
*Paris, FR ('''paris.voip.ms''') 159.8.85.180
</li>
</ul></div>

=== Serveur Realms ===

Pour IOS, s'il vous plaît utiliser le lien [http://wiki.voip.ms/article/Server_Realms Serveur Realms] pour obtenir le nom du serveur Realms que vous prévoyez utiliser, cela peut être différent du nom de domaine utilisé.

= Qu'est-ce qu'un ping? =

Un Ping est un outil standard utilisé pour tester les connexions réseau. Il est principalement utilisé pour déterminer si un serveur ou un périphérique peut être atteint sur le réseau et la latence de la réponse (le temps qu'il faut pour envoyer un paquet à la destination souhaitée et pour qu'il vous revienne sur votre ordinateur).

Les outils Ping font partie de Windows, Mac OS X et Linux ainsi que de certains routeurs.

== Comment fonctionne le ping? ==

Il envoie des messages de demande à une adresse réseau cible ou à des noms DNS à intervalle régulier et mesure le temps nécessaire à un message pour s'y rendre et revenir (mieux connu sous le nom de latence).

= La latence et son importance =

La latence est très importante pour la Voix sur IP, cela déterminera le temps nécessaire à la transmission du paquet de données pour atteindre la destination. Une latence élevée entraînera un retard et des échos dans la communication.

La latence se mesure en millisecondes (ms) Par exemple: une latence de 150ms est à peine perceptible, donc acceptable. Avec une valeur plus haute que celle-ci, la qualité de l'appel commence à être affectée. Lorsqu'elle dépasse 300 ms, cela devient inacceptable.

[[category:guides]]

Choosing Server

2021-05-26T13:07:07Z

B13n:

[[File:ChooseServerImg.png|thumb|none|1280px|VoIP.ms servers]]

{| class="wikitable"
|+
|-
! Article en Français !! Artículo en Español
|-
| [https://wiki.voip.ms/article/Choisir_un_serveur Français] ||
[https://wiki.voip.ms/article/Elegir_servidor Español]
|}

= Choosing a Server =

[http://www.voip.ms VoIP.ms] offers many different servers, but which one should you choose? One misconception is that you should pick the closest to your location, however this is not needed most of the time. For example, if you are in the USA, any of the US servers will provide a really good latency and service quality. The newest server within a city is indicated with the highest number attached to the name, as they are classified in ascending order. Also worth noting is that there is a network tool that will help you when deciding which server you want to use, generally named a "ping", which will provide you the latency between you and the server. Therefore the server which provides you less latency should be used.

'''Note:''' Please bear in mind that some servers might not be available for your DID number to be used as POP (Point of presence) at the ''Manage DIDs'' section.
Make sure that your SIP/IAX device and your phone number are pointing to the same server.

=== IPs ===

<div><ul>
<li style="display: inline-block; vertical-align:top;">
'''Canada'''
*Montreal 1, QC ('''montreal.voip.ms''') 192.175.96.73
*Montreal 2, QC ('''montreal2.voip.ms''') 192.175.96.74
*Montreal 3, QC ('''montreal3.voip.ms''') 192.175.96.68
*Montreal 4, QC ('''montreal4.voip.ms''') 67.205.74.179
*Montreal 5, QC ('''montreal5.voip.ms''') 192.175.96.69
*Montreal 6, QC ('''montreal6.voip.ms''') 192.175.96.70
*Montreal 7, QC ('''montreal7.voip.ms''') 192.175.96.71
*Montreal 8, QC ('''montreal8.voip.ms''') 192.175.96.72
*Montreal 9, QC ('''montreal9.voip.ms''') 67.205.74.184
*Montreal 10, QC ('''montreal10.voip.ms''') 67.205.74.187
*Toronto 1, ON ('''toronto.voip.ms''') 158.85.70.148
*Toronto 2, ON ('''toronto2.voip.ms''') 158.85.70.149
*Toronto 3, ON ('''toronto3.voip.ms''') 158.85.70.150
*Toronto 4, ON ('''toronto4.voip.ms''') 158.85.70.151
*Toronto 5, ON ('''toronto5.voip.ms''') 184.75.215.106
*Toronto 6, ON ('''toronto6.voip.ms''') 184.75.215.114
*Toronto 7, ON ('''toronto7.voip.ms''') 184.75.215.146
*Toronto 8, ON ('''toronto8.voip.ms''') 184.75.213.210
*Toronto 9, ON ('''toronto9.voip.ms''') 158.85.70.154
*Toronto 10, ON ('''toronto10.voip.ms''') 158.85.70.158
*Vancouver 1, BC ('''vancouver.voip.ms''') 162.213.157.220
*Vancouver 2, BC ('''vancouver2.voip.ms''') 162.213.157.117
*Vancouver 3, BC ('''vancouver3.voip.ms''') 162.213.157.82
</li>

<li style="display: inline-block; vertical-align:top;">
'''United States'''
*Atlanta 1, GA ('''atlanta.voip.ms''') 75.127.65.130
*Atlanta 2, GA ('''atlanta2.voip.ms''') 209.217.224.50
*Chicago 1, IL ('''chicago.voip.ms''') 69.162.175.27
*Chicago 2, IL ('''chicago2.voip.ms''') 69.162.175.28
*Chicago 3, IL ('''chicago3.voip.ms''') 69.162.175.29
*Chicago 4, IL ('''chicago4.voip.ms''') 208.100.39.55
*Chicago 5, IL ('''chicago5.voip.ms''') 50.31.115.149
*Chicago 6, IL ('''chicago6.voip.ms''') 50.31.115.150
*Chicago 7, IL ('''chicago7.voip.ms''') 50.31.115.151
*Dallas, TX ('''dallas.voip.ms''') 158.85.149.162
*Dallas 2, TX ('''dallas2.voip.ms''') 158.85.149.163
*Denver 1, CO ('''denver.voip.ms''') 23.239.211.90
*Denver 2, CO ('''denver2.voip.ms''') 64.27.52.226
*Houston, TX ('''houston.voip.ms''') 205.251.137.130
*Houston 2, TX ('''houston2.voip.ms''') 74.81.95.146
*Los Angeles 1, CA ('''losangeles.voip.ms''') 96.44.149.186
*Los Angeles 2, CA ('''losangeles2.voip.ms''') 96.44.149.202
*Los Angeles 3, CA ('''losangeles3.voip.ms''') 64.188.6.162
*Los Angeles 4, CA ('''losangeles4.voip.ms''') 64.188.6.170
*New York 1, NY ('''newyork.voip.ms''') 72.251.239.196
*New York 2, NY ('''newyork2.voip.ms''') 72.251.239.205
*New York 3, NY ('''newyork3.voip.ms''') 72.251.239.206
*New York 4, NY ('''newyork4.voip.ms''') 72.251.239.207
*New York 5, NY ('''newyork5.voip.ms''') 23.29.136.28
*New York 6, NY ('''newyork6.voip.ms''') 23.29.136.29
*New York 7, NY ('''newyork7.voip.ms''') 23.29.136.38
*New York 8, NY ('''newyork8.voip.ms''') 23.29.136.40
*San Jose, CA ('''sanjose.voip.ms''') 23.246.247.146
*San Jose 2, CA ('''sanjose2.voip.ms''') 23.246.247.147
*Seattle 1, WA ('''seattle.voip.ms''') 104.129.57.250
*Seattle 2, WA ('''seattle2.voip.ms''') 173.205.93.122
*Seattle 3, WA ('''seattle3.voip.ms''') 173.205.93.226
*Tampa, FL ('''tampa.voip.ms''') 162.254.144.173
*Tampa 2, FL ('''tampa2.voip.ms''') 209.133.209.70
*Tampa 3, FL ('''tampa3.voip.ms''') 23.111.187.139
*Tampa 4, FL ('''tampa4.voip.ms''') 23.111.166.202
*Washington 1, DC ('''washington.voip.ms''') 169.62.41.189
*Washington 2, DC ('''washington2.voip.ms''') 169.62.41.187
</li>

<li style="display: inline-block; vertical-align:top;">
'''International'''
*Amsterdam, NL ('''amsterdam.voip.ms''') 66.212.22.42
*London, UK ('''london.voip.ms''') 159.8.157.212
*Sydney, AU ('''sydney1.voip.ms''') 168.1.73.84
*Paris, FR ('''paris.voip.ms''') 159.8.85.180
</li>
</ul></div>

===Server Realms===

For IOS, Please click here [http://wiki.voip.ms/article/Server_Realms Server Realms] to get the Realm Name for the server you plan on using, this can differ from the Domain Name being used.

= What is a Ping? =

Ping is a standard tool used to test network connections. It is mostly used to determine if a server or device can be reached across the network and the latency of the response(the time it takes to send a packet to the destination and for it to return to your computer).

Ping tools are part of Windows, Mac OS X and Linux as well as some routers.

== How does the ping work? ==

It sends request messages to a target network address or DNS names at periodic intervals and measures the time it takes for a response message to arrive and return(better known as latency).

==How to ping on a PC==

Pinging is a command which tells you if the connection between your computer and a particular domain is working correctly.

In Windows, select Start > Programs > Accessories > Command Prompt. This will give you a window like the one below.

Enter the word ping, followed by a space, then the domain name.(montreal.voip.ms) in this case domain is our server name.

If the results show a series of replies, the connection is working. The time shows you how fast the connection is. If you see a "timed out" error instead of a reply, there is a breakdown somewhere between your computer and the domain.

[[File:Ping.gif|thumb|none|600px|Ping]]

==How to ping on a Mac Computer==

1- Click on Finder in the dock.

2- Click on Applications.

3- Click on Utilities.

4- Double-click on Network Utility. *

* In OS X Mavericks (10.9.x) this utility app changed location. Launch it from spotlight instead, either press "command"+"space bar" or click on spotlight directly (magnifying glass icon at top right of screen), type "network utility" and hit "return"

5- In the Network Utility window, click on the Ping tab

6- In the field under "Please enter the network address to ping," like montreal.voip.ms

''If pings results are not consistent, you may have an issue with Jitter. You can work on this issue by adjusting the "Network Jitter Level" setting on your VoIP device. Usually a ping of under 150 ms is recommended in order to have good quality. The latency time to the server is important, however there are also other factors that could affect the quality of the calls such as packet loss (VoIP communications are very sensitive to this), and the Jitter level of your Internet connection.''

The following is the output of running ping with the target losangeles.voip.ms.

#ping losangeles.voip.ms
Ping to losangeles.voip.ms [67.215.241.250] with 32 bytes de datos:
Response from 67.215.241.250: bytes=32 time=67ms TTL=52
Response from 67.215.241.250: bytes=32 time=69ms TTL=52
Response from 67.215.241.250: bytes=32 time=68ms TTL=52
Response from 67.215.241.250: bytes=32 time=67ms TTL=52
ping statistics from 67.215.241.250:
4 packets transmitted, 4 received, 0% packet lost. rtt min/avg/max/mdev = 67ms, 69ms, 67ms

Sample ping output in windows:
C:\Windows\system32>ping montreal.voip.ms

Pinging montreal.voip.ms [67.205.74.184] with 32 bytes of data:
Reply from 67.205.74.184: bytes=32 time=85ms TTL=49
Reply from 67.205.74.184: bytes=32 time=86ms TTL=49
Reply from 67.205.74.184: bytes=32 time=86ms TTL=49
Reply from 67.205.74.184: bytes=32 time=85ms TTL=49

Ping statistics for 67.205.74.184:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 85ms, Maximum = 86ms, Average = 85ms

= Latency Testing Scripts (User Submitted) =
<p>All the following scripts were produced by voip.ms users who felt others might also benefit from the output of their efforts. They were written over a span of Years and probably need adjusting before you use them, to cater for changes in servers over time and changes in policies (like not testing heavily subscribed servers which are not open to new registrations)</p>
<p>If you aren't satisfied that the scripts are safe or simply don’t like the way they syntactically appear, you can still manually ping a selection of servers and choose a server based on the best latency. The following scripts are essentially just wrappers around the ping command which support lists of servers to feed to ping and present the output in a readable format.</p>
<p>If you feel you have a simpler cleaner script that works for another platform or language, please do add it to this wiki via a support ticket.
</p>
=== Bash Script To Handle The Mac Ping Output Format ===

<p>To make use of this script (1) save as a plain text file (2) set permissions on the file to executable (3) invoke script
e.g. Save script below using your favourite editor as pingVoipMS.sh (2) chmod u+x pingVoipMS.sh (3) ./pingVoipMS.sh
This is a bash 3.x script, so it also works in Linux, just change the ping packet loss field from 7 to 6 in the final loop below (or wherever the loss field is in your ping output format). Depending upon your distro curl might need to change to wget.
</p>
<pre>
#!/bin/bash
# Ping several servers and display Latency, Jitter and Packet Loss
# Usage: [-c <count>][-i <wait time>][-r test restricted servers][<server list file>]
#
# The optional server list text file should be formatted with one host name per line.
# The list of voip.ms servers is available at https://wiki.voip.ms/article/Choosing_Server
# If no args are supplied, this script will scrape a ping server list from voip.ms
#
USER_FILE=""
COUNT=3; INTERVAL=5; RESTRICTED=0
restrictedList=(atlanta.voip.ms chicago.voip.ms
montreal.voip.ms montreal2.voip.ms montreal3.voip.ms montreal4.voip.ms
newyork.voip.ms newyork4.voip.ms seattle.voip.ms
toronto.voip.ms toronto2.voip.ms toronto3.voip.ms toronto4.voip.ms)

# Handle any passed in script arguments
while getopts c:i:r parm
do
case $parm in
c)count_opt=$OPTARG;;
i)interval_opt=$OPTARG;;
r)RESTRICTED=1;;
*)echo -e "Invalid arg\nUsage:\t[ -c <count of ECHO_REQUESTs to Tx, default 3> ] \
\n\t[ -i <wait time (s) between datagrams, default 5> ] \
\n\t[ -r ] Include restricted servers in latency test \
\n\t[FILE <ping server list> ]";exit 1;;
esac
done

# Test if an option was specified and whether it's a +ve non-zero integer
[[ -n $count_opt && ($count_opt =~ ^[[:digit:]]+$) && $count_opt -gt 0 ]] &&
COUNT=$count_opt
[[ -n $interval_opt && ($interval_opt =~ ^[[:digit:]]+$) && $interval_opt -gt 0 ]] &&
INTERVAL=$interval_opt

shift $((OPTIND - 1))

# Validate supplied file (server list)
[[ -n $1 && ! (-f $1 && -r $1) ]] &&
{ echo "\"$1\" file does not exist or is not readable"; exit 1; }
[[ -n $1 && -f $1 && -r $1 ]] && USER_FILE="$1"

if [[ -n $USER_FILE ]]
then
# Bash 3.x in macOS does not support readarray, need to do cumbersome array loops instead
while IFS= read -r servers; do
serverList+=( "$servers" )
done < <(grep -Eo '^\b[[:alpha:]]+?[[:alnum:]]\.voip\.ms\b$' "$USER_FILE" | \
grep -v '^\s*#' | awk NF | sort)
else
# N.B. The script looks for the html boldface tags <b> </b> inside a bracket
# If the website alters and the parse fails, manually create the list and
# supply as a script arg (or perhaps update the parsing to work again :)
while IFS= read -r servers; do
serverList+=( "$servers" )
done < <(curl -sm 10 https://wiki.voip.ms/article/Choosing_Server | \
grep -E '(<b>[[:alpha:]]+?[[:alnum:]]\.voip\.ms</b>)' | \
tr "<>" " " | awk '{print $(NF-3)}' | sort )
fi

# Newer voip.ms clients can't register onto these over-subscribed servers
# Don't test the restricted list unless explicitly asked (with the -r cmd line option)
if [[ $RESTRICTED -eq 0 ]]
then
for server in "${restrictedList[@]}"
do
ix=$(printf "%s\n" "${serverList[@]}" | grep -n "^${server}" | cut -d ":" -f1)
while IFS= read -ra idx; do
keys+=( "${idx[@]}" )
done < <([[ $ix -gt 0 ]] && echo $((ix-1)))
done
for ((i=${#keys[@]} - 1; i >= 0; i--)); do unset "serverList[keys[i]]"; done
fi

if [[ ${#serverList[@]} -eq 0 ]]
then
echo "No unrestricted Voip.ms servers could be found, please supply a server list"
exit 1
fi

runTime=$((COUNT * INTERVAL * ${#serverList[@]}))

echo "PING will send $COUNT packet(s) with a wait of $INTERVAL sec(s) between each packet"
echo "Change the PING options by invoking this script with -c and/or -i, default \"-c 3 -i 5\""
echo "Over $((${#serverList[@]})) server(s) the estimated script Run Time will be $runTime seconds"
echo "================================================================"
printf "%-20s %-18s %7s %8s %6s %s\n" "VoIP Server" "IP Address" "Latency" "Jitter" "Loss" "Countdown"
echo "================================================================ (seconds)"

for myLn in "${serverList[@]}"
do
while IFS=$'\n' read -r pings; do
pingList+=( "$pings" )
printf "%-64s %5d %2d/%-2d\n" "$pings" \
"$((runTime - COUNT * INTERVAL * ${#pingList[@]}))" \
"${#pingList[@]}" "${#serverList[@]}"
done < <( ping -c "$COUNT" -i "$INTERVAL" -q "$myLn" | awk \
'
/^PING / {myH=$2}
/^PING / {
IP = substr($3,2,15)
split(IP,myIP,")") }
/packet loss/ {myPL=$7}
/min\/avg\/max/ {
split($4,myS,"/")
printf("%-20s %-18s %7.3f %8.3f %6s\n",
myH, myIP[1], myS[2], myS[4], myPL ) }
' )
done

echo "================================================================"
echo -e "\nMost appropriate server listed in order of best latency\n"
echo "================================================================"
printf "%-20s %-18s %7s %8s %6s\n" "VoIP Server" "IP Address" "Latency" "Jitter" "Loss"
echo "================================================================"
printf "%s\n" "${pingList[@]}" | LC_ALL=C sort -n -k 3,3 -k 5,5 -k 4,4 | \
awk '{printf("%s $%2d$\n",$0, NR)}'
echo "================================================================"
</pre>

=== Perl Script ===
Pings list of voip.ms servers round robin with optional output csv file.

# usage ping_voip.ms.pl <number of times> <seconds in between> <output.csv>
use Net::Ping;
use Time::HiRes;
use strict;

# input list
my @hosts = qw(
atlanta.voip.ms
atlanta2.voip.ms
chicago.voip.ms
chicago2.voip.ms
chicago3.voip.ms
chicago4.voip.ms
dallas.voip.ms
denver.voip.ms
denver2.voip.ms
houston.voip.ms
losangeles.voip.ms
losangeles2.voip.ms
newyork.voip.ms
newyork2.voip.ms
newyork3.voip.ms
newyork4.voip.ms
seattle.voip.ms
seattle2.voip.ms
seattle3.voip.ms
tampa.voip.ms
washington.voip.ms
washington2.voip.ms
montreal.voip.ms
montreal2.voip.ms
montreal3.voip.ms
montreal4.voip.ms
toronto2.voip.ms
toronto3.voip.ms
toronto4.voip.ms
toronto.voip.ms
london.voip.ms
);

$| = 1; #autoflush
# High precision syntax (requires Time::HiRes)
my $p = Net::Ping->new("icmp",1);
$p->hires();
my $max_name_length = (reverse sort { $a <=> $b } map { length($_) } @hosts)[0];
my $count = 4; # number of times to ping
my $interval = 5; # seconds between ping rounds
my $output_file = "";
my @data;

# check for arguments
my $num_args = @ARGV;
if ($num_args >= 1) {$count = $ARGV[0];}
if ($num_args >= 2) {$interval = $ARGV[1];}
if ($num_args >= 3) {$output_file = $ARGV[2];}

# check argument validity
$0 =~ /^.*\\(.*)$/;
my $script = $1;
if ($count !~ /^\d+$/ or $interval !~ /^\d+$/) {die "Usage: $script <number of rounds> <seconds between rounds> <output.csv>\n";}
if (length($output_file) > 0 and $output_file !~ /\.csv$/) {$output_file .= ".csv";}

# main loop
for my $i (1..$count)
{
sleep $interval unless $i == 1;
print "Round $i\n";
my $host_num=0;
foreach my $host (@hosts)
{
(my $ret, my $duration, my $ip) = $p->ping($host);
$ip =~ /(\d+)\.(\d+)\.(\d+)\.(\d+)/;
if ($ret)
{
printf("%*s [ip: %3s.%3s.%3s.%3s] is alive (%6.2f ms)\n", $max_name_length, $host, $1, $2, $3, $4, $duration*1000);
$data[$host_num][$i]=$duration*1000;
}
else
{
printf("%*s [ip: %3s.%3s.%3s.%3s] is dead\n", $max_name_length, $host, $1, $2, $3, $4);
}
$host_num++;
}
print "\n";
}
$p->close();

# if output file name given
if (length($output_file)>0)
{
# print output to file
open FILE, ">$output_file" or die "$!\n";

# print column headers
print FILE "Server\\Round";
for my $i (1..$count)
{
print FILE ", $i";
}
print FILE ", Average\n";

# print data
my $i = 0;
foreach my $host (@hosts)
{
print FILE "$host";
my $sum = 0;
for my $j (1..$count)
{
$sum += $data[$i][$j];
printf FILE ", %8.4f",$data[$i][$j];
}
printf FILE ", %8.4f\n",$sum/$count;
$i++;
}

close FILE;
print "Data written to $output_file\n";
}

# print summary to screen
my $i = 0;
printf("%-*s Average (ms)\n", $max_name_length, "Server");
foreach my $host (@hosts)
{
my $sum = 0;
for my $j (1..$count)
{
$sum += $data[$i][$j];
}
printf("%-*s %8.4f\n", $max_name_length+1, $host, $sum/$count);
$i++;
}

Output:
Round 1
atlanta.voip.ms [ip: 174. 34.146.162] is alive ( 88.97 ms)
atlanta2.voip.ms [ip: 72. 9.246.170] is alive ( 92.99 ms)
chicago.voip.ms [ip: 208.100. 39. 52] is alive ( 49.70 ms)
chicago2.voip.ms [ip: 208.100. 39. 53] is alive ( 59.76 ms)
chicago3.voip.ms [ip: 208.100. 39. 54] is alive ( 59.53 ms)
chicago4.voip.ms [ip: 208.100. 39. 55] is alive ( 49.73 ms)
dallas.voip.ms [ip: 74. 54. 54.178] is alive ( 94.99 ms)
denver.voip.ms [ip: 173.248.161. 90] is alive ( 94.05 ms)
denver2.voip.ms [ip: 173.248.159.210] is alive ( 85.13 ms)
houston.voip.ms [ip: 209. 62. 1. 2] is alive (102.87 ms)
losangeles.voip.ms [ip: 96. 44.149.186] is alive ( 64.92 ms)
losangeles2.voip.ms [ip: 96. 44.149.202] is alive ( 63.41 ms)
newyork.voip.ms [ip: 74. 63. 41.218] is alive (131.75 ms)
newyork2.voip.ms [ip: 107. 6. 67.236] is alive (120.64 ms)
newyork3.voip.ms [ip: 107. 6. 67.237] is alive (120.49 ms)
newyork4.voip.ms [ip: 107. 6. 67.238] is alive (111.43 ms)
seattle.voip.ms [ip: 50. 23.160. 50] is alive ( 94.25 ms)
seattle2.voip.ms [ip: 50. 23.160. 51] is alive ( 95.86 ms)
seattle3.voip.ms [ip: 50. 23.160. 52] is alive ( 90.85 ms)
tampa.voip.ms [ip: 68.233.226. 97] is alive (123.29 ms)
washington.voip.ms [ip: 208. 43.234.226] is alive ( 98.71 ms)
washington2.voip.ms [ip: 208. 43.234.227] is alive (101.19 ms)
montreal.voip.ms [ip: 67.205. 74.184] is alive ( 81.82 ms)
montreal2.voip.ms [ip: 67.205. 74.187] is alive ( 86.13 ms)
montreal3.voip.ms [ip: 72. 55.168. 18] is alive ( 77.09 ms)
montreal4.voip.ms [ip: 67.205. 74.179] is alive ( 96.18 ms)
toronto2.voip.ms [ip: 184. 75.215.114] is alive (103.70 ms)
toronto3.voip.ms [ip: 184. 75.215.146] is alive (131.27 ms)
toronto4.voip.ms [ip: 184. 75.213.210] is alive (125.13 ms)
toronto.voip.ms [ip: 184. 75.215.106] is alive (103.26 ms)
london.voip.ms [ip: 5. 77. 36.136] is alive (152.77 ms)

Round 2
atlanta.voip.ms [ip: 174. 34.146.162] is alive ( 88.14 ms)
atlanta2.voip.ms [ip: 72. 9.246.170] is alive ( 92.86 ms)
chicago.voip.ms [ip: 208.100. 39. 52] is alive ( 50.03 ms)
chicago2.voip.ms [ip: 208.100. 39. 53] is alive ( 59.44 ms)
chicago3.voip.ms [ip: 208.100. 39. 54] is alive ( 59.33 ms)
chicago4.voip.ms [ip: 208.100. 39. 55] is alive ( 50.22 ms)
dallas.voip.ms [ip: 74. 54. 54.178] is alive ( 95.58 ms)
denver.voip.ms [ip: 173.248.161. 90] is alive ( 95.94 ms)
denver2.voip.ms [ip: 173.248.159.210] is alive ( 85.29 ms)
houston.voip.ms [ip: 209. 62. 1. 2] is alive (102.73 ms)
losangeles.voip.ms [ip: 96. 44.149.186] is alive ( 65.59 ms)
losangeles2.voip.ms [ip: 96. 44.149.202] is alive ( 64.27 ms)
newyork.voip.ms [ip: 74. 63. 41.218] is alive (112.74 ms)
newyork2.voip.ms [ip: 107. 6. 67.236] is alive (121.22 ms)
newyork3.voip.ms [ip: 107. 6. 67.237] is alive (121.34 ms)
newyork4.voip.ms [ip: 107. 6. 67.238] is alive (110.75 ms)
seattle.voip.ms [ip: 50. 23.160. 50] is alive ( 94.06 ms)
seattle2.voip.ms [ip: 50. 23.160. 51] is alive ( 95.33 ms)
seattle3.voip.ms [ip: 50. 23.160. 52] is alive ( 91.58 ms)
tampa.voip.ms [ip: 68.233.226. 97] is alive (122.94 ms)
washington.voip.ms [ip: 169.62.41.189] is alive ( 98.28 ms)
washington2.voip.ms [ip: 169.62.41.187] is alive (101.40 ms)
montreal.voip.ms [ip: 67.205. 74.184] is alive ( 81.91 ms)
montreal2.voip.ms [ip: 67.205. 74.187] is alive ( 85.64 ms)
montreal3.voip.ms [ip: 72. 55.168. 18] is alive ( 75.15 ms)
montreal4.voip.ms [ip: 67.205. 74.179] is alive ( 96.79 ms)
toronto2.voip.ms [ip: 184. 75.215.114] is alive (103.10 ms)
toronto3.voip.ms [ip: 184. 75.215.146] is alive (150.85 ms)
toronto4.voip.ms [ip: 184. 75.213.210] is alive (138.40 ms)
toronto.voip.ms [ip: 184. 75.215.106] is alive (103.45 ms)
london.voip.ms [ip: 5. 77. 36.136] is alive (170.79 ms)

Round 3
atlanta.voip.ms [ip: 174. 34.146.162] is alive ( 88.76 ms)
atlanta2.voip.ms [ip: 72. 9.246.170] is alive ( 92.86 ms)
chicago.voip.ms [ip: 208.100. 39. 52] is alive ( 49.65 ms)
chicago2.voip.ms [ip: 208.100. 39. 53] is alive ( 60.01 ms)
chicago3.voip.ms [ip: 208.100. 39. 54] is alive ( 59.05 ms)
chicago4.voip.ms [ip: 208.100. 39. 55] is alive ( 49.53 ms)
dallas.voip.ms [ip: 74. 54. 54.178] is alive ( 95.82 ms)
denver.voip.ms [ip: 173.248.161. 90] is alive ( 95.02 ms)
denver2.voip.ms [ip: 173.248.159.210] is alive ( 85.60 ms)
houston.voip.ms [ip: 209. 62. 1. 2] is alive (103.35 ms)
losangeles.voip.ms [ip: 96. 44.149.186] is alive ( 65.79 ms)
losangeles2.voip.ms [ip: 96. 44.149.202] is alive ( 64.05 ms)
newyork.voip.ms [ip: 74. 63. 41.218] is alive (113.01 ms)
newyork2.voip.ms [ip: 107. 6. 67.236] is alive (121.41 ms)
newyork3.voip.ms [ip: 107. 6. 67.237] is alive (122.23 ms)
newyork4.voip.ms [ip: 107. 6. 67.238] is alive (110.62 ms)
seattle.voip.ms [ip: 50. 23.160. 50] is alive ( 93.65 ms)
seattle2.voip.ms [ip: 50. 23.160. 51] is alive ( 95.19 ms)
seattle3.voip.ms [ip: 50. 23.160. 52] is alive ( 90.75 ms)
tampa.voip.ms [ip: 68.233.226. 97] is alive (125.12 ms)
washington.voip.ms [ip: 208. 43.234.226] is alive ( 98.19 ms)
washington2.voip.ms [ip: 208. 43.234.227] is alive (101.98 ms)
montreal.voip.ms [ip: 67.205. 74.184] is alive ( 80.16 ms)
montreal2.voip.ms [ip: 67.205. 74.187] is alive ( 87.16 ms)
montreal3.voip.ms [ip: 72. 55.168. 18] is alive ( 76.54 ms)
montreal4.voip.ms [ip: 67.205. 74.179] is alive ( 97.51 ms)
toronto2.voip.ms [ip: 184. 75.215.114] is alive (104.18 ms)
toronto3.voip.ms [ip: 184. 75.215.146] is alive (142.81 ms)
toronto4.voip.ms [ip: 184. 75.213.210] is alive (138.95 ms)
toronto.voip.ms [ip: 184. 75.215.106] is alive (103.78 ms)
london.voip.ms [ip: 5. 77. 36.136] is alive (153.14 ms)

Round 4
atlanta.voip.ms [ip: 174. 34.146.162] is alive ( 89.19 ms)
atlanta2.voip.ms [ip: 72. 9.246.170] is alive ( 92.98 ms)
chicago.voip.ms [ip: 208.100. 39. 52] is alive ( 49.21 ms)
chicago2.voip.ms [ip: 208.100. 39. 53] is alive ( 60.50 ms)
chicago3.voip.ms [ip: 208.100. 39. 54] is alive ( 59.68 ms)
chicago4.voip.ms [ip: 208.100. 39. 55] is alive ( 50.18 ms)
dallas.voip.ms [ip: 74. 54. 54.178] is alive ( 93.93 ms)
denver.voip.ms [ip: 173.248.161. 90] is alive ( 94.22 ms)
denver2.voip.ms [ip: 173.248.159.210] is alive ( 85.10 ms)
houston.voip.ms [ip: 209. 62. 1. 2] is alive (103.67 ms)
losangeles.voip.ms [ip: 96. 44.149.186] is alive ( 65.58 ms)
losangeles2.voip.ms [ip: 96. 44.149.202] is alive ( 63.60 ms)
newyork.voip.ms [ip: 74. 63. 41.218] is alive (114.76 ms)
newyork2.voip.ms [ip: 107. 6. 67.236] is alive (120.44 ms)
newyork3.voip.ms [ip: 107. 6. 67.237] is alive (121.05 ms)
newyork4.voip.ms [ip: 107. 6. 67.238] is alive (110.51 ms)
seattle.voip.ms [ip: 50. 23.160. 50] is alive ( 94.04 ms)
seattle2.voip.ms [ip: 50. 23.160. 51] is alive ( 96.92 ms)
seattle3.voip.ms [ip: 50. 23.160. 52] is alive ( 91.23 ms)
tampa.voip.ms [ip: 68.233.226. 97] is alive (123.28 ms)
washington.voip.ms [ip: 208. 43.234.226] is alive ( 98.45 ms)
washington2.voip.ms [ip: 208. 43.234.227] is alive (100.94 ms)
montreal.voip.ms [ip: 67.205. 74.184] is alive ( 82.33 ms)
montreal2.voip.ms [ip: 67.205. 74.187] is alive ( 85.02 ms)
montreal3.voip.ms [ip: 72. 55.168. 18] is alive ( 76.85 ms)
montreal4.voip.ms [ip: 67.205. 74.179] is alive ( 96.32 ms)
toronto2.voip.ms [ip: 184. 75.215.114] is alive (104.22 ms)
toronto3.voip.ms [ip: 184. 75.215.146] is alive (148.33 ms)
toronto4.voip.ms [ip: 184. 75.213.210] is alive (141.61 ms)
toronto.voip.ms [ip: 184. 75.215.106] is alive (105.91 ms)
london.voip.ms [ip: 5. 77. 36.136] is alive (152.85 ms)

Server Average (ms)
atlanta.voip.ms 88.7630
atlanta2.voip.ms 92.9233
chicago.voip.ms 49.6477
chicago2.voip.ms 59.9305
chicago3.voip.ms 59.3972
chicago4.voip.ms 49.9152
dallas.voip.ms 95.0790
denver.voip.ms 94.8077
denver2.voip.ms 85.2797
houston.voip.ms 103.1562
losangeles.voip.ms 65.4693
losangeles2.voip.ms 63.8347
newyork.voip.ms 118.0643
newyork2.voip.ms 120.9265
newyork3.voip.ms 121.2778
newyork4.voip.ms 110.8275
seattle.voip.ms 93.9993
seattle2.voip.ms 95.8267
seattle3.voip.ms 91.1035
tampa.voip.ms 123.6570
washington.voip.ms 98.4065
washington2.voip.ms 101.3774
montreal.voip.ms 81.5525
montreal2.voip.ms 85.9863
montreal3.voip.ms 76.4058
montreal4.voip.ms 96.7013
toronto2.voip.ms 103.7986
toronto3.voip.ms 143.3156
toronto4.voip.ms 136.0254
toronto.voip.ms 104.1012
london.voip.ms 157.3885

=== Powershell ===

Dec 2017 - A bug in the code shown washington2.voip.ms as the best server, this was corrected.

<pre>
# Usage: Copy and paste the following code into a powershell window
# To run it from a command prompt, save this file with extension ps1.
# Then run Powershell.exe -file "pathtothisscript.ps1"
Clear-Variable best* -Scope Global #Clear the best* variables in case you run it more than once...
#Get the list of servers into an array
$Servers =
@("amsterdam.voip.ms","atlanta.voip.ms","atlanta2.voip.ms","chicago.voip.ms","chicago2.voip.ms","chicago3.voip.ms",
"chicago4.voip.ms","dallas.voip.ms","dallas2.voip.ms","denver.voip.ms","denver2.voip.ms","houston.voip.ms",
"houston2.voip.ms","london.voip.ms","losangeles.voip.ms","losangeles2.voip.ms","montreal.voip.ms",
"montreal2.voip.ms","montreal3.voip.ms","montreal4.voip.ms","montreal5.voip.ms","montreal6.voip.ms","montreal7.voip.ms",
"montreal8.voip.ms","newyork.voip.ms","newyork2.voip.ms","newyork3.voip.ms","newyork4.voip.ms","newyork5.voip.ms",
"newyork6.voip.ms","newyork7.voip.ms","newyork8.voip.ms","paris.voip.ms","sanjose.voip.ms","sanjose2.voip.ms",
"seattle.voip.ms","seattle2.voip.ms","seattle3.voip.ms","tampa.voip.ms","tampa2.voip.ms","toronto.voip.ms",
"toronto2.voip.ms","toronto3.voip.ms","toronto4.voip.ms","toronto5.voip.ms","toronto6.voip.ms","toronto7.voip.ms",
"toronto8.voip.ms","vancouver.voip.ms","vancouver2.voip.ms","washington.voip.ms","washington2.voip.ms")
$k = 0 #Counting variable so we know what server number we are testing
#num of servers to test
$servercount = $servers.length
#Do the following code for each server in our array
ForEach($server in $servers)
{
#Add one to the counting variable....we are on server #1...then server 2, then server 3 etc...
$k++
#Update the progress bar
Write-Progress -Activity "Testing Server: ${server}" -status "Testing Server $k out of $servercount" -percentComplete ($k / $servercount*100)
#Counting variable for number of times we tried to ping a given server
$i = 0
Do{
#assume a failure
$pingsuccess = $false
$i++ #Add one to the counting variable.....1st try....2nd try....3rd try etc...
Try{
#Try to ping
$currentping = (test-connection $server -count 1 -ErrorAction Stop).responsetime
#If success full, set success variable
$pingsuccess = $true
}
#Catch the failure and set the success variable to false
Catch {
$pingsuccess = $false
}
}
#Try everything between Do and While up to 5 times, or while $pingsuccess is not true
While($pingsuccess -eq $false -and $i -le 5)
#Compare the last ping test with the best known ping test....if there is no known best ping test, assume this one is the best $bestping = $currentping
If($pingsuccess -and ($currentping -lt $bestping -or (!($bestping)))){
#If this is the best ping...save it
$bestserver = $server #Save the best server
$bestping = $currentping #Save the best ping results
}
write-host "tested: $server at $currentping ms after $i attempts" #write the results of the test for this server
}
write-host "`r`n The server with the best ping is: $bestserver at $bestping ms`r`n" #write the end result
Pause
</pre>

=== Linux Shell Script ===
Pings several voip.ms servers

#!/bin/sh
# Ping several servers and display Latency, Jitter and Packet Loss
#
# First, create a text file with all servers you want to ping - one host name per line.
# The list of voip.ms servers is available at http://wiki.voip.ms/article/Choosing_Server
myHF="voip_ping_hosts.txt"
# Sample file:
# toronto.voip.ms
# montreal.voip.ms
# seattle.voip.ms
# chicago.voip.ms
# newyork.voip.ms
#
echo "============================================"
printf "%-20s %7s %8s %6s\n" "VoIP Server" "Latency" "Jitter" "Loss"
echo "============================================"
cat ${myHF} |\
while read myLn
do
ping -c 3 -i 5 -q $myLn |\
awk '/^PING / {myH=$2}
/packet loss/ {myPL=$6}
/min\/avg\/max/ {
split($4,myS,"/")
printf( "%-20s %3.1f %1.3f %4s\n", myH, myS[2], myS[4], myPL)
}'
done
echo "============================================"

Output:

============================================
VoIP Server Latency Jitter Loss
============================================
toronto.voip.ms 68.3 0.439 0%
montreal.voip.ms 89.6 0.197 0%
seattle.voip.ms 71.2 0.387 0%
chicago.voip.ms 71.6 0.084 0%
newyork.voip.ms 79.1 0.411 0%
============================================

= Latency and its importance =

Latency is very important for Voip, this will determine the time that will take for the data package transmission to reach the destination. A high latency will lead to a delay and echoes in the communication.

Latency is measured in milliseconds (ms) For example: a latency of 150ms is barely noticeable, thus acceptable. Higher than that, quality starts to suffer. When it gets higher than 300 ms, it becomes unacceptable.

[[category:guides]]

Mensajes multimedia (MMS)

2021-04-22T17:00:44Z

B13n:

{| class="wikitable"
|+
|-
! Article in English !! Article en Français
|-
| [https://wiki.voip.ms/article/MMS English] ||
[https://wiki.voip.ms/article/Messagerie_multim%C3%A9dia Français]
|}

==MMS==

Con la incorporación del Servicio de mensajes multimedia (MMS) al servicio, los usuarios ahora pueden enviar y recibir archivos multimedia (fotos, videos y audio), así como enviar mensajes de texto con más de 160 caracteres (que es el límite para un SMS). El servicio MMS también permite al usuario enviar un mensaje a varios destinatarios al mismo tiempo.

==Artículos de Blog==

[https://wiki.voip.ms/article/Benefits_of_SMS/MMS_Campaigns_vs._Email_Marketing Beneficios de las campañas de SMS / MMS frente al marketing por correo electrónico (Inglés)]

==Limitaciones del Servicio==

'''Nota:''' tenga en cuenta que el servicio MMS se encuentra en la fase Beta.
Es importante para nosotros que informe cualquier problema con este servicio enviando un correo electrónico al soporte para que los desarrolladores puedan participar
si es necesario.

Los mensajes MMS tienen un costo de $ 0.02 por mensaje entrante y saliente.
* El servicio MMS solo está disponible para números DID locales de E.U.A y Canadá marcados con el ícono distintivo de SMS / MMS.
* El servicio MMS solo se puede utilizar para enviar mensajes MMS a números canadienses y estadounidenses de 10 dígitos en este momento.
* Por el momento, recibir y leer MMS solo es posible a través del centro de mensajes y usando la opción de reenvío de mensajes (Forward). MMS a través del protocolo SIP no está disponible.
* VoIP.ms se reserva el derecho, a su sola discreción, de limitar o deshabilitar el servicio MMS de cualquier cuenta que pueda presentar patrones de marketing / patrones de automatización / envío o recepción masiva.
* No podemos garantizar que los acentos o caracteres especiales, incluidas las letras no latinas, se entreguen correctamente.
* Los acortadores de URL públicas como bit.ly, tinyurl.com, etc., están ampliamente restringidos por los proveedores de servicios móviles como una respuesta de la industria para combatir las campañas de SPAM y proteger al consumidor. La inclusión de este tipo de enlaces en sus mensajes puede resultar en un mensaje bloqueado o no entregado.
* Para números porteados o transferidos compatibles con la función: La función MMS estará disponible hasta 48 horas después de que el proceso de transferencia se marque como completado.

'''Además, tenga en cuenta las siguientes restricciones para enviar MMS:'''
• Los tipos de archivos adjuntos permitidos son JPG, GIF, JPEG, PNG, MP3, WAV, MIDI, MP4 y 3GP
• El tamaño máximo de cada archivo adjunto es de 1300 KB.
• Puede adjuntar hasta 3 archivos
• El número máximo de caracteres en un mensaje de texto es 2048

Si tiene más preguntas, no dude en ponerse en contacto con el personal de soporte en el chat en vivo o el sistema de tickets.

==Identificación de un número DID de MMS==

Lo primero que debe saber es que esta función solo está disponible para números locales de US y Canadá en este momento. Notarás que algunos números tienen un pequeño ícono Sms-mms-icon.png, esto indica que el número es compatible con esta función.

Puede comenzar a solicitar un número DID desde su portal >> DID Numbers >> Order DID >> Local Numbers >> US or Canada Numbers y podrá comprar el número deseado, solo asegúrese de que sea compatible con la función MMS.

[[File:ORDER_DID_SMS_MMS_ICON.png|thumb|none|600px]]

==Configurar el servicio MMS==

Una vez comprado, el Servicio MMS debe activarse en la configuración DID, desde su portal >> DID Numbers >> Manage DID >> Edit Selectión >> sección de configuración SMS / MMS.

En esa sección, puede activar y configurar algunas opciones de reenvío para el servicio SMS / MMS.

[[File:ENABLE_DID_SMS_MMS.png|thumb|none|600px]]

==Envío de un MMS (interfaz web)==

'''Paso 1'''

Haga clic en el botón "send New Message" para que se muestre una lista de contactos o escriba directamente el número en el campo de texto del contacto. Si este número está registrado en la agenda, mostrará su nombre en su lugar.

[[File:MMS-Webportal1.png|thumb|none|600px]]

'''Paso 2'''

Haga clic para mostrar la lista de números DID disponibles. Elija el número desde el cual enviar el mensaje.

[[File:MMS-Webportal3.png|thumb|none|600px]]

'''Paso 3'''

Escriba su mensaje en el campo de texto y haga clic en la flecha roja para enviarlo. Los mensajes de texto de hasta 160 caracteres se considerarán SMS. Los mensajes de medios o mensajes de texto de más de 160 caracteres se considerarán MMS y verá el icono que cambia de SMS a MMS indicando esto.

[[File:MMS-Webportal4.png|thumb|none|600px]]

'''Paso 4'''

Para enviar un archivo multimedia a través de un MMS, haga clic en el botón del clip para buscar y elegir un archivo multimedia.

[[File:MMS-Webportal5.2.png|thumb|none|600px]]

Haga clic en el botón Examinar para buscar el archivo multimedia en su computadora o arrastre y suelte el archivo directamente en el cuadro.

[[File:MMS-Webportal6.PNG|thumb|none|600px]]

Los archivos adjuntos se mostrarán debajo del cuadro de texto.

[[File:MMS-Webportal5.PNG|thumb|none|600px]]

Una vez enviado el mensaje, se abrirá una nueva conversación a la izquierda. Al seleccionar esta conversación, se mostrará el historial de mensajes en el cuadro.

[[File:MMS_WINDOW_CONVO.png|thumb|none|600px]]

==Recibir un MMS (interfaz web)==

Si bien los mensajes SMS se pueden recibir directamente en una App a través del Protocolo SIP y la configuración correcta, por el momento, recibir y leer MMS solo es posible a través del centro de mensajes.

Puede acceder al centro de comunicaciones desde su portal de clientes en DID Numbers> Centro de Mensajes SMS / MMS . Cualquier mensaje recibido aparecerá aquí en el lado izquierdo del panel.

Utilice el filtro DID para elegir y mostrar mensajes para un número DID específico o para todos los números DID. También puede filtrar los mensajes por fecha y zona horaria.

[[File:MMS-Inbound-1.png|thumb|none|600px]]

Elija una conversación del panel de la izquierda. También está disponible una opción para eliminar la conversación. Elija el número DID del cuadro de texto para responder.

[[File:MMS-Inbound_DELETE.png|thumb|none|600px]]

MMS

2021-04-22T16:55:38Z

B13n:

{| class="wikitable"
|+
|-
! Article en Français !! Artículo en Español
|-
| [https://wiki.voip.ms/article/Messagerie_multim%C3%A9dia Français] ||
[https://wiki.voip.ms/article/Mensajes_multimedia_(MMS) Español]
|}

==MMS==

With the addition of '''M'''ultimedia '''M'''essage '''S'''ervice ('''MMS''') to the service, users are now capable of sending and receiving media files ('''photos, videos, and audio''') as well as sending text messages with more than 160 characters (which is the limit for an SMS). The MMS service also allows the user to send a message to multiple recipients at the same time.

== Blog Articles ==
[https://wiki.voip.ms/article/Benefits_of_SMS/MMS_Campaigns_vs._Email_Marketing Benefits of SMS/MMS Campaigns vs. Email Marketing]

== Service Limitations ==

'''Note: Please notice that the MMS service is in the Beta phase.'''
It is important to us that you report any issues with this service by sending an email to [mailto:support@voip.ms support] so that the developers can<br>get involved if necessary.

'''MMS Messages have a cost of $0.02 per incoming and outgoing message.'''

* '''The limit of the capacity to send SMS/MMS via the portal is unlimited.'''

* '''The limit of sending SMS/MMS via the API is limited to 100 per day. For any modification to the limit, please contact support or open a ticket via the customer portal.'''

:* The MMS Service is only available for US and Canadian local DID Numbers marked with the distinctive SMS/MMS Icon.
:* The MMS Service can only be used to send MMS Messages to Canadian and US 10 digit numbers at this time.
:* At the moment, receiving and reading MMS is only possible through the message center or by using the SMS/MMS Forward option. MMS through SIP protocol is not available.
:* VoIP.ms reserves the right, at its sole discretion, to limit or disable the MMS service from any account that may present marketing patterns/automation patterns/bulk sending or receiving.
:* We cannot guarantee that accents or special characters including non-Latin letters will be properly delivered.
:* Public URL shorteners such as '''bit.ly, tinyurl.com, etc''', are widely restricted by mobile providers as a response from the industry to combat SPAM campaigns and protect the consumer. Including this type of links into your messages may result in a blocked or undelivered message.
:* For '''Ported In Numbers''' compatible with the feature: The MMS Functionality will be available up to 48 hours after the porting process is marked as Completed.

'''Additionally, please note of the following restrictions for sending MMS:'''
• Permitted attachment types are JPG, GIF, JPEG, PNG, MP3, WAV, MIDI, MP4 and 3GP
• The maximum size for each attachment is 1300 KB
• You can attach up to 3 files
• Maximum characters in a text message is 2048

If you have further questions don't hesitate to contact the Support Staff on the Live Chat or Ticket System.

==Identifying a MMS DID Number==

The first thing you need to know is that this feature is only available for local US and Canadian numbers at this time. You will note that some numbers have a little [[File:Sms-mms-icon.png|15px]] icon, this indicates that the number supports this feature.

You can start ordering a DID Number from your portal >> DID Numbers >> Order DID >> Local Numbers >> (US or Canada) Numbers and you will be able to purchase your desired number, just make sure it supports the MMS feature.

[[File:ORDER_DID_SMS_MMS_ICON.png|thumb|none|600px]]

==Configuring the MMS service==

Once purchased the MMS Service needs to be activated on the DID settings, from your portal >> DID Numbers >> Manage DID >> Edit Selection >> SMS/MMS configuration section.

In that section, you can activate and configure some forward options for the SMS/MMS service.

[[File:ENABLE_DID_SMS_MMS.png|thumb|none|600px]]

==Sending a MMS (Web Interface)==

'''Step 1'''

Click the "send New Message" button to get a list of contacts displayed or directly type in the number into the contact text field. If this number is registered in the phonebook, it will display its name instead.

[[File:MMS-Webportal1.png|thumb|none|600px]]

'''Step 2'''

Click to display the list of available DID numbers. Choose the number to send the message from.

[[File:MMS-Webportal3.png|thumb|none|600px]]

'''Step 3'''

Write your message on the text field and click the red arrow to send it. Text messages up to 160 characters will be considered SMS. Media messages or text messages over 160 characters will be considered MMS and you will see the icon turning from SMS to MMS indicating of this.
[[File:MMS-Webportal4.png|thumb|none|600px]]

'''Step 4'''

In order to send a media file over an MMS, click the clip button to browse and choose a media file.

[[File:MMS-Webportal5.2.png|thumb|none|600px]]

Click the browse button to search for the media file in your computer or drag and drop the file directly into the box.

[[File:MMS-Webportal6.PNG|thumb|none|600px]]

The attached files will show below the text box.

[[File:MMS-Webportal5.PNG|thumb|none|600px]]

Once the message is sent, a new conversation will be opened on the left. Selecting this conversation will show the messages history on the box.

[[File:MMS_WINDOW_CONVO.png|thumb|none|600px]]

==Receiving an MMS (Web Interface)==

While SMS messages can be received directly in an App through the SIP Protocol and correct configuration, at the moment, '''receiving and reading MMS is only possible through the message center.'''

You can access the communication center from your customer portal at DID numbers > SMS / MMS Message Center. Any message received will appear here on the left side of the panel.

Use the DID Filter to choose and display messages for a specific DID number or for all DID numbers. You can also filter the messages by date and time zone.

[[File:MMS-Inbound-1.png|thumb|none|600px]]

Choose a conversation from the left panel. An option to delete the conversation is also available. Choose the DID number from the text box to reply.

[[File:MMS-Inbound_DELETE.png|thumb|none|600px]]

Elegir servidor

2021-03-31T13:05:35Z

B13n:

[[File:ChooseServerImg.png|thumb|none|1280px|VoIP.ms servers]]

{| class="wikitable"
|+
|-
! Article in English !! Article en Français
|-
| [https://wiki.voip.ms/article/Choosing_Server English] ||
[https://wiki.voip.ms/article/Choisir_un_serveur Français]
|}

= Elegir un Servidor =

VoIP.ms le ofrece la posibilidad de conectarse a diferentes servidores, pero ¿cuál es el que debe elegir? Es común pensar que se debe elegir el servidor más cercano a su localidad, sin embargo esto no es necesario en la mayoría de las veces. Si usted está en Estados Unidos, cualquier servidor en EEUU le debe dar un buen resultado en latencia y calidad. También es de utilidad saber que hay una herramienta que le puede ayudar a seleccionar el mejor servidor a usar, este normalmente se llama "ping", el cual le provee la latencia entre usted y el servidor, así usted opcionalmente puede elegir específicamente el servidor que le provea una menor latencia.

'''Nota:''' Tenga en cuenta que es posible que algunos servidores no estén disponibles para que su número DID se utilice como POP (Punto de presencia) en la sección
"Administrar DID". Asegúrese de que su dispositivo SIP / IAX y su número de teléfono apunten al mismo servidor.

=== IPs ===

<div><ul>
<li style="display: inline-block; vertical-align:top;">
'''Canada'''
*Montreal 1, QC ('''montreal.voip.ms''') 192.175.96.73
*Montreal 2, QC ('''montreal2.voip.ms''') 192.175.96.74
*Montreal 3, QC ('''montreal3.voip.ms''') 192.175.96.68
*Montreal 4, QC ('''montreal4.voip.ms''') 67.205.74.179
*Montreal 5, QC ('''montreal5.voip.ms''') 192.175.96.69
*Montreal 6, QC ('''montreal6.voip.ms''') 192.175.96.70
*Montreal 7, QC ('''montreal7.voip.ms''') 192.175.96.71
*Montreal 8, QC ('''montreal8.voip.ms''') 192.175.96.72
*Montreal 9, QC ('''montreal9.voip.ms''') 67.205.74.184
*Montreal 10, QC ('''montreal10.voip.ms''') 67.205.74.187
*Toronto 1, ON ('''toronto.voip.ms''') 158.85.70.148
*Toronto 2, ON ('''toronto2.voip.ms''') 158.85.70.149
*Toronto 3, ON ('''toronto3.voip.ms''') 158.85.70.150
*Toronto 4, ON ('''toronto4.voip.ms''') 158.85.70.151
*Toronto 5, ON ('''toronto5.voip.ms''') 184.75.215.106
*Toronto 6, ON ('''toronto6.voip.ms''') 184.75.215.114
*Toronto 7, ON ('''toronto7.voip.ms''') 184.75.215.146
*Toronto 8, ON ('''toronto8.voip.ms''') 184.75.213.210
*Toronto 9, ON ('''toronto9.voip.ms''') 158.85.70.154
*Toronto 10, ON ('''toronto10.voip.ms''') 158.85.70.158
*Vancouver 1, BC ('''vancouver.voip.ms''') 162.213.157.220
*Vancouver 2, BC ('''vancouver2.voip.ms''') 162.213.157.117
*Vancouver 3, BC ('''vancouver3.voip.ms''') 162.213.157.82
</li>

<li style="display: inline-block; vertical-align:top;">
'''Estados Unidos'''
*Atlanta 1, GA ('''atlanta.voip.ms''') 75.127.65.130
*Atlanta 2, GA ('''atlanta2.voip.ms''') 209.217.224.50
*Chicago 1, IL ('''chicago.voip.ms''') 208.100.39.52
*Chicago 2, IL ('''chicago2.voip.ms''') 208.100.39.53
*Chicago 3, IL ('''chicago3.voip.ms''') 208.100.39.54
*Chicago 4, IL ('''chicago4.voip.ms''') 208.100.39.55
*Chicago 5, IL ('''chicago5.voip.ms''') 50.31.115.149
*Chicago 6, IL ('''chicago6.voip.ms''') 50.31.115.150
*Chicago 7, IL ('''chicago7.voip.ms''') 50.31.115.151
*Dallas, TX ('''dallas.voip.ms''') 158.85.149.162
*Dallas 2, TX ('''dallas2.voip.ms''') 158.85.149.163
*Denver 1, CO ('''denver.voip.ms''') 23.239.211.90
*Denver 2, CO ('''denver2.voip.ms''') 64.27.52.226
*Houston, TX ('''houston.voip.ms''') 173.193.85.18
*Houston 2, TX ('''houston2.voip.ms''') 173.193.85.19
*Los Angeles 1, CA ('''losangeles.voip.ms''') 96.44.149.186
*Los Angeles 2, CA ('''losangeles2.voip.ms''') 96.44.149.202
*Los Angeles 3, CA ('''losangeles3.voip.ms''') 64.188.6.162
*Los Angeles 4, CA ('''losangeles4.voip.ms''') 64.188.6.170
*New York 1, NY ('''newyork.voip.ms''') 72.251.239.196
*New York 2, NY ('''newyork2.voip.ms''') 72.251.239.205
*New York 3, NY ('''newyork3.voip.ms''') 72.251.239.206
*New York 4, NY ('''newyork4.voip.ms''') 72.251.239.207
*New York 5, NY ('''newyork5.voip.ms''') 23.29.136.28
*New York 6, NY ('''newyork6.voip.ms''') 23.29.136.29
*New York 7, NY ('''newyork7.voip.ms''') 23.29.136.38
*New York 8, NY ('''newyork8.voip.ms''') 23.29.136.40
*San Jose, CA ('''sanjose.voip.ms''') 23.246.247.146
*San Jose 2, CA ('''sanjose2.voip.ms''') 23.246.247.147
*Seattle 1, WA ('''seattle.voip.ms''') 50.23.160.53
*Seattle 2, WA ('''seattle2.voip.ms''') 50.23.149.166
*Seattle 3, WA ('''seattle3.voip.ms''') 50.23.160.54
*Tampa, FL ('''tampa.voip.ms''') 162.254.144.173
*Tampa 2, FL ('''tampa2.voip.ms''') 209.133.209.70
*Tampa 3, FL ('''tampa3.voip.ms''') 23.111.187.139
*Tampa 4, FL ('''tampa4.voip.ms''') 23.111.166.202
*Washington 1, DC ('''washington.voip.ms''') 169.62.41.187
*Washington 2, DC ('''washington2.voip.ms''') 169.62.41.189
</li>

<li style="display: inline-block; vertical-align:top;">
'''Internacional'''
*Amsterdam, NL ('''amsterdam.voip.ms''') 66.212.22.42
*London, UK ('''london.voip.ms''') 159.8.157.212
*Paris, FR ('''paris.voip.ms''') 159.8.85.180
</li>
</ul></div>

===Dominios del Servidor===

Para IOS, haga clic aquí [http://wiki.voip.ms/article/Server_Realms Server Realms] para obtener el nombre de dominio para el servidor que planea usar, esto puede diferir del nombre de dominio que se está utilizando.

= ¿Qué es un Ping? =

Ping es la herramienta estándar usada para probar la latencia (demora) en conexiones en red. Normalmente es usada para determinar si un servidor o dispositivo puede ser alcanzado a través de la red y su tiempo de latencia (tiempo que toma en enviarse un paquete a su destino y regresar a su origen) para responder.

La herramienta Ping es parte de Windows, MAC OS y Linux, también se puede encontrar en algunos ruteadores.

== ¿Cómo funciona la herramienta Ping? ==

Esta envía mensajes de petición a un una dirección de red determinada o nombres DNS en ciertos intervalos de tiempo y contabiliza el tiempo que tarda en recibirse un mensaje de respuesta. (mejor conocido como tiempo de latencia)

==¿Cómo hacer un ping en una PC?==

Hacer ping es un comando que le dice si la conexión entre su computadora y un dominio en particular está funcionando correctamente.

En Windows, seleccione Inicio> Programas> Accesorios> Símbolo del sistema. Esto le dará una ventana como la de abajo.

Ingrese la palabra ping, seguida de un espacio, luego el nombre de dominio (montreal.voip.ms) en este caso, el dominio es el nombre de nuestro servidor.

Si los resultados muestran una serie de respuestas, la conexión está funcionando. El tiempo te muestra qué tan rápida es la conexión. Si ves un error de "tiempo de espera agotado" en lugar de una respuesta, hay una falla en algún lugar entre tu computadora y el dominio.

[[File:Ping.gif|thumb|none|600px|Ping]]

== ¿Cómo enviar un ping a una MAC? ==

1- Haga click en el buscador en la barra de herramientas.

2- Haga click en aplicaciones.

3- Haga click en utilidades (usos / configuraciones).

4- Haga doble-click en utilidades de red.*

*En OS X Mavericks (10.9.x), esta aplicación de utilidad cambió de ubicación. En su lugar, inícielo desde Spotlight, presione "comando" + "barra espaciadora" o haga clic en Spotlight directamente (icono de lupa en la parte superior derecha de la pantalla), escriba "utilidad de red" y presione "regresar"

5- En la ventana de utilidades de red, haga click en el el cuadro de ping.

6- En el campo debajo "Ingresese la direccion de red para hacer ping," como montreal.voip.ms

'' Si el ping resulta no ser consistente, puede tener un problema de ''jitter'' (variación del tiempo que tardan en llegar los paquetes debido a una congestión en la red o a diferentes rutas tomadas). Para tratar este problema, puede ajustar el nivel de ''jitter'' en su configuración del dispositivo VoIP (si cuenta con esta opción). Normalmente es recomendado un ping por debajo de 150ms para tener una buena calidad de audio durante la llamada. El tiempo de latencia del servidor es importante, sin embargo hay otros factores importantes a tomar en cuenta para la calidad de las llamadas como son la pérdida de paquetes (las comunicaciones VoIP son muy sensibles a esto) y el nivel de ''jitter'' de su conexión a Internet. ''

El siguiente es el resultado de ejecutar ping con el destino losangeles.voip.ms.

#ping losangeles.voip.ms
Ping to losangeles.voip.ms [67.215.241.250] with 32 bytes de datos:
Response from 67.215.241.250: bytes=32 time=67ms TTL=52
Response from 67.215.241.250: bytes=32 time=69ms TTL=52
Response from 67.215.241.250: bytes=32 time=68ms TTL=52
Response from 67.215.241.250: bytes=32 time=67ms TTL=52
ping statistics from 67.215.241.250:
4 packets transmitted, 4 received, 0% packet lost. rtt min/avg/max/mdev = 67ms, 69ms, 67ms

Ejemplo de salida de ping en Windows:
C:\Windows\system32>ping montreal.voip.ms

Pinging montreal.voip.ms [67.205.74.184] with 32 bytes of data:
Reply from 67.205.74.184: bytes=32 time=85ms TTL=49
Reply from 67.205.74.184: bytes=32 time=86ms TTL=49
Reply from 67.205.74.184: bytes=32 time=86ms TTL=49
Reply from 67.205.74.184: bytes=32 time=85ms TTL=49

Ping statistics for 67.205.74.184:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 85ms, Maximum = 86ms, Average = 85ms

= Scripts de prueba de latencia (enviados por el usuario) =
<p> Todos los siguientes scripts fueron producidos por usuarios de voip.ms que sintieron que otros también podrían beneficiarse del resultado de sus esfuerzos. Se escribieron durante un período de años y probablemente deban ajustarse antes de usarlos, para adaptarse a los cambios en los servidores a lo largo del tiempo y los cambios en las políticas (como no probar servidores muy suscritos que no están abiertos a nuevos registros) </p>
<p> Si no está satisfecho con la seguridad de los scripts o simplemente no le gusta la forma en que aparecen sintácticamente, aún puede hacer ping manualmente a una selección de servidores y elegir un servidor en función de la mejor latencia. Los siguientes scripts son esencialmente envoltorios del comando ping que admiten listas de servidores para enviar a ping y presentar la salida en un formato legible. </p>
<p> Si cree que tiene un script más simple y limpio que funcione para otra plataforma o idioma, agréguelo a este wiki a través de un ticket de soporte.

=== Script de Bash para manejar el formato de salida de ping de Mac ===

Para hacer uso de este script (1) guárdelo como un archivo de texto sin formato (2) establezca los permisos del archivo en ejecutable (3) invoque el script
p.ej. Guarde el script a continuación usando su editor favorito como pingVoipMS.sh (2) chmod u + x pingVoipMS.sh (3) ./pingVoipMS.sh
Este es un script bash 3.x, por lo que también funciona en Linux, simplemente cambie el campo de pérdida de paquetes de ping de 7 a 6 en el ciclo final a continuación (o donde sea que el campo de pérdida esté en su formato de salida de ping). Dependiendo de su distribución, es posible que tenga que cambiar el curl a wget.

</p>
<pre>
#!/bin/bash
# Ping several servers and display Latency, Jitter and Packet Loss
# Usage: [-c <count>][-i <wait time>][-r test restricted servers][<server list file>]
#
# The optional server list text file should be formatted with one host name per line.
# The list of voip.ms servers is available at https://wiki.voip.ms/article/Choosing_Server
# If no args are supplied, this script will scrape a ping server list from voip.ms
#
USER_FILE=""
COUNT=3; INTERVAL=5; RESTRICTED=0
restrictedList=(atlanta.voip.ms chicago.voip.ms
montreal.voip.ms montreal2.voip.ms montreal3.voip.ms montreal4.voip.ms
newyork.voip.ms newyork4.voip.ms seattle.voip.ms
toronto.voip.ms toronto2.voip.ms toronto3.voip.ms toronto4.voip.ms)

# Handle any passed in script arguments
while getopts c:i:r parm
do
case $parm in
c)count_opt=$OPTARG;;
i)interval_opt=$OPTARG;;
r)RESTRICTED=1;;
*)echo -e "Invalid arg\nUsage:\t[ -c <count of ECHO_REQUESTs to Tx, default 3> ] \
\n\t[ -i <wait time (s) between datagrams, default 5> ] \
\n\t[ -r ] Include restricted servers in latency test \
\n\t[FILE <ping server list> ]";exit 1;;
esac
done

# Test if an option was specified and whether it's a +ve non-zero integer
[[ -n $count_opt && ($count_opt =~ ^[[:digit:]]+$) && $count_opt -gt 0 ]] &&
COUNT=$count_opt
[[ -n $interval_opt && ($interval_opt =~ ^[[:digit:]]+$) && $interval_opt -gt 0 ]] &&
INTERVAL=$interval_opt

shift $((OPTIND - 1))

# Validate supplied file (server list)
[[ -n $1 && ! (-f $1 && -r $1) ]] &&
{ echo "\"$1\" file does not exist or is not readable"; exit 1; }
[[ -n $1 && -f $1 && -r $1 ]] && USER_FILE="$1"

if [[ -n $USER_FILE ]]
then
# Bash 3.x in macOS does not support readarray, need to do cumbersome array loops instead
while IFS= read -r servers; do
serverList+=( "$servers" )
done < <(grep -Eo '^\b[[:alpha:]]+?[[:alnum:]]\.voip\.ms\b$' "$USER_FILE" | \
grep -v '^\s*#' | awk NF | sort)
else
# N.B. The script looks for the html boldface tags <b> </b> inside a bracket
# If the website alters and the parse fails, manually create the list and
# supply as a script arg (or perhaps update the parsing to work again :)
while IFS= read -r servers; do
serverList+=( "$servers" )
done < <(curl -sm 10 https://wiki.voip.ms/article/Choosing_Server | \
grep -E '(<b>[[:alpha:]]+?[[:alnum:]]\.voip\.ms</b>)' | \
tr "<>" " " | awk '{print $(NF-3)}' | sort )
fi

# Newer voip.ms clients can't register onto these over-subscribed servers
# Don't test the restricted list unless explicitly asked (with the -r cmd line option)
if [[ $RESTRICTED -eq 0 ]]
then
for server in "${restrictedList[@]}"
do
ix=$(printf "%s\n" "${serverList[@]}" | grep -n "^${server}" | cut -d ":" -f1)
while IFS= read -ra idx; do
keys+=( "${idx[@]}" )
done < <([[ $ix -gt 0 ]] && echo $((ix-1)))
done
for ((i=${#keys[@]} - 1; i >= 0; i--)); do unset "serverList[keys[i]]"; done
fi

if [[ ${#serverList[@]} -eq 0 ]]
then
echo "No unrestricted Voip.ms servers could be found, please supply a server list"
exit 1
fi

runTime=$((COUNT * INTERVAL * ${#serverList[@]}))

echo "PING will send $COUNT packet(s) with a wait of $INTERVAL sec(s) between each packet"
echo "Change the PING options by invoking this script with -c and/or -i, default \"-c 3 -i 5\""
echo "Over $((${#serverList[@]})) server(s) the estimated script Run Time will be $runTime seconds"
echo "================================================================"
printf "%-20s %-18s %7s %8s %6s %s\n" "VoIP Server" "IP Address" "Latency" "Jitter" "Loss" "Countdown"
echo "================================================================ (seconds)"

for myLn in "${serverList[@]}"
do
while IFS=$'\n' read -r pings; do
pingList+=( "$pings" )
printf "%-64s %5d %2d/%-2d\n" "$pings" \
"$((runTime - COUNT * INTERVAL * ${#pingList[@]}))" \
"${#pingList[@]}" "${#serverList[@]}"
done < <( ping -c "$COUNT" -i "$INTERVAL" -q "$myLn" | awk \
'
/^PING / {myH=$2}
/^PING / {
IP = substr($3,2,15)
split(IP,myIP,")") }
/packet loss/ {myPL=$7}
/min\/avg\/max/ {
split($4,myS,"/")
printf("%-20s %-18s %7.3f %8.3f %6s\n",
myH, myIP[1], myS[2], myS[4], myPL ) }
' )
done

echo "================================================================"
echo -e "\nMost appropriate server listed in order of best latency\n"
echo "================================================================"
printf "%-20s %-18s %7s %8s %6s\n" "VoIP Server" "IP Address" "Latency" "Jitter" "Loss"
echo "================================================================"
printf "%s\n" "${pingList[@]}" | LC_ALL=C sort -n -k 3,3 -k 5,5 -k 4,4 | \
awk '{printf("%s $%2d$\n",$0, NR)}'
echo "================================================================"
</pre>

=== Perl Script ===
Lista de ping de servidores voip.ms round robin con archivo csv de salida opcional.

# usage ping_voip.ms.pl <number of times> <seconds in between> <output.csv>
use Net::Ping;
use Time::HiRes;
use strict;

# input list
my @hosts = qw(
atlanta.voip.ms
atlanta2.voip.ms
chicago.voip.ms
chicago2.voip.ms
chicago3.voip.ms
chicago4.voip.ms
dallas.voip.ms
denver.voip.ms
denver2.voip.ms
houston.voip.ms
losangeles.voip.ms
losangeles2.voip.ms
newyork.voip.ms
newyork2.voip.ms
newyork3.voip.ms
newyork4.voip.ms
seattle.voip.ms
seattle2.voip.ms
seattle3.voip.ms
tampa.voip.ms
washington.voip.ms
washington2.voip.ms
montreal.voip.ms
montreal2.voip.ms
montreal3.voip.ms
montreal4.voip.ms
toronto2.voip.ms
toronto3.voip.ms
toronto4.voip.ms
toronto.voip.ms
london.voip.ms
);

$| = 1; #autoflush
# High precision syntax (requires Time::HiRes)
my $p = Net::Ping->new("icmp",1);
$p->hires();
my $max_name_length = (reverse sort { $a <=> $b } map { length($_) } @hosts)[0];
my $count = 4; # number of times to ping
my $interval = 5; # seconds between ping rounds
my $output_file = "";
my @data;

# check for arguments
my $num_args = @ARGV;
if ($num_args >= 1) {$count = $ARGV[0];}
if ($num_args >= 2) {$interval = $ARGV[1];}
if ($num_args >= 3) {$output_file = $ARGV[2];}

# check argument validity
$0 =~ /^.*\\(.*)$/;
my $script = $1;
if ($count !~ /^\d+$/ or $interval !~ /^\d+$/) {die "Usage: $script <number of rounds> <seconds between rounds> <output.csv>\n";}
if (length($output_file) > 0 and $output_file !~ /\.csv$/) {$output_file .= ".csv";}

# main loop
for my $i (1..$count)
{
sleep $interval unless $i == 1;
print "Round $i\n";
my $host_num=0;
foreach my $host (@hosts)
{
(my $ret, my $duration, my $ip) = $p->ping($host);
$ip =~ /(\d+)\.(\d+)\.(\d+)\.(\d+)/;
if ($ret)
{
printf("%*s [ip: %3s.%3s.%3s.%3s] is alive (%6.2f ms)\n", $max_name_length, $host, $1, $2, $3, $4, $duration*1000);
$data[$host_num][$i]=$duration*1000;
}
else
{
printf("%*s [ip: %3s.%3s.%3s.%3s] is dead\n", $max_name_length, $host, $1, $2, $3, $4);
}
$host_num++;
}
print "\n";
}
$p->close();

# if output file name given
if (length($output_file)>0)
{
# print output to file
open FILE, ">$output_file" or die "$!\n";

# print column headers
print FILE "Server\\Round";
for my $i (1..$count)
{
print FILE ", $i";
}
print FILE ", Average\n";

# print data
my $i = 0;
foreach my $host (@hosts)
{
print FILE "$host";
my $sum = 0;
for my $j (1..$count)
{
$sum += $data[$i][$j];
printf FILE ", %8.4f",$data[$i][$j];
}
printf FILE ", %8.4f\n",$sum/$count;
$i++;
}

close FILE;
print "Data written to $output_file\n";
}

# print summary to screen
my $i = 0;
printf("%-*s Average (ms)\n", $max_name_length, "Server");
foreach my $host (@hosts)
{
my $sum = 0;
for my $j (1..$count)
{
$sum += $data[$i][$j];
}
printf("%-*s %8.4f\n", $max_name_length+1, $host, $sum/$count);
$i++;
}

Salidas:
Round 1
atlanta.voip.ms [ip: 174. 34.146.162] is alive ( 88.97 ms)
atlanta2.voip.ms [ip: 72. 9.246.170] is alive ( 92.99 ms)
chicago.voip.ms [ip: 208.100. 39. 52] is alive ( 49.70 ms)
chicago2.voip.ms [ip: 208.100. 39. 53] is alive ( 59.76 ms)
chicago3.voip.ms [ip: 208.100. 39. 54] is alive ( 59.53 ms)
chicago4.voip.ms [ip: 208.100. 39. 55] is alive ( 49.73 ms)
dallas.voip.ms [ip: 74. 54. 54.178] is alive ( 94.99 ms)
denver.voip.ms [ip: 173.248.161. 90] is alive ( 94.05 ms)
denver2.voip.ms [ip: 173.248.159.210] is alive ( 85.13 ms)
houston.voip.ms [ip: 209. 62. 1. 2] is alive (102.87 ms)
losangeles.voip.ms [ip: 96. 44.149.186] is alive ( 64.92 ms)
losangeles2.voip.ms [ip: 96. 44.149.202] is alive ( 63.41 ms)
newyork.voip.ms [ip: 74. 63. 41.218] is alive (131.75 ms)
newyork2.voip.ms [ip: 107. 6. 67.236] is alive (120.64 ms)
newyork3.voip.ms [ip: 107. 6. 67.237] is alive (120.49 ms)
newyork4.voip.ms [ip: 107. 6. 67.238] is alive (111.43 ms)
seattle.voip.ms [ip: 50. 23.160. 50] is alive ( 94.25 ms)
seattle2.voip.ms [ip: 50. 23.160. 51] is alive ( 95.86 ms)
seattle3.voip.ms [ip: 50. 23.160. 52] is alive ( 90.85 ms)
tampa.voip.ms [ip: 68.233.226. 97] is alive (123.29 ms)
washington.voip.ms [ip: 208. 43.234.226] is alive ( 98.71 ms)
washington2.voip.ms [ip: 208. 43.234.227] is alive (101.19 ms)
montreal.voip.ms [ip: 67.205. 74.184] is alive ( 81.82 ms)
montreal2.voip.ms [ip: 67.205. 74.187] is alive ( 86.13 ms)
montreal3.voip.ms [ip: 72. 55.168. 18] is alive ( 77.09 ms)
montreal4.voip.ms [ip: 67.205. 74.179] is alive ( 96.18 ms)
toronto2.voip.ms [ip: 184. 75.215.114] is alive (103.70 ms)
toronto3.voip.ms [ip: 184. 75.215.146] is alive (131.27 ms)
toronto4.voip.ms [ip: 184. 75.213.210] is alive (125.13 ms)
toronto.voip.ms [ip: 184. 75.215.106] is alive (103.26 ms)
london.voip.ms [ip: 5. 77. 36.136] is alive (152.77 ms)

Round 2
atlanta.voip.ms [ip: 174. 34.146.162] is alive ( 88.14 ms)
atlanta2.voip.ms [ip: 72. 9.246.170] is alive ( 92.86 ms)
chicago.voip.ms [ip: 208.100. 39. 52] is alive ( 50.03 ms)
chicago2.voip.ms [ip: 208.100. 39. 53] is alive ( 59.44 ms)
chicago3.voip.ms [ip: 208.100. 39. 54] is alive ( 59.33 ms)
chicago4.voip.ms [ip: 208.100. 39. 55] is alive ( 50.22 ms)
dallas.voip.ms [ip: 74. 54. 54.178] is alive ( 95.58 ms)
denver.voip.ms [ip: 173.248.161. 90] is alive ( 95.94 ms)
denver2.voip.ms [ip: 173.248.159.210] is alive ( 85.29 ms)
houston.voip.ms [ip: 209. 62. 1. 2] is alive (102.73 ms)
losangeles.voip.ms [ip: 96. 44.149.186] is alive ( 65.59 ms)
losangeles2.voip.ms [ip: 96. 44.149.202] is alive ( 64.27 ms)
newyork.voip.ms [ip: 74. 63. 41.218] is alive (112.74 ms)
newyork2.voip.ms [ip: 107. 6. 67.236] is alive (121.22 ms)
newyork3.voip.ms [ip: 107. 6. 67.237] is alive (121.34 ms)
newyork4.voip.ms [ip: 107. 6. 67.238] is alive (110.75 ms)
seattle.voip.ms [ip: 50. 23.160. 50] is alive ( 94.06 ms)
seattle2.voip.ms [ip: 50. 23.160. 51] is alive ( 95.33 ms)
seattle3.voip.ms [ip: 50. 23.160. 52] is alive ( 91.58 ms)
tampa.voip.ms [ip: 68.233.226. 97] is alive (122.94 ms)
washington.voip.ms [ip: 208. 43.234.226] is alive ( 98.28 ms)
washington2.voip.ms [ip: 208. 43.234.227] is alive (101.40 ms)
montreal.voip.ms [ip: 67.205. 74.184] is alive ( 81.91 ms)
montreal2.voip.ms [ip: 67.205. 74.187] is alive ( 85.64 ms)
montreal3.voip.ms [ip: 72. 55.168. 18] is alive ( 75.15 ms)
montreal4.voip.ms [ip: 67.205. 74.179] is alive ( 96.79 ms)
toronto2.voip.ms [ip: 184. 75.215.114] is alive (103.10 ms)
toronto3.voip.ms [ip: 184. 75.215.146] is alive (150.85 ms)
toronto4.voip.ms [ip: 184. 75.213.210] is alive (138.40 ms)
toronto.voip.ms [ip: 184. 75.215.106] is alive (103.45 ms)
london.voip.ms [ip: 5. 77. 36.136] is alive (170.79 ms)

Round 3
atlanta.voip.ms [ip: 174. 34.146.162] is alive ( 88.76 ms)
atlanta2.voip.ms [ip: 72. 9.246.170] is alive ( 92.86 ms)
chicago.voip.ms [ip: 208.100. 39. 52] is alive ( 49.65 ms)
chicago2.voip.ms [ip: 208.100. 39. 53] is alive ( 60.01 ms)
chicago3.voip.ms [ip: 208.100. 39. 54] is alive ( 59.05 ms)
chicago4.voip.ms [ip: 208.100. 39. 55] is alive ( 49.53 ms)
dallas.voip.ms [ip: 74. 54. 54.178] is alive ( 95.82 ms)
denver.voip.ms [ip: 173.248.161. 90] is alive ( 95.02 ms)
denver2.voip.ms [ip: 173.248.159.210] is alive ( 85.60 ms)
houston.voip.ms [ip: 209. 62. 1. 2] is alive (103.35 ms)
losangeles.voip.ms [ip: 96. 44.149.186] is alive ( 65.79 ms)
losangeles2.voip.ms [ip: 96. 44.149.202] is alive ( 64.05 ms)
newyork.voip.ms [ip: 74. 63. 41.218] is alive (113.01 ms)
newyork2.voip.ms [ip: 107. 6. 67.236] is alive (121.41 ms)
newyork3.voip.ms [ip: 107. 6. 67.237] is alive (122.23 ms)
newyork4.voip.ms [ip: 107. 6. 67.238] is alive (110.62 ms)
seattle.voip.ms [ip: 50. 23.160. 50] is alive ( 93.65 ms)
seattle2.voip.ms [ip: 50. 23.160. 51] is alive ( 95.19 ms)
seattle3.voip.ms [ip: 50. 23.160. 52] is alive ( 90.75 ms)
tampa.voip.ms [ip: 68.233.226. 97] is alive (125.12 ms)
washington.voip.ms [ip: 208. 43.234.226] is alive ( 98.19 ms)
washington2.voip.ms [ip: 208. 43.234.227] is alive (101.98 ms)
montreal.voip.ms [ip: 67.205. 74.184] is alive ( 80.16 ms)
montreal2.voip.ms [ip: 67.205. 74.187] is alive ( 87.16 ms)
montreal3.voip.ms [ip: 72. 55.168. 18] is alive ( 76.54 ms)
montreal4.voip.ms [ip: 67.205. 74.179] is alive ( 97.51 ms)
toronto2.voip.ms [ip: 184. 75.215.114] is alive (104.18 ms)
toronto3.voip.ms [ip: 184. 75.215.146] is alive (142.81 ms)
toronto4.voip.ms [ip: 184. 75.213.210] is alive (138.95 ms)
toronto.voip.ms [ip: 184. 75.215.106] is alive (103.78 ms)
london.voip.ms [ip: 5. 77. 36.136] is alive (153.14 ms)

Round 4
atlanta.voip.ms [ip: 174. 34.146.162] is alive ( 89.19 ms)
atlanta2.voip.ms [ip: 72. 9.246.170] is alive ( 92.98 ms)
chicago.voip.ms [ip: 208.100. 39. 52] is alive ( 49.21 ms)
chicago2.voip.ms [ip: 208.100. 39. 53] is alive ( 60.50 ms)
chicago3.voip.ms [ip: 208.100. 39. 54] is alive ( 59.68 ms)
chicago4.voip.ms [ip: 208.100. 39. 55] is alive ( 50.18 ms)
dallas.voip.ms [ip: 74. 54. 54.178] is alive ( 93.93 ms)
denver.voip.ms [ip: 173.248.161. 90] is alive ( 94.22 ms)
denver2.voip.ms [ip: 173.248.159.210] is alive ( 85.10 ms)
houston.voip.ms [ip: 209. 62. 1. 2] is alive (103.67 ms)
losangeles.voip.ms [ip: 96. 44.149.186] is alive ( 65.58 ms)
losangeles2.voip.ms [ip: 96. 44.149.202] is alive ( 63.60 ms)
newyork.voip.ms [ip: 74. 63. 41.218] is alive (114.76 ms)
newyork2.voip.ms [ip: 107. 6. 67.236] is alive (120.44 ms)
newyork3.voip.ms [ip: 107. 6. 67.237] is alive (121.05 ms)
newyork4.voip.ms [ip: 107. 6. 67.238] is alive (110.51 ms)
seattle.voip.ms [ip: 50. 23.160. 50] is alive ( 94.04 ms)
seattle2.voip.ms [ip: 50. 23.160. 51] is alive ( 96.92 ms)
seattle3.voip.ms [ip: 50. 23.160. 52] is alive ( 91.23 ms)
tampa.voip.ms [ip: 68.233.226. 97] is alive (123.28 ms)
washington.voip.ms [ip: 208. 43.234.226] is alive ( 98.45 ms)
washington2.voip.ms [ip: 208. 43.234.227] is alive (100.94 ms)
montreal.voip.ms [ip: 67.205. 74.184] is alive ( 82.33 ms)
montreal2.voip.ms [ip: 67.205. 74.187] is alive ( 85.02 ms)
montreal3.voip.ms [ip: 72. 55.168. 18] is alive ( 76.85 ms)
montreal4.voip.ms [ip: 67.205. 74.179] is alive ( 96.32 ms)
toronto2.voip.ms [ip: 184. 75.215.114] is alive (104.22 ms)
toronto3.voip.ms [ip: 184. 75.215.146] is alive (148.33 ms)
toronto4.voip.ms [ip: 184. 75.213.210] is alive (141.61 ms)
toronto.voip.ms [ip: 184. 75.215.106] is alive (105.91 ms)
london.voip.ms [ip: 5. 77. 36.136] is alive (152.85 ms)

Server Average (ms)
atlanta.voip.ms 88.7630
atlanta2.voip.ms 92.9233
chicago.voip.ms 49.6477
chicago2.voip.ms 59.9305
chicago3.voip.ms 59.3972
chicago4.voip.ms 49.9152
dallas.voip.ms 95.0790
denver.voip.ms 94.8077
denver2.voip.ms 85.2797
houston.voip.ms 103.1562
losangeles.voip.ms 65.4693
losangeles2.voip.ms 63.8347
newyork.voip.ms 118.0643
newyork2.voip.ms 120.9265
newyork3.voip.ms 121.2778
newyork4.voip.ms 110.8275
seattle.voip.ms 93.9993
seattle2.voip.ms 95.8267
seattle3.voip.ms 91.1035
tampa.voip.ms 123.6570
washington.voip.ms 98.4065
washington2.voip.ms 101.3774
montreal.voip.ms 81.5525
montreal2.voip.ms 85.9863
montreal3.voip.ms 76.4058
montreal4.voip.ms 96.7013
toronto2.voip.ms 103.7986
toronto3.voip.ms 143.3156
toronto4.voip.ms 136.0254
toronto.voip.ms 104.1012
london.voip.ms 157.3885

=== Powershell ===

Diciembre 2017 - Un problema en el codigo del dominio washington2.voip.ms lo mostraba como el mejor servidor, esto fue corregido.
<pre>
# Usage: Copy and paste the following code into a powershell window
# To run it from a command prompt, save this file with extension ps1.
# Then run Powershell.exe -file "pathtothisscript.ps1"
Clear-Variable best* -Scope Global #Clear the best* variables in case you run it more than once...
#Get the list of servers into an array
$Servers =
@("amsterdam.voip.ms","atlanta.voip.ms","atlanta2.voip.ms","chicago.voip.ms","chicago2.voip.ms","chicago3.voip.ms",
"chicago4.voip.ms","dallas.voip.ms","dallas2.voip.ms","denver.voip.ms","denver2.voip.ms","houston.voip.ms",
"houston2.voip.ms","london.voip.ms","losangeles.voip.ms","losangeles2.voip.ms","montreal.voip.ms",
"montreal2.voip.ms","montreal3.voip.ms","montreal4.voip.ms","montreal5.voip.ms","montreal6.voip.ms","montreal7.voip.ms",
"montreal8.voip.ms","newyork.voip.ms","newyork2.voip.ms","newyork3.voip.ms","newyork4.voip.ms","newyork5.voip.ms",
"newyork6.voip.ms","newyork7.voip.ms","newyork8.voip.ms","paris.voip.ms","sanjose.voip.ms","sanjose2.voip.ms",
"seattle.voip.ms","seattle2.voip.ms","seattle3.voip.ms","tampa.voip.ms","tampa2.voip.ms","toronto.voip.ms",
"toronto2.voip.ms","toronto3.voip.ms","toronto4.voip.ms","toronto5.voip.ms","toronto6.voip.ms","toronto7.voip.ms",
"toronto8.voip.ms","vancouver.voip.ms","vancouver2.voip.ms","washington.voip.ms","washington2.voip.ms")
$k = 0 #Counting variable so we know what server number we are testing
#num of servers to test
$servercount = $servers.length
#Do the following code for each server in our array
ForEach($server in $servers)
{
#Add one to the counting variable....we are on server #1...then server 2, then server 3 etc...
$k++
#Update the progress bar
Write-Progress -Activity "Testing Server: ${server}" -status "Testing Server $k out of $servercount" -percentComplete ($k / $servercount*100)
#Counting variable for number of times we tried to ping a given server
$i = 0
Do{
#assume a failure
$pingsuccess = $false
$i++ #Add one to the counting variable.....1st try....2nd try....3rd try etc...
Try{
#Try to ping
$currentping = (test-connection $server -count 1 -ErrorAction Stop).responsetime
#If success full, set success variable
$pingsuccess = $true
}
#Catch the failure and set the success variable to false
Catch {
$pingsuccess = $false
}
}
#Try everything between Do and While up to 5 times, or while $pingsuccess is not true
While($pingsuccess -eq $false -and $i -le 5)
#Compare the last ping test with the best known ping test....if there is no known best ping test, assume this one is the best $bestping = $currentping
If($pingsuccess -and ($currentping -lt $bestping -or (!($bestping)))){
#If this is the best ping...save it
$bestserver = $server #Save the best server
$bestping = $currentping #Save the best ping results
}
write-host "tested: $server at $currentping ms after $i attempts" #write the results of the test for this server
}
write-host "`r`n The server with the best ping is: $bestserver at $bestping ms`r`n" #write the end result
Pause
</pre>

=== Linux Shell Script ===
Hace ping a varios servidores voip.ms

#!/bin/sh
# Ping several servers and display Latency, Jitter and Packet Loss
#
# First, create a text file with all servers you want to ping - one host name per line.
# The list of voip.ms servers is available at http://wiki.voip.ms/article/Choosing_Server
myHF="voip_ping_hosts.txt"
# Sample file:
# toronto.voip.ms
# montreal.voip.ms
# seattle.voip.ms
# chicago.voip.ms
# newyork.voip.ms
#
echo "============================================"
printf "%-20s %7s %8s %6s\n" "VoIP Server" "Latency" "Jitter" "Loss"
echo "============================================"
cat ${myHF} |\
while read myLn
do
ping -c 3 -i 5 -q $myLn |\
awk '/^PING / {myH=$2}
/packet loss/ {myPL=$6}
/min\/avg\/max/ {
split($4,myS,"/")
printf( "%-20s %3.1f %1.3f %4s\n", myH, myS[2], myS[4], myPL)
}'
done
echo "============================================"

Salidas:

============================================
VoIP Server Latency Jitter Loss
============================================
toronto.voip.ms 68.3 0.439 0%
montreal.voip.ms 89.6 0.197 0%
seattle.voip.ms 71.2 0.387 0%
chicago.voip.ms 71.6 0.084 0%
newyork.voip.ms 79.1 0.411 0%
============================================

= La Latencia y su importancia =

La latencia es muy importante para Voip, esto determinará el tiempo que tardará la transmisión del paquete de datos en llegar al destino. Una latencia alta provocará un retraso y ecos en la comunicación.

La latencia se mide en milisegundos (ms) Por ejemplo: una latencia de 150 ms es apenas perceptible, por lo que es aceptable. Más alto que eso, la calidad comienza a sufrir. Cuando supera los 300 ms, se vuelve inaceptable.

[[category:Guías]]

Choisir un serveur

2021-03-31T13:05:15Z

B13n:

[[File:ChooseServerImg.png|thumb|none|1280px|VoIP.ms servers]]

{| class="wikitable"
|+
|-
! Article in English !! Artículo en Español
|-
| [https://wiki.voip.ms/article/Choosing_Server English] || [https://wiki.voip.ms/article/Elegir_servidor Español]
|}

= Choisir un serveur =

[http://www.voip.ms VoIP.ms] propose de nombreux serveurs PoP différents, mais lequel choisir? Une des conceptions erronées est que vous devriez choisir le serveur PoP le plus proche de votre emplacement, mais cela n'est pas nécessaire la plupart du temps.

Par exemple, si vous êtes aux États-Unis, l'un des serveurs américains fournira une très bonne latence et une très bonne qualité de service. Le serveur le plus récent d'une ville est indiqué par le numéro le plus élevé associé au nom du serveur, car ils sont classés par ordre croissant.

Il convient également de noter qu'il existe un outil réseau qui vous aidera à choisir le serveur que vous souhaitez utiliser, généralement appelé "ping", qui vous fournira la latence entre vous et le serveur. Par conséquent, le serveur qui vous offre le moins de latence doit être utilisé.

'''Note:''' Veuillez garder à l'esprit que certains serveurs peuvent ne pas être disponibles pour que votre numéro DID soit utilisé comme POP (point de présence) dans la section
'''Gestion des DID'''. Assurez-vous aussi que votre appareil SIP/IAX et votre numéro DID pointent vers le même serveur POP.

=== Adresses IPs ===

<div><ul>
<li style="display: inline-block; vertical-align:top;">
'''Canada'''
*Montreal 1, QC ('''montreal.voip.ms''') 192.175.96.73
*Montreal 2, QC ('''montreal2.voip.ms''') 192.175.96.74
*Montreal 3, QC ('''montreal3.voip.ms''') 192.175.96.68
*Montreal 4, QC ('''montreal4.voip.ms''') 67.205.74.179
*Montreal 5, QC ('''montreal5.voip.ms''') 192.175.96.69
*Montreal 6, QC ('''montreal6.voip.ms''') 192.175.96.70
*Montreal 7, QC ('''montreal7.voip.ms''') 192.175.96.71
*Montreal 8, QC ('''montreal8.voip.ms''') 192.175.96.72
*Montreal 9, QC ('''montreal9.voip.ms''') 67.205.74.184
*Montreal 10, QC ('''montreal10.voip.ms''') 67.205.74.187
*Toronto 1, ON ('''toronto.voip.ms''') 158.85.70.148
*Toronto 2, ON ('''toronto2.voip.ms''') 158.85.70.149
*Toronto 3, ON ('''toronto3.voip.ms''') 158.85.70.150
*Toronto 4, ON ('''toronto4.voip.ms''') 158.85.70.151
*Toronto 5, ON ('''toronto5.voip.ms''') 184.75.215.106
*Toronto 6, ON ('''toronto6.voip.ms''') 184.75.215.114
*Toronto 7, ON ('''toronto7.voip.ms''') 184.75.215.146
*Toronto 8, ON ('''toronto8.voip.ms''') 184.75.213.210
*Toronto 9, ON ('''toronto9.voip.ms''') 158.85.70.154
*Toronto 10, ON ('''toronto10.voip.ms''') 158.85.70.158
*Vancouver 1, BC ('''vancouver.voip.ms''') 162.213.157.220
*Vancouver 2, BC ('''vancouver2.voip.ms''') 162.213.157.117
*Vancouver 3, BC ('''vancouver3.voip.ms''') 162.213.157.82
</li>

<li style="display: inline-block; vertical-align:top;">
'''États-Unis'''
*Atlanta 1, GA ('''atlanta.voip.ms''') 75.127.65.130
*Atlanta 2, GA ('''atlanta2.voip.ms''') 209.217.224.50
*Chicago 1, IL ('''chicago.voip.ms''') 69.162.175.27
*Chicago 2, IL ('''chicago2.voip.ms''') 69.162.175.28
*Chicago 3, IL ('''chicago3.voip.ms''') 69.162.175.29
*Chicago 4, IL ('''chicago4.voip.ms''') 208.100.39.55
*Chicago 5, IL ('''chicago5.voip.ms''') 50.31.115.149
*Chicago 6, IL ('''chicago6.voip.ms''') 50.31.115.150
*Chicago 7, IL ('''chicago7.voip.ms''') 50.31.115.151
*Dallas, TX ('''dallas.voip.ms''') 158.85.149.162
*Dallas 2, TX ('''dallas2.voip.ms''') 158.85.149.163
*Denver 1, CO ('''denver.voip.ms''') 23.239.211.90
*Denver 2, CO ('''denver2.voip.ms''') 64.27.52.226
*Houston, TX ('''houston.voip.ms''') 173.193.85.18
*Houston 2, TX ('''houston2.voip.ms''') 173.193.85.19
*Los Angeles 1, CA ('''losangeles.voip.ms''') 96.44.149.186
*Los Angeles 2, CA ('''losangeles2.voip.ms''') 96.44.149.202
*Los Angeles 3, CA ('''losangeles3.voip.ms''') 64.188.6.162
*Los Angeles 4, CA ('''losangeles4.voip.ms''') 64.188.6.170
*New York 1, NY ('''newyork.voip.ms''') 72.251.239.196
*New York 2, NY ('''newyork2.voip.ms''') 72.251.239.205
*New York 3, NY ('''newyork3.voip.ms''') 72.251.239.206
*New York 4, NY ('''newyork4.voip.ms''') 72.251.239.207
*New York 5, NY ('''newyork5.voip.ms''') 23.29.136.28
*New York 6, NY ('''newyork6.voip.ms''') 23.29.136.29
*New York 7, NY ('''newyork7.voip.ms''') 23.29.136.38
*New York 8, NY ('''newyork8.voip.ms''') 23.29.136.40
*San Jose, CA ('''sanjose.voip.ms''') 23.246.247.146
*San Jose 2, CA ('''sanjose2.voip.ms''') 23.246.247.147
*Seattle 1, WA ('''seattle.voip.ms''') 50.23.160.53
*Seattle 2, WA ('''seattle2.voip.ms''') 50.23.149.166
*Seattle 3, WA ('''seattle3.voip.ms''') 50.23.160.54
*Tampa, FL ('''tampa.voip.ms''') 162.254.144.173
*Tampa 2, FL ('''tampa2.voip.ms''') 209.133.209.70
*Tampa 3, FL ('''tampa3.voip.ms''') 23.111.187.139
*Tampa 4, FL ('''tampa4.voip.ms''') 23.111.166.202
*Washington 1, DC ('''washington.voip.ms''') 169.62.41.187
*Washington 2, DC ('''washington2.voip.ms''') 169.62.41.189
</li>

<li style="display: inline-block; vertical-align:top;">
'''Internationaux'''
*Amsterdam, NL ('''amsterdam.voip.ms''') 66.212.22.42
*London, UK ('''london.voip.ms''') 159.8.157.212
*Paris, FR ('''paris.voip.ms''') 159.8.85.180
</li>
</ul></div>

=== Serveur Realms ===

Pour IOS, s'il vous plaît utiliser le lien [http://wiki.voip.ms/article/Server_Realms Serveur Realms] pour obtenir le nom du serveur Realms que vous prévoyez utiliser, cela peut être différent du nom de domaine utilisé.

= Qu'est-ce qu'un ping? =

Un Ping est un outil standard utilisé pour tester les connexions réseau. Il est principalement utilisé pour déterminer si un serveur ou un périphérique peut être atteint sur le réseau et la latence de la réponse (le temps qu'il faut pour envoyer un paquet à la destination souhaitée et pour qu'il vous revienne sur votre ordinateur).

Les outils Ping font partie de Windows, Mac OS X et Linux ainsi que de certains routeurs.

== Comment fonctionne le ping? ==

Il envoie des messages de demande à une adresse réseau cible ou à des noms DNS à intervalle régulier et mesure le temps nécessaire à un message pour s'y rendre et revenir (mieux connu sous le nom de latence).

= La latence et son importance =

La latence est très importante pour la Voix sur IP, cela déterminera le temps nécessaire à la transmission du paquet de données pour atteindre la destination. Une latence élevée entraînera un retard et des échos dans la communication.

La latence se mesure en millisecondes (ms) Par exemple: une latence de 150ms est à peine perceptible, donc acceptable. Avec une valeur plus haute que celle-ci, la qualité de l'appel commence à être affectée. Lorsqu'elle dépasse 300 ms, cela devient inacceptable.

[[category:guides]]

Choosing Server

2021-03-31T13:04:52Z

B13n:

[[File:ChooseServerImg.png|thumb|none|1280px|VoIP.ms servers]]

{| class="wikitable"
|+
|-
! Article en Français !! Artículo en Español
|-
| [https://wiki.voip.ms/article/Choisir_un_serveur Français] ||
[https://wiki.voip.ms/article/Elegir_servidor Español]
|}

= Choosing a Server =

[http://www.voip.ms VoIP.ms] offers many different servers, but which one should you choose? One misconception is that you should pick the closest to your location, however this is not needed most of the time. For example, if you are in the USA, any of the US servers will provide a really good latency and service quality. The newest server within a city is indicated with the highest number attached to the name, as they are classified in ascending order. Also worth noting is that there is a network tool that will help you when deciding which server you want to use, generally named a "ping", which will provide you the latency between you and the server. Therefore the server which provides you less latency should be used.

'''Note:''' Please bear in mind that some servers might not be available for your DID number to be used as POP (Point of presence) at the ''Manage DIDs'' section.
Make sure that your SIP/IAX device and your phone number are pointing to the same server.

=== IPs ===

<div><ul>
<li style="display: inline-block; vertical-align:top;">
'''Canada'''
*Montreal 1, QC ('''montreal.voip.ms''') 192.175.96.73
*Montreal 2, QC ('''montreal2.voip.ms''') 192.175.96.74
*Montreal 3, QC ('''montreal3.voip.ms''') 192.175.96.68
*Montreal 4, QC ('''montreal4.voip.ms''') 67.205.74.179
*Montreal 5, QC ('''montreal5.voip.ms''') 192.175.96.69
*Montreal 6, QC ('''montreal6.voip.ms''') 192.175.96.70
*Montreal 7, QC ('''montreal7.voip.ms''') 192.175.96.71
*Montreal 8, QC ('''montreal8.voip.ms''') 192.175.96.72
*Montreal 9, QC ('''montreal9.voip.ms''') 67.205.74.184
*Montreal 10, QC ('''montreal10.voip.ms''') 67.205.74.187
*Toronto 1, ON ('''toronto.voip.ms''') 158.85.70.148
*Toronto 2, ON ('''toronto2.voip.ms''') 158.85.70.149
*Toronto 3, ON ('''toronto3.voip.ms''') 158.85.70.150
*Toronto 4, ON ('''toronto4.voip.ms''') 158.85.70.151
*Toronto 5, ON ('''toronto5.voip.ms''') 184.75.215.106
*Toronto 6, ON ('''toronto6.voip.ms''') 184.75.215.114
*Toronto 7, ON ('''toronto7.voip.ms''') 184.75.215.146
*Toronto 8, ON ('''toronto8.voip.ms''') 184.75.213.210
*Toronto 9, ON ('''toronto9.voip.ms''') 158.85.70.154
*Toronto 10, ON ('''toronto10.voip.ms''') 158.85.70.158
*Vancouver 1, BC ('''vancouver.voip.ms''') 162.213.157.220
*Vancouver 2, BC ('''vancouver2.voip.ms''') 162.213.157.117
*Vancouver 3, BC ('''vancouver3.voip.ms''') 162.213.157.82
</li>

<li style="display: inline-block; vertical-align:top;">
'''United States'''
*Atlanta 1, GA ('''atlanta.voip.ms''') 75.127.65.130
*Atlanta 2, GA ('''atlanta2.voip.ms''') 209.217.224.50
*Chicago 1, IL ('''chicago.voip.ms''') 69.162.175.27
*Chicago 2, IL ('''chicago2.voip.ms''') 69.162.175.28
*Chicago 3, IL ('''chicago3.voip.ms''') 69.162.175.29
*Chicago 4, IL ('''chicago4.voip.ms''') 208.100.39.55
*Chicago 5, IL ('''chicago5.voip.ms''') 50.31.115.149
*Chicago 6, IL ('''chicago6.voip.ms''') 50.31.115.150
*Chicago 7, IL ('''chicago7.voip.ms''') 50.31.115.151
*Dallas, TX ('''dallas.voip.ms''') 158.85.149.162
*Dallas 2, TX ('''dallas2.voip.ms''') 158.85.149.163
*Denver 1, CO ('''denver.voip.ms''') 23.239.211.90
*Denver 2, CO ('''denver2.voip.ms''') 64.27.52.226
*Houston, TX ('''houston.voip.ms''') 173.193.85.18
*Houston 2, TX ('''houston2.voip.ms''') 173.193.85.19
*Los Angeles 1, CA ('''losangeles.voip.ms''') 96.44.149.186
*Los Angeles 2, CA ('''losangeles2.voip.ms''') 96.44.149.202
*Los Angeles 3, CA ('''losangeles3.voip.ms''') 64.188.6.162
*Los Angeles 4, CA ('''losangeles4.voip.ms''') 64.188.6.170
*New York 1, NY ('''newyork.voip.ms''') 72.251.239.196
*New York 2, NY ('''newyork2.voip.ms''') 72.251.239.205
*New York 3, NY ('''newyork3.voip.ms''') 72.251.239.206
*New York 4, NY ('''newyork4.voip.ms''') 72.251.239.207
*New York 5, NY ('''newyork5.voip.ms''') 23.29.136.28
*New York 6, NY ('''newyork6.voip.ms''') 23.29.136.29
*New York 7, NY ('''newyork7.voip.ms''') 23.29.136.38
*New York 8, NY ('''newyork8.voip.ms''') 23.29.136.40
*San Jose, CA ('''sanjose.voip.ms''') 23.246.247.146
*San Jose 2, CA ('''sanjose2.voip.ms''') 23.246.247.147
*Seattle 1, WA ('''seattle.voip.ms''') 104.129.57.250
*Seattle 2, WA ('''seattle2.voip.ms''') 173.205.93.122
*Seattle 3, WA ('''seattle3.voip.ms''') 173.205.93.226
*Tampa, FL ('''tampa.voip.ms''') 162.254.144.173
*Tampa 2, FL ('''tampa2.voip.ms''') 209.133.209.70
*Tampa 3, FL ('''tampa3.voip.ms''') 23.111.187.139
*Tampa 4, FL ('''tampa4.voip.ms''') 23.111.166.202
*Washington 1, DC ('''washington.voip.ms''') 169.62.41.189
*Washington 2, DC ('''washington2.voip.ms''') 169.62.41.187
</li>

<li style="display: inline-block; vertical-align:top;">
'''International'''
*Amsterdam, NL ('''amsterdam.voip.ms''') 66.212.22.42
*London, UK ('''london.voip.ms''') 159.8.157.212
*Sydney, AU ('''sydney1.voip.ms''') 168.1.73.84
*Paris, FR ('''paris.voip.ms''') 159.8.85.180
</li>
</ul></div>

===Server Realms===

For IOS, Please click here [http://wiki.voip.ms/article/Server_Realms Server Realms] to get the Realm Name for the server you plan on using, this can differ from the Domain Name being used.

= What is a Ping? =

Ping is a standard tool used to test network connections. It is mostly used to determine if a server or device can be reached across the network and the latency of the response(the time it takes to send a packet to the destination and for it to return to your computer).

Ping tools are part of Windows, Mac OS X and Linux as well as some routers.

== How does the ping work? ==

It sends request messages to a target network address or DNS names at periodic intervals and measures the time it takes for a response message to arrive and return(better known as latency).

==How to ping on a PC==

Pinging is a command which tells you if the connection between your computer and a particular domain is working correctly.

In Windows, select Start > Programs > Accessories > Command Prompt. This will give you a window like the one below.

Enter the word ping, followed by a space, then the domain name.(montreal.voip.ms) in this case domain is our server name.

If the results show a series of replies, the connection is working. The time shows you how fast the connection is. If you see a "timed out" error instead of a reply, there is a breakdown somewhere between your computer and the domain.

[[File:Ping.gif|thumb|none|600px|Ping]]

==How to ping on a Mac Computer==

1- Click on Finder in the dock.

2- Click on Applications.

3- Click on Utilities.

4- Double-click on Network Utility. *

* In OS X Mavericks (10.9.x) this utility app changed location. Launch it from spotlight instead, either press "command"+"space bar" or click on spotlight directly (magnifying glass icon at top right of screen), type "network utility" and hit "return"

5- In the Network Utility window, click on the Ping tab

6- In the field under "Please enter the network address to ping," like montreal.voip.ms

''If pings results are not consistent, you may have an issue with Jitter. You can work on this issue by adjusting the "Network Jitter Level" setting on your VoIP device. Usually a ping of under 150 ms is recommended in order to have good quality. The latency time to the server is important, however there are also other factors that could affect the quality of the calls such as packet loss (VoIP communications are very sensitive to this), and the Jitter level of your Internet connection.''

The following is the output of running ping with the target losangeles.voip.ms.

#ping losangeles.voip.ms
Ping to losangeles.voip.ms [67.215.241.250] with 32 bytes de datos:
Response from 67.215.241.250: bytes=32 time=67ms TTL=52
Response from 67.215.241.250: bytes=32 time=69ms TTL=52
Response from 67.215.241.250: bytes=32 time=68ms TTL=52
Response from 67.215.241.250: bytes=32 time=67ms TTL=52
ping statistics from 67.215.241.250:
4 packets transmitted, 4 received, 0% packet lost. rtt min/avg/max/mdev = 67ms, 69ms, 67ms

Sample ping output in windows:
C:\Windows\system32>ping montreal.voip.ms

Pinging montreal.voip.ms [67.205.74.184] with 32 bytes of data:
Reply from 67.205.74.184: bytes=32 time=85ms TTL=49
Reply from 67.205.74.184: bytes=32 time=86ms TTL=49
Reply from 67.205.74.184: bytes=32 time=86ms TTL=49
Reply from 67.205.74.184: bytes=32 time=85ms TTL=49

Ping statistics for 67.205.74.184:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 85ms, Maximum = 86ms, Average = 85ms

= Latency Testing Scripts (User Submitted) =
<p>All the following scripts were produced by voip.ms users who felt others might also benefit from the output of their efforts. They were written over a span of Years and probably need adjusting before you use them, to cater for changes in servers over time and changes in policies (like not testing heavily subscribed servers which are not open to new registrations)</p>
<p>If you aren't satisfied that the scripts are safe or simply don’t like the way they syntactically appear, you can still manually ping a selection of servers and choose a server based on the best latency. The following scripts are essentially just wrappers around the ping command which support lists of servers to feed to ping and present the output in a readable format.</p>
<p>If you feel you have a simpler cleaner script that works for another platform or language, please do add it to this wiki via a support ticket.
</p>
=== Bash Script To Handle The Mac Ping Output Format ===

<p>To make use of this script (1) save as a plain text file (2) set permissions on the file to executable (3) invoke script
e.g. Save script below using your favourite editor as pingVoipMS.sh (2) chmod u+x pingVoipMS.sh (3) ./pingVoipMS.sh
This is a bash 3.x script, so it also works in Linux, just change the ping packet loss field from 7 to 6 in the final loop below (or wherever the loss field is in your ping output format). Depending upon your distro curl might need to change to wget.
</p>
<pre>
#!/bin/bash
# Ping several servers and display Latency, Jitter and Packet Loss
# Usage: [-c <count>][-i <wait time>][-r test restricted servers][<server list file>]
#
# The optional server list text file should be formatted with one host name per line.
# The list of voip.ms servers is available at https://wiki.voip.ms/article/Choosing_Server
# If no args are supplied, this script will scrape a ping server list from voip.ms
#
USER_FILE=""
COUNT=3; INTERVAL=5; RESTRICTED=0
restrictedList=(atlanta.voip.ms chicago.voip.ms
montreal.voip.ms montreal2.voip.ms montreal3.voip.ms montreal4.voip.ms
newyork.voip.ms newyork4.voip.ms seattle.voip.ms
toronto.voip.ms toronto2.voip.ms toronto3.voip.ms toronto4.voip.ms)

# Handle any passed in script arguments
while getopts c:i:r parm
do
case $parm in
c)count_opt=$OPTARG;;
i)interval_opt=$OPTARG;;
r)RESTRICTED=1;;
*)echo -e "Invalid arg\nUsage:\t[ -c <count of ECHO_REQUESTs to Tx, default 3> ] \
\n\t[ -i <wait time (s) between datagrams, default 5> ] \
\n\t[ -r ] Include restricted servers in latency test \
\n\t[FILE <ping server list> ]";exit 1;;
esac
done

# Test if an option was specified and whether it's a +ve non-zero integer
[[ -n $count_opt && ($count_opt =~ ^[[:digit:]]+$) && $count_opt -gt 0 ]] &&
COUNT=$count_opt
[[ -n $interval_opt && ($interval_opt =~ ^[[:digit:]]+$) && $interval_opt -gt 0 ]] &&
INTERVAL=$interval_opt

shift $((OPTIND - 1))

# Validate supplied file (server list)
[[ -n $1 && ! (-f $1 && -r $1) ]] &&
{ echo "\"$1\" file does not exist or is not readable"; exit 1; }
[[ -n $1 && -f $1 && -r $1 ]] && USER_FILE="$1"

if [[ -n $USER_FILE ]]
then
# Bash 3.x in macOS does not support readarray, need to do cumbersome array loops instead
while IFS= read -r servers; do
serverList+=( "$servers" )
done < <(grep -Eo '^\b[[:alpha:]]+?[[:alnum:]]\.voip\.ms\b$' "$USER_FILE" | \
grep -v '^\s*#' | awk NF | sort)
else
# N.B. The script looks for the html boldface tags <b> </b> inside a bracket
# If the website alters and the parse fails, manually create the list and
# supply as a script arg (or perhaps update the parsing to work again :)
while IFS= read -r servers; do
serverList+=( "$servers" )
done < <(curl -sm 10 https://wiki.voip.ms/article/Choosing_Server | \
grep -E '(<b>[[:alpha:]]+?[[:alnum:]]\.voip\.ms</b>)' | \
tr "<>" " " | awk '{print $(NF-3)}' | sort )
fi

# Newer voip.ms clients can't register onto these over-subscribed servers
# Don't test the restricted list unless explicitly asked (with the -r cmd line option)
if [[ $RESTRICTED -eq 0 ]]
then
for server in "${restrictedList[@]}"
do
ix=$(printf "%s\n" "${serverList[@]}" | grep -n "^${server}" | cut -d ":" -f1)
while IFS= read -ra idx; do
keys+=( "${idx[@]}" )
done < <([[ $ix -gt 0 ]] && echo $((ix-1)))
done
for ((i=${#keys[@]} - 1; i >= 0; i--)); do unset "serverList[keys[i]]"; done
fi

if [[ ${#serverList[@]} -eq 0 ]]
then
echo "No unrestricted Voip.ms servers could be found, please supply a server list"
exit 1
fi

runTime=$((COUNT * INTERVAL * ${#serverList[@]}))

echo "PING will send $COUNT packet(s) with a wait of $INTERVAL sec(s) between each packet"
echo "Change the PING options by invoking this script with -c and/or -i, default \"-c 3 -i 5\""
echo "Over $((${#serverList[@]})) server(s) the estimated script Run Time will be $runTime seconds"
echo "================================================================"
printf "%-20s %-18s %7s %8s %6s %s\n" "VoIP Server" "IP Address" "Latency" "Jitter" "Loss" "Countdown"
echo "================================================================ (seconds)"

for myLn in "${serverList[@]}"
do
while IFS=$'\n' read -r pings; do
pingList+=( "$pings" )
printf "%-64s %5d %2d/%-2d\n" "$pings" \
"$((runTime - COUNT * INTERVAL * ${#pingList[@]}))" \
"${#pingList[@]}" "${#serverList[@]}"
done < <( ping -c "$COUNT" -i "$INTERVAL" -q "$myLn" | awk \
'
/^PING / {myH=$2}
/^PING / {
IP = substr($3,2,15)
split(IP,myIP,")") }
/packet loss/ {myPL=$7}
/min\/avg\/max/ {
split($4,myS,"/")
printf("%-20s %-18s %7.3f %8.3f %6s\n",
myH, myIP[1], myS[2], myS[4], myPL ) }
' )
done

echo "================================================================"
echo -e "\nMost appropriate server listed in order of best latency\n"
echo "================================================================"
printf "%-20s %-18s %7s %8s %6s\n" "VoIP Server" "IP Address" "Latency" "Jitter" "Loss"
echo "================================================================"
printf "%s\n" "${pingList[@]}" | LC_ALL=C sort -n -k 3,3 -k 5,5 -k 4,4 | \
awk '{printf("%s $%2d$\n",$0, NR)}'
echo "================================================================"
</pre>

=== Perl Script ===
Pings list of voip.ms servers round robin with optional output csv file.

# usage ping_voip.ms.pl <number of times> <seconds in between> <output.csv>
use Net::Ping;
use Time::HiRes;
use strict;

# input list
my @hosts = qw(
atlanta.voip.ms
atlanta2.voip.ms
chicago.voip.ms
chicago2.voip.ms
chicago3.voip.ms
chicago4.voip.ms
dallas.voip.ms
denver.voip.ms
denver2.voip.ms
houston.voip.ms
losangeles.voip.ms
losangeles2.voip.ms
newyork.voip.ms
newyork2.voip.ms
newyork3.voip.ms
newyork4.voip.ms
seattle.voip.ms
seattle2.voip.ms
seattle3.voip.ms
tampa.voip.ms
washington.voip.ms
washington2.voip.ms
montreal.voip.ms
montreal2.voip.ms
montreal3.voip.ms
montreal4.voip.ms
toronto2.voip.ms
toronto3.voip.ms
toronto4.voip.ms
toronto.voip.ms
london.voip.ms
);

$| = 1; #autoflush
# High precision syntax (requires Time::HiRes)
my $p = Net::Ping->new("icmp",1);
$p->hires();
my $max_name_length = (reverse sort { $a <=> $b } map { length($_) } @hosts)[0];
my $count = 4; # number of times to ping
my $interval = 5; # seconds between ping rounds
my $output_file = "";
my @data;

# check for arguments
my $num_args = @ARGV;
if ($num_args >= 1) {$count = $ARGV[0];}
if ($num_args >= 2) {$interval = $ARGV[1];}
if ($num_args >= 3) {$output_file = $ARGV[2];}

# check argument validity
$0 =~ /^.*\\(.*)$/;
my $script = $1;
if ($count !~ /^\d+$/ or $interval !~ /^\d+$/) {die "Usage: $script <number of rounds> <seconds between rounds> <output.csv>\n";}
if (length($output_file) > 0 and $output_file !~ /\.csv$/) {$output_file .= ".csv";}

# main loop
for my $i (1..$count)
{
sleep $interval unless $i == 1;
print "Round $i\n";
my $host_num=0;
foreach my $host (@hosts)
{
(my $ret, my $duration, my $ip) = $p->ping($host);
$ip =~ /(\d+)\.(\d+)\.(\d+)\.(\d+)/;
if ($ret)
{
printf("%*s [ip: %3s.%3s.%3s.%3s] is alive (%6.2f ms)\n", $max_name_length, $host, $1, $2, $3, $4, $duration*1000);
$data[$host_num][$i]=$duration*1000;
}
else
{
printf("%*s [ip: %3s.%3s.%3s.%3s] is dead\n", $max_name_length, $host, $1, $2, $3, $4);
}
$host_num++;
}
print "\n";
}
$p->close();

# if output file name given
if (length($output_file)>0)
{
# print output to file
open FILE, ">$output_file" or die "$!\n";

# print column headers
print FILE "Server\\Round";
for my $i (1..$count)
{
print FILE ", $i";
}
print FILE ", Average\n";

# print data
my $i = 0;
foreach my $host (@hosts)
{
print FILE "$host";
my $sum = 0;
for my $j (1..$count)
{
$sum += $data[$i][$j];
printf FILE ", %8.4f",$data[$i][$j];
}
printf FILE ", %8.4f\n",$sum/$count;
$i++;
}

close FILE;
print "Data written to $output_file\n";
}

# print summary to screen
my $i = 0;
printf("%-*s Average (ms)\n", $max_name_length, "Server");
foreach my $host (@hosts)
{
my $sum = 0;
for my $j (1..$count)
{
$sum += $data[$i][$j];
}
printf("%-*s %8.4f\n", $max_name_length+1, $host, $sum/$count);
$i++;
}

Output:
Round 1
atlanta.voip.ms [ip: 174. 34.146.162] is alive ( 88.97 ms)
atlanta2.voip.ms [ip: 72. 9.246.170] is alive ( 92.99 ms)
chicago.voip.ms [ip: 208.100. 39. 52] is alive ( 49.70 ms)
chicago2.voip.ms [ip: 208.100. 39. 53] is alive ( 59.76 ms)
chicago3.voip.ms [ip: 208.100. 39. 54] is alive ( 59.53 ms)
chicago4.voip.ms [ip: 208.100. 39. 55] is alive ( 49.73 ms)
dallas.voip.ms [ip: 74. 54. 54.178] is alive ( 94.99 ms)
denver.voip.ms [ip: 173.248.161. 90] is alive ( 94.05 ms)
denver2.voip.ms [ip: 173.248.159.210] is alive ( 85.13 ms)
houston.voip.ms [ip: 209. 62. 1. 2] is alive (102.87 ms)
losangeles.voip.ms [ip: 96. 44.149.186] is alive ( 64.92 ms)
losangeles2.voip.ms [ip: 96. 44.149.202] is alive ( 63.41 ms)
newyork.voip.ms [ip: 74. 63. 41.218] is alive (131.75 ms)
newyork2.voip.ms [ip: 107. 6. 67.236] is alive (120.64 ms)
newyork3.voip.ms [ip: 107. 6. 67.237] is alive (120.49 ms)
newyork4.voip.ms [ip: 107. 6. 67.238] is alive (111.43 ms)
seattle.voip.ms [ip: 50. 23.160. 50] is alive ( 94.25 ms)
seattle2.voip.ms [ip: 50. 23.160. 51] is alive ( 95.86 ms)
seattle3.voip.ms [ip: 50. 23.160. 52] is alive ( 90.85 ms)
tampa.voip.ms [ip: 68.233.226. 97] is alive (123.29 ms)
washington.voip.ms [ip: 208. 43.234.226] is alive ( 98.71 ms)
washington2.voip.ms [ip: 208. 43.234.227] is alive (101.19 ms)
montreal.voip.ms [ip: 67.205. 74.184] is alive ( 81.82 ms)
montreal2.voip.ms [ip: 67.205. 74.187] is alive ( 86.13 ms)
montreal3.voip.ms [ip: 72. 55.168. 18] is alive ( 77.09 ms)
montreal4.voip.ms [ip: 67.205. 74.179] is alive ( 96.18 ms)
toronto2.voip.ms [ip: 184. 75.215.114] is alive (103.70 ms)
toronto3.voip.ms [ip: 184. 75.215.146] is alive (131.27 ms)
toronto4.voip.ms [ip: 184. 75.213.210] is alive (125.13 ms)
toronto.voip.ms [ip: 184. 75.215.106] is alive (103.26 ms)
london.voip.ms [ip: 5. 77. 36.136] is alive (152.77 ms)

Round 2
atlanta.voip.ms [ip: 174. 34.146.162] is alive ( 88.14 ms)
atlanta2.voip.ms [ip: 72. 9.246.170] is alive ( 92.86 ms)
chicago.voip.ms [ip: 208.100. 39. 52] is alive ( 50.03 ms)
chicago2.voip.ms [ip: 208.100. 39. 53] is alive ( 59.44 ms)
chicago3.voip.ms [ip: 208.100. 39. 54] is alive ( 59.33 ms)
chicago4.voip.ms [ip: 208.100. 39. 55] is alive ( 50.22 ms)
dallas.voip.ms [ip: 74. 54. 54.178] is alive ( 95.58 ms)
denver.voip.ms [ip: 173.248.161. 90] is alive ( 95.94 ms)
denver2.voip.ms [ip: 173.248.159.210] is alive ( 85.29 ms)
houston.voip.ms [ip: 209. 62. 1. 2] is alive (102.73 ms)
losangeles.voip.ms [ip: 96. 44.149.186] is alive ( 65.59 ms)
losangeles2.voip.ms [ip: 96. 44.149.202] is alive ( 64.27 ms)
newyork.voip.ms [ip: 74. 63. 41.218] is alive (112.74 ms)
newyork2.voip.ms [ip: 107. 6. 67.236] is alive (121.22 ms)
newyork3.voip.ms [ip: 107. 6. 67.237] is alive (121.34 ms)
newyork4.voip.ms [ip: 107. 6. 67.238] is alive (110.75 ms)
seattle.voip.ms [ip: 50. 23.160. 50] is alive ( 94.06 ms)
seattle2.voip.ms [ip: 50. 23.160. 51] is alive ( 95.33 ms)
seattle3.voip.ms [ip: 50. 23.160. 52] is alive ( 91.58 ms)
tampa.voip.ms [ip: 68.233.226. 97] is alive (122.94 ms)
washington.voip.ms [ip: 169.62.41.189] is alive ( 98.28 ms)
washington2.voip.ms [ip: 169.62.41.187] is alive (101.40 ms)
montreal.voip.ms [ip: 67.205. 74.184] is alive ( 81.91 ms)
montreal2.voip.ms [ip: 67.205. 74.187] is alive ( 85.64 ms)
montreal3.voip.ms [ip: 72. 55.168. 18] is alive ( 75.15 ms)
montreal4.voip.ms [ip: 67.205. 74.179] is alive ( 96.79 ms)
toronto2.voip.ms [ip: 184. 75.215.114] is alive (103.10 ms)
toronto3.voip.ms [ip: 184. 75.215.146] is alive (150.85 ms)
toronto4.voip.ms [ip: 184. 75.213.210] is alive (138.40 ms)
toronto.voip.ms [ip: 184. 75.215.106] is alive (103.45 ms)
london.voip.ms [ip: 5. 77. 36.136] is alive (170.79 ms)

Round 3
atlanta.voip.ms [ip: 174. 34.146.162] is alive ( 88.76 ms)
atlanta2.voip.ms [ip: 72. 9.246.170] is alive ( 92.86 ms)
chicago.voip.ms [ip: 208.100. 39. 52] is alive ( 49.65 ms)
chicago2.voip.ms [ip: 208.100. 39. 53] is alive ( 60.01 ms)
chicago3.voip.ms [ip: 208.100. 39. 54] is alive ( 59.05 ms)
chicago4.voip.ms [ip: 208.100. 39. 55] is alive ( 49.53 ms)
dallas.voip.ms [ip: 74. 54. 54.178] is alive ( 95.82 ms)
denver.voip.ms [ip: 173.248.161. 90] is alive ( 95.02 ms)
denver2.voip.ms [ip: 173.248.159.210] is alive ( 85.60 ms)
houston.voip.ms [ip: 209. 62. 1. 2] is alive (103.35 ms)
losangeles.voip.ms [ip: 96. 44.149.186] is alive ( 65.79 ms)
losangeles2.voip.ms [ip: 96. 44.149.202] is alive ( 64.05 ms)
newyork.voip.ms [ip: 74. 63. 41.218] is alive (113.01 ms)
newyork2.voip.ms [ip: 107. 6. 67.236] is alive (121.41 ms)
newyork3.voip.ms [ip: 107. 6. 67.237] is alive (122.23 ms)
newyork4.voip.ms [ip: 107. 6. 67.238] is alive (110.62 ms)
seattle.voip.ms [ip: 50. 23.160. 50] is alive ( 93.65 ms)
seattle2.voip.ms [ip: 50. 23.160. 51] is alive ( 95.19 ms)
seattle3.voip.ms [ip: 50. 23.160. 52] is alive ( 90.75 ms)
tampa.voip.ms [ip: 68.233.226. 97] is alive (125.12 ms)
washington.voip.ms [ip: 208. 43.234.226] is alive ( 98.19 ms)
washington2.voip.ms [ip: 208. 43.234.227] is alive (101.98 ms)
montreal.voip.ms [ip: 67.205. 74.184] is alive ( 80.16 ms)
montreal2.voip.ms [ip: 67.205. 74.187] is alive ( 87.16 ms)
montreal3.voip.ms [ip: 72. 55.168. 18] is alive ( 76.54 ms)
montreal4.voip.ms [ip: 67.205. 74.179] is alive ( 97.51 ms)
toronto2.voip.ms [ip: 184. 75.215.114] is alive (104.18 ms)
toronto3.voip.ms [ip: 184. 75.215.146] is alive (142.81 ms)
toronto4.voip.ms [ip: 184. 75.213.210] is alive (138.95 ms)
toronto.voip.ms [ip: 184. 75.215.106] is alive (103.78 ms)
london.voip.ms [ip: 5. 77. 36.136] is alive (153.14 ms)

Round 4
atlanta.voip.ms [ip: 174. 34.146.162] is alive ( 89.19 ms)
atlanta2.voip.ms [ip: 72. 9.246.170] is alive ( 92.98 ms)
chicago.voip.ms [ip: 208.100. 39. 52] is alive ( 49.21 ms)
chicago2.voip.ms [ip: 208.100. 39. 53] is alive ( 60.50 ms)
chicago3.voip.ms [ip: 208.100. 39. 54] is alive ( 59.68 ms)
chicago4.voip.ms [ip: 208.100. 39. 55] is alive ( 50.18 ms)
dallas.voip.ms [ip: 74. 54. 54.178] is alive ( 93.93 ms)
denver.voip.ms [ip: 173.248.161. 90] is alive ( 94.22 ms)
denver2.voip.ms [ip: 173.248.159.210] is alive ( 85.10 ms)
houston.voip.ms [ip: 209. 62. 1. 2] is alive (103.67 ms)
losangeles.voip.ms [ip: 96. 44.149.186] is alive ( 65.58 ms)
losangeles2.voip.ms [ip: 96. 44.149.202] is alive ( 63.60 ms)
newyork.voip.ms [ip: 74. 63. 41.218] is alive (114.76 ms)
newyork2.voip.ms [ip: 107. 6. 67.236] is alive (120.44 ms)
newyork3.voip.ms [ip: 107. 6. 67.237] is alive (121.05 ms)
newyork4.voip.ms [ip: 107. 6. 67.238] is alive (110.51 ms)
seattle.voip.ms [ip: 50. 23.160. 50] is alive ( 94.04 ms)
seattle2.voip.ms [ip: 50. 23.160. 51] is alive ( 96.92 ms)
seattle3.voip.ms [ip: 50. 23.160. 52] is alive ( 91.23 ms)
tampa.voip.ms [ip: 68.233.226. 97] is alive (123.28 ms)
washington.voip.ms [ip: 208. 43.234.226] is alive ( 98.45 ms)
washington2.voip.ms [ip: 208. 43.234.227] is alive (100.94 ms)
montreal.voip.ms [ip: 67.205. 74.184] is alive ( 82.33 ms)
montreal2.voip.ms [ip: 67.205. 74.187] is alive ( 85.02 ms)
montreal3.voip.ms [ip: 72. 55.168. 18] is alive ( 76.85 ms)
montreal4.voip.ms [ip: 67.205. 74.179] is alive ( 96.32 ms)
toronto2.voip.ms [ip: 184. 75.215.114] is alive (104.22 ms)
toronto3.voip.ms [ip: 184. 75.215.146] is alive (148.33 ms)
toronto4.voip.ms [ip: 184. 75.213.210] is alive (141.61 ms)
toronto.voip.ms [ip: 184. 75.215.106] is alive (105.91 ms)
london.voip.ms [ip: 5. 77. 36.136] is alive (152.85 ms)

Server Average (ms)
atlanta.voip.ms 88.7630
atlanta2.voip.ms 92.9233
chicago.voip.ms 49.6477
chicago2.voip.ms 59.9305
chicago3.voip.ms 59.3972
chicago4.voip.ms 49.9152
dallas.voip.ms 95.0790
denver.voip.ms 94.8077
denver2.voip.ms 85.2797
houston.voip.ms 103.1562
losangeles.voip.ms 65.4693
losangeles2.voip.ms 63.8347
newyork.voip.ms 118.0643
newyork2.voip.ms 120.9265
newyork3.voip.ms 121.2778
newyork4.voip.ms 110.8275
seattle.voip.ms 93.9993
seattle2.voip.ms 95.8267
seattle3.voip.ms 91.1035
tampa.voip.ms 123.6570
washington.voip.ms 98.4065
washington2.voip.ms 101.3774
montreal.voip.ms 81.5525
montreal2.voip.ms 85.9863
montreal3.voip.ms 76.4058
montreal4.voip.ms 96.7013
toronto2.voip.ms 103.7986
toronto3.voip.ms 143.3156
toronto4.voip.ms 136.0254
toronto.voip.ms 104.1012
london.voip.ms 157.3885

=== Powershell ===

Dec 2017 - A bug in the code shown washington2.voip.ms as the best server, this was corrected.

<pre>
# Usage: Copy and paste the following code into a powershell window
# To run it from a command prompt, save this file with extension ps1.
# Then run Powershell.exe -file "pathtothisscript.ps1"
Clear-Variable best* -Scope Global #Clear the best* variables in case you run it more than once...
#Get the list of servers into an array
$Servers =
@("amsterdam.voip.ms","atlanta.voip.ms","atlanta2.voip.ms","chicago.voip.ms","chicago2.voip.ms","chicago3.voip.ms",
"chicago4.voip.ms","dallas.voip.ms","dallas2.voip.ms","denver.voip.ms","denver2.voip.ms","houston.voip.ms",
"houston2.voip.ms","london.voip.ms","losangeles.voip.ms","losangeles2.voip.ms","montreal.voip.ms",
"montreal2.voip.ms","montreal3.voip.ms","montreal4.voip.ms","montreal5.voip.ms","montreal6.voip.ms","montreal7.voip.ms",
"montreal8.voip.ms","newyork.voip.ms","newyork2.voip.ms","newyork3.voip.ms","newyork4.voip.ms","newyork5.voip.ms",
"newyork6.voip.ms","newyork7.voip.ms","newyork8.voip.ms","paris.voip.ms","sanjose.voip.ms","sanjose2.voip.ms",
"seattle.voip.ms","seattle2.voip.ms","seattle3.voip.ms","tampa.voip.ms","tampa2.voip.ms","toronto.voip.ms",
"toronto2.voip.ms","toronto3.voip.ms","toronto4.voip.ms","toronto5.voip.ms","toronto6.voip.ms","toronto7.voip.ms",
"toronto8.voip.ms","vancouver.voip.ms","vancouver2.voip.ms","washington.voip.ms","washington2.voip.ms")
$k = 0 #Counting variable so we know what server number we are testing
#num of servers to test
$servercount = $servers.length
#Do the following code for each server in our array
ForEach($server in $servers)
{
#Add one to the counting variable....we are on server #1...then server 2, then server 3 etc...
$k++
#Update the progress bar
Write-Progress -Activity "Testing Server: ${server}" -status "Testing Server $k out of $servercount" -percentComplete ($k / $servercount*100)
#Counting variable for number of times we tried to ping a given server
$i = 0
Do{
#assume a failure
$pingsuccess = $false
$i++ #Add one to the counting variable.....1st try....2nd try....3rd try etc...
Try{
#Try to ping
$currentping = (test-connection $server -count 1 -ErrorAction Stop).responsetime
#If success full, set success variable
$pingsuccess = $true
}
#Catch the failure and set the success variable to false
Catch {
$pingsuccess = $false
}
}
#Try everything between Do and While up to 5 times, or while $pingsuccess is not true
While($pingsuccess -eq $false -and $i -le 5)
#Compare the last ping test with the best known ping test....if there is no known best ping test, assume this one is the best $bestping = $currentping
If($pingsuccess -and ($currentping -lt $bestping -or (!($bestping)))){
#If this is the best ping...save it
$bestserver = $server #Save the best server
$bestping = $currentping #Save the best ping results
}
write-host "tested: $server at $currentping ms after $i attempts" #write the results of the test for this server
}
write-host "`r`n The server with the best ping is: $bestserver at $bestping ms`r`n" #write the end result
Pause
</pre>

=== Linux Shell Script ===
Pings several voip.ms servers

#!/bin/sh
# Ping several servers and display Latency, Jitter and Packet Loss
#
# First, create a text file with all servers you want to ping - one host name per line.
# The list of voip.ms servers is available at http://wiki.voip.ms/article/Choosing_Server
myHF="voip_ping_hosts.txt"
# Sample file:
# toronto.voip.ms
# montreal.voip.ms
# seattle.voip.ms
# chicago.voip.ms
# newyork.voip.ms
#
echo "============================================"
printf "%-20s %7s %8s %6s\n" "VoIP Server" "Latency" "Jitter" "Loss"
echo "============================================"
cat ${myHF} |\
while read myLn
do
ping -c 3 -i 5 -q $myLn |\
awk '/^PING / {myH=$2}
/packet loss/ {myPL=$6}
/min\/avg\/max/ {
split($4,myS,"/")
printf( "%-20s %3.1f %1.3f %4s\n", myH, myS[2], myS[4], myPL)
}'
done
echo "============================================"

Output:

============================================
VoIP Server Latency Jitter Loss
============================================
toronto.voip.ms 68.3 0.439 0%
montreal.voip.ms 89.6 0.197 0%
seattle.voip.ms 71.2 0.387 0%
chicago.voip.ms 71.6 0.084 0%
newyork.voip.ms 79.1 0.411 0%
============================================

= Latency and its importance =

Latency is very important for Voip, this will determine the time that will take for the data package transmission to reach the destination. A high latency will lead to a delay and echoes in the communication.

Latency is measured in milliseconds (ms) For example: a latency of 150ms is barely noticeable, thus acceptable. Higher than that, quality starts to suffer. When it gets higher than 300 ms, it becomes unacceptable.

[[category:guides]]

Cisco SPA112

2021-01-25T19:50:32Z

B13n:

[[File:SPA112.jpg|300px|thumb|left|Cisco SPA112]]
<div style="width:100%;overflow:hidden;clear:both"></div>

'''Please note these models are EOL (End of life) & aren't supported by CISCO anymore''' https://www.cisco.com/c/en/us/products/collateral/unified-communications/small-business-voice-gateways-ata/eos-eol-notice-c51-743206.html

: '''There have been some reports of issues with this device from customers of both VoIP.ms and other providers.'''
: '''Make sure to install the latest firmware from [https://software.cisco.com/download/release.html?mdfid=283998771&softwareid=282463187&release=1.4.1%20SR3&relind=AVAILABLE&rellifecycle=&reltype=latest Cisco Software].'''
: '''Version 1.1 or later should be used for proper Caller ID support. '''
: '''Some People have reported issues using Firefox to Configure this device; please try Chrome or IE. '''

==Documentation==
[https://www.cisco.com/c/en/us/support/unified-communications/spa112-2-port-phone-adapter/model.html#~tab-documents Official Configuration guide / User guide / Data Sheets]

== Configuration Details ==

=== Getting the IP address of your device ===

There are two ways to retrieve the IP address of your Cisco SPA112: via analog phone menu, and via your internet router.

{| class="wikitable"
! style="text-align: center;" | Analog phone interface
! style="text-align: center;" | Internet Router
|-
|
# Attach the Cisco SPA112 to your network and attach an analog phone to one of the phone ports, then do the following:
## Dial **** from the phone, even though there is no dial tone.
## When you hear "System Configuration Menu," dial 1 1 0 # slowly. The current IP address will be read back. (e.g. 192.168.X.X)

'''If you hear 0.0.0.0, check your network connection and DHCP server. If necessary, a static IP address'''
'''can be assigned by using option 111# at the IVR, then entering the IP address with your phone's keypad'''
'''(for example, 10*1*27*2 for 10.1.27.2). The network mask can be set with option 121# and the default'''
'''gateway can be sent with option 131#'''
Learn more about the IVR menu options from the https://supportforums.cisco.com/docs/DOC-9900 document.

Be sure to allow at least a minute or two for the box to initialize; even a correctly configured and installed SPA112/122 will give no power or dialtone to the phone until initialization is complete.

Note that the SPA122 is basically a SPA112 with a second network port, intended for installation between a local network hub (LAN) and an upstream Internet (WAN) connection. The SPA122 may be configured as either a "NAT" or "bridge". Depending on configuration, this leaves the SPA122 with two addresses; a local area network address (such as 192.168.15.1) and an outside Internet address. Dialing ****110# will give one address, ****210# will give the other.
|
# Attach the Cisco SPA112 to your network
# Access your router's remote administration interface via your web browser (typical addresses may be <code>192.168.0.1</code> or <code>192.168.1.1</code>). Refer to your router instructions for more information.
# Enter your username/password if asked. If you have not set one, then it is likely the unchanged default password.
# In the router's menu, there should be a page showing a list of connected clients, with their internal IP address. Find the entry corresponding to the Cisco SPA112. It should identify itself in the list as "SPA112"
# Navigate to this IP address via your web browser
|}

=== Accessing to the device's settings page ===

Open your web browser and go to the IP address you obtained in step 1 (for example, http://192.168.2.1).
The default username is admin, and the default password is also admin.

For the SPA122, if one address does not return the web interface (or has some functions greyed/disabled), try the other.

=== Configuring the Quick Setup screen ===

Go to Quick Setup and configure Line 1 as follows:

'''Proxy:''' atlanta.voip.ms (You can choose any of our multiple VoIP.ms [http://wiki.voip.ms/article/Choosing_Server servers])

'''Display Name:''' Your name

'''User ID:''' 100000 (Replace with your 6 digit Main SIP account UserID or Sub Account user name, i.e. 123456 or 123456_sub)

'''Password:''' Your VoIP.MS SIP Password

'''Dial Plan:''' (911S0|310xxxx|<:1555>[2-9]xxxxxx|1[2-9]xx[2-9]xxxxxxS0|[2-9]xx[2-9]xxxxxxS0|*xx|***xxx|*xx.|[3468]11|822|0|00|4xxx|**275*x.|xxxxxxxxxxxx.)

('''''Note''''': Replace 555 in the dial plan with your area code, See [[Dial Plan for Linksys ATAs]] for details.)

Click Submit to save settings.

[[File:quick_setup_test.png|800px|thumb|left|Quick Setup Page - Click to enlarge]]
<br clear="all" />

=== Configuring the Voice Line ===
==== Nat Settings ====

Click on Voice, then Line 1

Set '''NAT Mapping Enable''' to Yes, then set '''NAT Keep Alive Enable''' to Yes. If your environment does not use NAT, you can leave these settings disabled. These features can usually be disabled on the SPA122 if it is connected directly to your modem since its traffic will not be subject to NAT in this configuration.

If using the second phone line on an SPA122 device, change the SIP Port for one of the lines to e.g. 5080.

[[File:VL_1_nat_settings.png|800px|thumb|left|NAT Settings - Click to enlarge]]
<br clear="all" />

==== Proxy and Registration ====

Under '''Proxy and Registration''', set the server you will use as registration server and the proper values for the Register Expires and Proxy Fallback Intvl:

'''Proxy''': atlanta.voip.ms (one of VoIP.ms multiple [http://wiki.voip.ms/article/Choosing_Server servers], you can choose the one closest to your location)
'''Register Expires''' to 300
'''Proxy Fallback Intvl''' to 300

Also confirm the following settings:<br />
'''Register:''' YES <br />
'''Use DNS SRV:''' NO<br />
'''DNS SRV Auto Prefix:''' NO

[[File:VL_2_proxyAndRegistration.png|800px|thumb|left|Proxy and Registration - Click to enlarge]]
<br clear="all" />

Click Submit to save these changes

==== Subscriber Information ====

In this section please confirm that you have the proper account information:

'''Display Name''': Your name (that will be shown as callerID name)
'''User ID''': 100000 (Replace with your 6 digit Main SIP account UserID or Sub Account user name, i.e. 123456 or 123456_sub)
'''Password''': Your VoIP.ms SIP Password

[[File:VL_3_subscriberInformation.png|800px|thumb|left|Subscriber Information - Click to enlarge]]
<br clear="all" />

==== Audio Configuration ====

You can verify or change the audio codec that will be used with the calls. Please verify that you have the same codec selected in your SIP account's settings.

Preferred codec: g711u (or G729)

[[File:VL_4_audioConfig.png|800px|thumb|left|Audio configuration - Click to enlarge]]
<br clear="all" />

==== Dial Plan ====

We recommend to use this dial plan.

(911S0|310xxxx|<:1555>[2-9]xxxxxx|1[2-9]xx[2-9]xxxxxxS0|[2-9]xx[2-9]xxxxxxS0|*xx|***xxx|*xx.|[3468]11|822|0|00|4xxx|**275*x.|xxxxxxxxxxxx.)

('''''Note''''': Replace 555 in the dial plan with your area code, See [[Dial Plan for Linksys ATAs]] for details.)

[[File:VL_5_dialPlan.png|800px|thumb|left|Dial Plan - Click to enlarge]]
<br clear="all" />

You can create your own dial plan if you need it. See [[Dial Plan for Linksys ATAs]] and also [https://www.cisco.com/c/en/us/support/docs/collaboration-endpoints/spa901-1-line-ip-phone/108747-pqa-108747.html here] you'll find a great explanation about dial plans for Cisco devices

=== Optional settings ===

==== Outbound audio "breaking up". ====

Cisco's defaults (SIP T1 = 0.5 sec, RTP packet size 0.030 on most Sipura adapters) respectively may cause unnecessary retransmission of commands over connections with high latency and create issues with outbound audio "breaking up".

Click '''Voice''', then go to '''SIP'''.

Set SIP Timer Values (sec)

SIP T1: 1

Set RTP Parameters

RTP Packet Size: 0.02
RTP Port Min: 10000
RTP Port Max: 20000

Click Submit to save the changes

[[File:VS_sipAndRTP.png|800px|thumb|left|SIP Values - Click to enlarge]]
<br clear="all" />

==== Caller ID display showing incorrect time ====

Sometimes the hour shown in your caller ID is incorrect. Following this suggestion usually solves the issue:

Enter your device's settings and click '''Network Setup''', then go to '''Basic Setup''', then click '''Time Settings'''

Set your time zone and (optional) NTP settings. A good time server choice is 0.pool.ntp.org. Setting the proper time zone will ensure that the time which appears on your Caller ID display is correct.

===Configuring a Voice line using TLS===

'''NOTE''': This section is optional. It explains in detail how to use encrypted traffic in the device. If you are not certain on how encrypted traffic works, or the benefits of encrypting SIP traffic, please contact technical support for more information.

These devices are compatible with TLS, however, some settings need to be adjusted to have it working. This section will be assuming that your SIP account is already enabled to use TLS, if you have not enable it yet, please follow these instructions before going further:

For more information on how to enable encrypted traffic for the main account, please click on [[Call_Encryption_-_TLS/SRTP#Activate_This_Option_on_Your_Main_Account | Main account]] or more information on how to enable encrypted traffic for the sub account [[Call_Encryption_-_TLS/SRTP#Activate_This_Option_on_Your_Sub_Account | sub account]]

====Verifying the device's Firmware version====

First, check your firmware's version. This is, from your Device's Configuration Utility at ''Status >> System Information''

We '''strongly recommend''' to use the latest firmware version available, up today is the ''1.4.1 (SR3) Apr 3 2019''. If you do not have this version, you may consider its upgrade.

[[File:SPA_FW_Ver.png|800px|thumb|left|Click to enlarge]]
<br clear="all" />

==== Enabling TLS for the line ====

Go to the User's line you will use (If you use the Line 1 go to User 1) and navigate to the '''''Supplementary Service Settings''''', there set:
:''Secure Call Setting'': '''''yes'''''

[[File:SPA_User_SCS.png|800px|thumb|left|Click to enlarge]]
<br clear="all" />

==== Configuring the transport and port ====

Go to the line you will be using with TLS and navigate to the section ''SIP Settings'', then set:
:''SIP Transport'' : '''''TLS'''''
:''SIP Port'' : '''''5061'''''

[[File:SPA_Voice_Line.png|800px|thumb|left|Click to enlarge]]
<br clear="all" />

==== CA Certificate ====

As per CISCO's requirements, a CA certificate is needed to use Secure calls with the SPA112's device. To achieve this you will need to import the CA Cert.

Go to ''Voice >> Provisioning'' and once there navigate to '''''CA Settings''''', at ''Custom CA URL'' enter the following:

http://spa1xx.voip.ms/cca.pem

[[File:SPA_Prov_CA.png|800px|thumb|left|Click to enlarge]]
<br clear="all" />

Click ''Submit'', the device will reboot and after that will register and you will be ready to use it with TLS

==== Secure Call Indication Tone ====

Once the secure call feature is enabled, during all the duration of your calls you will hear a couple of tones (beeps), this is normal and beyond ''VoIP.ms'' control, however you can disable this notification going to: ''Voice >> Regional >> Secure Call Indication Tone''

'''''Note:''''' Please notice that this setting is not an on/off, you will need to remove all the line
In case you need to set it back, the default value is
397@-19,507@-19;15(0/2/0,.2/.1/1,.1/2.1/2)

[[File:SPA_Regional_Tone.png|800px|thumb|left|Click to enlarge]]
<br clear="all" />

Click Submit to save the changes

==Known Issues==

=== '''Phone will not ring on handset''' ===

Sometimes the Phone you are using is designed for a certain voltage and ring waveform. If someone tries to call you and the phone appears to be ringing for the caller but your phone never rings, please follow these steps to hopefully resolve this issue for you.

Step 1: First access the SPA web interface.

Step 2: Click on the '''Admin Login''' and then click on '''(switch to advanced view)'''

Step 3: Click on your Regional tab on the top menu.

Step 4: Go halfway down the page until you see the heading '''Ring and Call Waiting Tone Spec'''

[[File:Pap2Ring.jpg|800px|thumb|left| Ring and Call Waiting - Click to enlarge]]
<br clear="all" />

Step 5: Change the Ring Waveform setting to Sinusoid or Trapezoid, the opposite of what you have set. You can also change the Ring Voltage in increments of 5 to 90 or 95.

Step 6: Save settings and test an incoming call.

=== Receiving Unwanted Calls in the middle of the Night (i.e. CallerID 100) that do not appear in your CDR: ===

These calls are not going through our Network but rather through the internet directly to your ATA Device.

Please look under the Voice>> Line 1 page in your SPA device for the following setting: Restrict Source IP and make sure it's enabled.

This way the ATA device will block any traffic not coming from our servers.

[[File:VL_1_restrictSourceIP.png|800px|thumb|left|Restrict IP - Click to enlarge]]
<br clear="all" />

=== Firmware Upgrade ===

SPA112 and SPA122 adapters were distributed with outdated (1.0.x) firmware at least as late as 2012; affected boxes will not show Caller ID on any inbound call, even though the caller names and numbers are visible in the call detail record on VoIP.ms (or other provider's) web interface.

Updated firmware is available from the Cisco site [https://software.cisco.com/download/release.html?mdfid=283998771&softwareid=282463187&release=1.4.1%20SR3&relind=AVAILABLE&rellifecycle=&reltype=latest Cisco Firmware] as a .ZIP archive which contains two files (a .BIN with the actual firmware and a .PDF with documentation). Download and unzip this file. Go to the 'administration' tab on the web interface (on the SPA122, this needs to be done from the LAN side with SPA122's built-in networking set to NAT mode). On the left sidebar, click 'update firmware' (as most of the administration menu does not appear for Firefox users, downgrade to MS IE or another browser temporarily). Click the 'upload' button and indicate the location of the unzipped .BIN file. A box will appear with a progress indicator and a warning not to interrupt the upgrade. When the upgrade is completed, the SPA112/122 will reset and will likely take a minute or more to reinitialize, reconnect to the network and restore dial tone. SPA122 users who have installed the device in-line between the local PCs and the Internet will be disconnected from the Internet until reinitialization is complete.

Once the new firmware is deployed, call display will operate normally and the configuration web page will display in Firefox without missing options in the administration menu.

A manual for Cisco's SPA100 series adapters is online at http://www.cisco.com/en/US/docs/voice_ip_comm/csbpvga/spa100-200/admin_guide_SPA100/spa100_ag.html

* You can check the most commonly used [[Cisco/Linksys Star Codes]]

=== SPA Star Codes ===

{| class="wikitable" style="margin-left: center; margin-right: auto; border: none;"
! colspan="3" | SPA Star Codes
|-
! scope="col" | Star Code
! scope="col" | Name
! scope="col" | Result
|-
| *69 || Call Return Code || This code calls the last caller.
|-
| *07 || Call Redial Code || Redials the last number called. (Not in pap2t)
|-
| *98 || Blind Transfer Code || Begins a blind transfer of the current call to the extension specified after the activation code.
|-
| *66 || Call Back Act Code || Starts a callback when the last outbound call is not busy.
|-
| *86 || Call Back Dea t Code || Cancels a callback.
|-
| *05 || Call Back Busy Act Code || Starts a callback when the last outbound call is busy. (Not in pap2t)
|-
| *72 || Cfwd All Act Code || Forwards all calls to the extension specified after the activation code.
|-
| *73 || Cfwd All Deact Code || Cancels call forwarding of all calls.
|-
| *90 || Cfwd Busy Act Code || Forwards busy calls to the extension specified after the activation code.
|-
| *91 || Cfwd Busy Deact Code || Cancels call forwarding of busy calls.
|-
| *92 || Cfwd No Ans Act Code || Forwards no-answer calls to the extension specified after the activation code.
|-
| *93 || Cfwd No Ans Deact Code || Cancels call forwarding of no-answer calls.
|-
| *63 || Cfwd Last Act Code || Forwards the last inbound or outbound calls to the extension specified after the activation code.
|-
| *83 || Cfwd Last Deact Code || Cancels call forwarding of the last inbound or outbound calls.
|-
| *60 || Block Last Act Code || Blocks the last inbound call.
|-
| *80 || Block Last Deact Code || Cancels blocking of the last inbound call.
|-
| *64 || Accept Last Act Code || Accepts the last outbound call. It lets the call ring through when do not disturb or call forwarding of all calls are enabled.
|-
| *84 || Accept Last Deact Code || Cancels the code to accept the last outbound call.
|-
| *56 || CW Act Code || Enables call waiting on all calls.
|-
| *57 || CW Deact Code || Disables call waiting on all calls.
|-
| *71 || CW Per Call Act Code || Enables call waiting for the next call.
|-
| *70 || CW Per Call Deact Code || Disables call waiting for the next call.
|-
| *67 || Block CID Act Code || Blocks caller ID on all outbound calls.
|-
| *68 || Block CID Deact Code || Removes caller ID blocking on all outbound calls.
|-
| *81 || Block CID Per Call Act Code || Blocks caller ID on the next outbound call.
|-
| *82 || Block CID Per Call Deact Code || Removes caller ID blocking on the next inbound call.
|-
| *77 || Block ANC Act Code || Blocks all anonymous calls.
|-
| *87 || Block ANC Deact Code || Removes blocking of all anonymous calls.
|-
| *78 || DND Act Code || Enables the do not disturb feature.
|-
| *79 || DND Deact Code || Disables the do not disturb feature.
|-
| *65 || CID Act Code || Enables caller ID generation.
|-
| *85 || CID Deact Code || Disables caller ID generation.
|-
| *25 || CWCID Act Code || Enables call waiting, caller ID generation.
|-
| *45 || CWCID Deact Code || Disables call waiting, caller ID generation.
|-
| *26 || Dist Ring Act Code || Enables the distinctive ringing feature.
|-
| *46 || Dist Ring Deact Code || Enables the distinctive ringing feature. The default is *46 ||.
|-
| *74 || Speed Dial Act Code || Assigns a speed dial number.
|-
| *16 || Secure All Call Act Code || Makes all outbound calls secure.
|-
| *17 || Secure No Call Act Code || Makes all outbound calls not secure.
|-
| *18 || Secure One Call Act Code || Makes the next outbound call secure. (It is redundant if all outbound calls are secure by default.)
|-
| *19 || Secure One Call Deact Code || Secure One Call Deact Code Makes the next outbound call not secure. (It is redundant if all outbound calls are not secure by default.)
|}

==Guide Links==
In the event where you need the guide directly from Cisco, you may find the admin manual guide below:

Admin Manual : [https://www.cisco.com/c/dam/en/us/td/docs/voice_ip_comm/csbpvga/spa100-200/admin_guide_SPA100/spa100_ag_1_3_5.pdf Download PDF]

[[category:Analog Telephone Adapters]]

FAQ

2021-01-21T20:16:52Z

B13n:

[[File:Logo-VoIPms-light.png|250px|]]

{| class="wikitable"
|+
|-
! Article en Français !! Artículo en Español
|-
| [https://wiki.voip.ms/article/Questions_Les_Plus_Fr%C3%A9quentes Français] || [https://wiki.voip.ms/article/Preguntas_frecuentes Español]
|}

<span style="font-size: 120%;">__TOC__</span>

__TOC__

==Do you offer a Test Account or Number?==
We currently do not have a test account or test number program however opening an account is completely free and we provide free dialing codes to test the quality of the service.
Please check our many dialing codes here: [[Dialing Codes]]

==How do I start?==
You can open an account for free following this link : https://voip.ms/signup.php
Once your account is active you will be able to log in and find all of our features and options.
We suggest to also check our [[Getting Started]] guide.

==Is there a cost to open the account?==
Opening an account is completely free. The minimum amount of funds you can add is $15 USD which will become your account balance to use the services.

==Is there a Contract?==
There are no contracts with us, you can open an account for free at any time you wish, for as long as you want.

==What are the Payment Options?==
The current options available are Paypal (No Account Needed for Paypal Guest CC Payment), VISA, Master Card, American Express, and via Bank Wire deposit to our bank account in Montreal.
Please contact Customer Support for information about Bank Wire.

==Can I deposit less than $15 into my account?==
Currently $15 is the minimum amount you can add to your account. This credit won’t expire and will last until depleted by using the services.
You can ask for a refund of the remaining balance at any time within a 90 day period from your last deposit.

==Do you charge taxes?==
All customers with Canada as country will pay for the tax called GST. The customers who are also from Quebec in Canada will pay an additional province tax, PST. This applies for both Paypal and Credit Card payments.
The HST will get applied on Canadian provinces that require it.
In order to get further details about how these are applied, feel free to check this link: http://en.wikipedia.org/wiki/Sales_taxes_in_Canada

==How much does the service cost?==
The cost will vary depending on the services used.
For outbound calls you are subject to the per minute rate of the destination you call and the billing increment.
For inbound calls you are subject to the rate plan of the DID, the monthly fee and the billing increment it if applies.
There may be additional monthly fees or set up fees depending on the services you subscribe to.
Please check more details about the service cost here [[Service Cost]]

==What is the Billing Increment?==
The Billing Increment is a call duration measurement unit expressed in seconds.
For example, with our 6 seconds billing increment, a 5 second call will be billed as 6 seconds or 1/10 of 1 minute or $0.0010.
This way, you don't get charged for a whole minute just for a 10 seconds call.

With a $0.0100 per minute rate, and a 60 seconds billing increment, any call less than 60 seconds is rounded up to 60 seconds or 1 full minute of usage.
A 5 seconds call and a 50 seconds call are both billed as 1 minute or $0.0100.

==What is a DID?==
A Direct Inward Dial number (DID), in simple terms, is a virtual number that, for all intents and purposes, can be considered a regular phone number, with the exception that it is not attached to any POTS line (Landline). Once your configuration is ready, your DID will be the phone number that everyone in the world will call to reach you, just like any other phone number.

==What type of DID numbers you offer?==
There are different types of DID numbers. They are mostly differentiated by their geographic presence.
Local DIDs from US or Canada.
International DIDs.
Toll Free numbers.

These are the most common used by our customers. For further information about getting a DID number and other types please check our related article [[Order a DID Number]]

==Can I dial out with my DID?==
The DID numbers are a type of service that are exclusively for receiving calls.
When you place outgoing calls with our service you are not calling from the DID number but from the account instead and the number you will pass on your calls as your Caller ID will be the one that is configured on the accounts settings from the portal.

==What is Caller ID?==
Caller ID is a telephone service that transmits the calling party’s number to the called party’s telephone . When available, the Caller ID number can be complemented with Caller ID name (e.g. John Smith).
If you are placing outgoing calls you will likely need to pass a Caller ID to ensure proper termination of your calls, particularly to reach toll free numbers.
There are two types of caller ID and it is important to differentiate them: Caller ID Number (CID) and Caller ID Name (CNAM).
Please contact Technical Support for assistance or more details about Caller ID or check our related article at [[Caller ID]]

==What is CNAM?==
CNAM stands for CallerID Name and it's the information that will be displayed in the phone of the receiving party, when you place an outgoing call.
If you will be making calls to Canadian numbers, you can simply pass the Caller ID name from your device or system as most of them support this.
The Caller ID name on US calls works differently, this is controlled by a national CNAM database with records of numbers and names matching each number.
We can update the CNAM database under request. For more information please check our related article at [[http://wiki.voip.ms/article/Caller_ID#Outgoing_Caller_ID_name Caller ID Name]]

==Can I port my existing number from another provider to VoIP.ms?==
VoIP.ms does offer Local Number Portability (LNP) service and your number may be available for porting. Please contact Customer Service to find out whether your current number is portable to VoIP.ms network or if you already have an open account, please refer to the [[Porting a Number]] guide.

==Do you provide any hardware for the service?==
We don’t provide any kind of hardware device, software or system to use the service. The service is a BYOD (Bring your own device). You should be able to get one from any Communications specialized store and all SIP- compatible devices are supported.

==Can I use my existing device with VoIP.ms?==
Basically any device or system that supports SIP or IAX2 protocol will work with our service . If you bring your device (ATA, IP phone) from a previous provider, make sure it is unlocked and you are able to make changes to its configuration. You can find a list of some devices that we support, with their configuration guides, at [[Devices]]

==Do you have Configuration Samples?==
You can find configuration samples for most of the common devices and phone systems used with VoIP.ms here: [[Devices]]
If your device or system is not listed there but supports the protocol SIP or IAX2 and at least one of the following codecs: G711u, G729a or GSM, you should be able to use it, and you can always contact our Technical Support staff for additional assistance.

==Do you offer Technical Support by phone?==
Due to the nature of the troubleshooting which can result time consuming we chose our main ways to offer support to be via Ticket System (Email) and Live chat.
At this point, Technical Support over the phone is not available.

==What is my Main Account SIP password?==
The main account SIP password is, by default, the same as your customer portal password. If you have not changed the SIP password, it is the same password you use to log into your portal. You can change your SIP password from the Customer Portal at any time from the Main Menu - Account Settings page. Please check our related article for more information: [[http://wiki.voip.ms/article/Account_Settings#Security Account Security]]

==What Server should I use?==
Usually, in order to receive better results, you should choose the server physically closest to your location. You can also send a ping to any of the servers to check the best response time.
Please check our related article for more information about this subject [[Choosing Server]]

==Does VoIP.ms encrypt the communication?==
By default the SIP communication is secure although not encrypted, however, the passwords are MD5 hashed and are not transmitted without encryption when establishing the call. We offer Call encryption over SIP-TLS/SRTP, that we can enable as you wish for your main account/sub accounts. The communication will be encrypted between our servers and your devices/PBX. ''We suggest enabling this option if you are in a public network.''

==Do you Support e911==
We offer e911 service only for US and Canadian DID numbers (including USA and Canadian Toll-free numbers). This feature can be activated in the Customer Portal directly under the e911 page under the DID numbers menu.
More information available in our related wiki article here [[E911]]

==Do you offer Calling Card?==
We do not offer any Calling Card feature at this moment, however you can set up a Calling Card solution with your own system and our DID numbers as long as this is used with DID numbers in our Per Minute plan.
For more information please contact Technical Support.

==Do you offer Fax service?==
We offer a Virtual Fax feature. This feature can be used with special Fax DID numbers which can be acquired and configured through our Fax portal.
Please check our related article for further details: [[Virtual Fax]]

==Do you offer SMS service?==
SMS is available for a great number of DIDs and Cities from US and Canada and requires to be used through the SMS portal.

We also offer SIP SMS, providing the possibility to send and receive SMS messages from softwares and PBXes that support the functionality.

You can read more details about this feature in our related article [[SMS]]

==Do you offer Conference Calls?==
We offer Conference calls, as a feature in the customer portal. This feature is known as [[Audio Conferencing]]

==Do you support TCP for the SIP communication?==
TCP is fully supported in our servers.

==Do you Support IPV6 with SIP and or IAX2?==
We do not support at this time IPV6 for SIP and IAX2 protocol at this moment.

==Do you transmit DSCP QoS priority bits?==
Yes we do, we transmit Code CS3 for SIP and EF for RTP.

==Do you offer alternative ports besides 5060/5061?==
We offer alternative SIP ports, UDP/TCP 5080 and 42872 on all of our servers, You can try those ports in case your Internet Service Provider blocks the port 5060 UDP/TCP or if you need to use another one. For the SIP-TLS we offer alternative ports only by TCP protocol, 5061 and 42873 on all of our servers name with a number at the end. ''e.g. chicago1.voip.ms''

==Can I register 2 or more different devices with the same account username?==
It is strongly suggested not to do so, this can possibly cause conflicts while routing the calls to your device as well issues related with registration. If you need to register more than one device please create and use the Sub Accounts, you will get new credentials for any additional device.
For more information about Sub Accounts please check the related article on this subject [[Sub Accounts]]

==Do you accept Call Center, Autodialers or Telemarketing traffic ?==

The Customer covenants and agrees that if he wishes to use VoIP.ms termination (outbound) services for telemarketing purposes (including, but not limited to Automated Dialers, Call Centers and collection agencies) that he first has to reach out to sales@voip.ms to get the written authorization to do so. In the event where the Customer does not obtain the proper authorization from the Company, Customer understands that VoIP.ms will suspend such activities without warning, to its sole discretion.

==Can I resell your services ?==
Yes, our customers will be able to find a "Reseller Section" included in the Customer Portal.
We give you all the tools you need plus a White label Reseller Interface that has been developed to help our clients upsell our services under their own brand. We also recommend that you must familiarize yourself with the Voip.ms interface before reselling the service.
For more information about reseller please contact Technical Support or visit our related article here: [[Reseller Basic Guide]]

==Do you offer Wholesale Rates ?==
If you are interested on a discount based on traffic usage or volume, please send an email to sales@voip.ms providing all details about your traffic like destinations you need to call and average of minutes used per month, in order to receive additional information and quotes.

==Can I port out my number ?==
If you wish to port out a number from our service you can do so at any time by starting the porting request with the new provider. We authorize all Port Out Request matching the correct information from your account.
Remember to delete the DID number from your VoIP.ms account once the port out process is completed.
For any question regarding Port Out please send an email to our LNP Department at ports@voip.ms

==How do I delete my DID ?==
From the customer portal, go to the “DID Numbers” menu tab and then click “DID Billing”. From this page, you can cancel number(s). Remember this process cannot be reversed, please be sure that you will no longer need the number.

==Is there any Cancellation Fee ?==
We do not charge any cancellation fee of any kind, you are free to cancel your account or number at any time you wish to.

==Where are you located ?==
VoIP.ms is a Canadian Company founded back in 2007 in Montreal.
The main office is located in Montreal, QC, Canada and there is also a Technical Site in Merida, Yucatan, Mexico for the South America market.

==Do you offer a Referral Program ?==
Yes, the referral invite link, as well as all the details and information can be found in the customer portal under the '''"Finances"''' menu. You can also review the public information by clicking the following link: https://voip.ms/en/features/referral-program

== What are the audio codecs you support? ==

We support audio codecs: G722, G729a, G711u (also know as uLaw or PCMU) and GSM. Their specifications are:

Codec : '''G.722'''

Bit Rate: 64 Kbps

Nominal Ethernet Bandwidth (Kilobits) : 87.2 Kbps

Codec : '''G.711u'''

Bit Rate: 64 Kbps

Nominal Ethernet Bandwidth (Kilobits) : 87.2 Kbps

Codec : '''G.729a'''

Bit Rate: 8 Kbps

Nominal Ethernet Bandwidth (Kilobits) : 31.2 Kbps

Codec : '''GSM'''

Bit Rate: 13 kbps

Nominal Ethernet Bandwidth (Kilobits) : 29.2 kbps

[[Category: Guides]]

Choosing Server

2021-01-21T16:46:38Z

B13n: Updated IPs of WAS-1 & WAS-2

[[File:ChooseServerImg.png|thumb|none|1280px|VoIP.ms servers]]

{| class="wikitable"
|+
|-
! Article en Français !! Artículo en Español
|-
| [https://wiki.voip.ms/article/Choisir_un_serveur Français] ||
[https://wiki.voip.ms/article/Elegir_servidor Español]
|}

= Choosing a Server =

[http://www.voip.ms VoIP.ms] offers many different servers, but which one should you choose? One misconception is that you should pick the closest to your location, however this is not needed most of the time. For example, if you are in the USA, any of the US servers will provide a really good latency and service quality. The newest server within a city is indicated with the highest number attached to the name, as they are classified in ascending order. Also worth noting is that there is a network tool that will help you when deciding which server you want to use, generally named a "ping", which will provide you the latency between you and the server. Therefore the server which provides you less latency should be used.

'''Note:''' Please bear in mind that some servers might not be available for your DID number to be used as POP (Point of presence) at the ''Manage DIDs'' section.
Make sure that your SIP/IAX device and your phone number are pointing to the same server.

=== IPs ===

<div><ul>
<li style="display: inline-block; vertical-align:top;">
'''Canada'''
*Montreal 1, QC ('''montreal.voip.ms''') 192.175.96.73
*Montreal 2, QC ('''montreal2.voip.ms''') 192.175.96.74
*Montreal 3, QC ('''montreal3.voip.ms''') 192.175.96.68
*Montreal 4, QC ('''montreal4.voip.ms''') 67.205.74.179
*Montreal 5, QC ('''montreal5.voip.ms''') 192.175.96.69
*Montreal 6, QC ('''montreal6.voip.ms''') 192.175.96.70
*Montreal 7, QC ('''montreal7.voip.ms''') 192.175.96.71
*Montreal 8, QC ('''montreal8.voip.ms''') 192.175.96.72
*Montreal 9, QC ('''montreal9.voip.ms''') 67.205.74.184
*Montreal 10, QC ('''montreal10.voip.ms''') 67.205.74.187
*Toronto 1, ON ('''toronto.voip.ms''') 158.85.70.148
*Toronto 2, ON ('''toronto2.voip.ms''') 158.85.70.149
*Toronto 3, ON ('''toronto3.voip.ms''') 158.85.70.150
*Toronto 4, ON ('''toronto4.voip.ms''') 158.85.70.151
*Toronto 5, ON ('''toronto5.voip.ms''') 184.75.215.106
*Toronto 6, ON ('''toronto6.voip.ms''') 184.75.215.114
*Toronto 7, ON ('''toronto7.voip.ms''') 184.75.215.146
*Toronto 8, ON ('''toronto8.voip.ms''') 184.75.213.210
*Toronto 9, ON ('''toronto9.voip.ms''') 158.85.70.154
*Toronto 10, ON ('''toronto10.voip.ms''') 158.85.70.158
*Vancouver 1, BC ('''vancouver.voip.ms''') 162.213.157.220
*Vancouver 2, BC ('''vancouver2.voip.ms''') 162.213.157.117
*Vancouver 3, BC ('''vancouver3.voip.ms''') 162.213.157.82
</li>

<li style="display: inline-block; vertical-align:top;">
'''United States'''
*Atlanta 1, GA ('''atlanta.voip.ms''') 75.127.65.130
*Atlanta 2, GA ('''atlanta2.voip.ms''') 209.217.224.50
*Chicago 1, IL ('''chicago.voip.ms''') 69.162.175.27
*Chicago 2, IL ('''chicago2.voip.ms''') 69.162.175.28
*Chicago 3, IL ('''chicago3.voip.ms''') 69.162.175.29
*Chicago 4, IL ('''chicago4.voip.ms''') 208.100.39.55
*Chicago 5, IL ('''chicago5.voip.ms''') 50.31.115.149
*Chicago 6, IL ('''chicago6.voip.ms''') 50.31.115.150
*Chicago 7, IL ('''chicago7.voip.ms''') 50.31.115.151
*Dallas, TX ('''dallas.voip.ms''') 158.85.149.162
*Dallas 2, TX ('''dallas2.voip.ms''') 158.85.149.163
*Denver 1, CO ('''denver.voip.ms''') 23.239.211.90
*Denver 2, CO ('''denver2.voip.ms''') 64.27.52.226
*Houston, TX ('''houston.voip.ms''') 173.193.85.18
*Houston 2, TX ('''houston2.voip.ms''') 173.193.85.19
*Los Angeles 1, CA ('''losangeles.voip.ms''') 96.44.149.186
*Los Angeles 2, CA ('''losangeles2.voip.ms''') 96.44.149.202
*Los Angeles 3, CA ('''losangeles3.voip.ms''') 64.188.6.162
*Los Angeles 4, CA ('''losangeles4.voip.ms''') 64.188.6.170
*New York 1, NY ('''newyork.voip.ms''') 72.251.239.196
*New York 2, NY ('''newyork2.voip.ms''') 72.251.239.205
*New York 3, NY ('''newyork3.voip.ms''') 72.251.239.206
*New York 4, NY ('''newyork4.voip.ms''') 72.251.239.207
*New York 5, NY ('''newyork5.voip.ms''') 23.29.136.28
*New York 6, NY ('''newyork6.voip.ms''') 23.29.136.29
*New York 7, NY ('''newyork7.voip.ms''') 23.29.136.38
*New York 8, NY ('''newyork8.voip.ms''') 23.29.136.40
*San Jose, CA ('''sanjose.voip.ms''') 23.246.247.146
*San Jose 2, CA ('''sanjose2.voip.ms''') 23.246.247.147
*Seattle 1, WA ('''seattle.voip.ms''') 50.23.160.53
*Seattle 2, WA ('''seattle2.voip.ms''') 50.23.149.166
*Seattle 3, WA ('''seattle3.voip.ms''') 50.23.160.54
*Tampa, FL ('''tampa.voip.ms''') 162.254.144.173
*Tampa 2, FL ('''tampa2.voip.ms''') 162.254.144.176
*Tampa 3, FL ('''tampa3.voip.ms''') 23.111.187.139
*Tampa 4, FL ('''tampa4.voip.ms''') 23.111.166.202
*Washington 1, DC ('''washington.voip.ms''') 169.62.41.189
*Washington 2, DC ('''washington2.voip.ms''') 169.62.41.187
</li>

<li style="display: inline-block; vertical-align:top;">
'''International'''
*Amsterdam, NL ('''amsterdam.voip.ms''') 37.58.88.242
*London, UK ('''london.voip.ms''') 159.8.157.212
*Melbourne, AU ('''melbourne.voip.ms''') 168.1.73.84
*Paris, FR ('''paris.voip.ms''') 159.8.85.180
</li>
</ul></div>

===Server Realms===

For IOS, Please click here [http://wiki.voip.ms/article/Server_Realms Server Realms] to get the Realm Name for the server you plan on using, this can differ from the Domain Name being used.

= What is a Ping? =

Ping is a standard tool used to test network connections. It is mostly used to determine if a server or device can be reached across the network and the latency of the response(the time it takes to send a packet to the destination and for it to return to your computer).

Ping tools are part of Windows, Mac OS X and Linux as well as some routers.

== How does the ping work? ==

It sends request messages to a target network address or DNS names at periodic intervals and measures the time it takes for a response message to arrive and return(better known as latency).

==How to ping on a PC==

Pinging is a command which tells you if the connection between your computer and a particular domain is working correctly.

In Windows, select Start > Programs > Accessories > Command Prompt. This will give you a window like the one below.

Enter the word ping, followed by a space, then the domain name.(montreal.voip.ms) in this case domain is our server name.

If the results show a series of replies, the connection is working. The time shows you how fast the connection is. If you see a "timed out" error instead of a reply, there is a breakdown somewhere between your computer and the domain.

[[File:Ping.gif|thumb|none|600px|Ping]]

==How to ping on a Mac Computer==

1- Click on Finder in the dock.

2- Click on Applications.

3- Click on Utilities.

4- Double-click on Network Utility. *

* In OS X Mavericks (10.9.x) this utility app changed location. Launch it from spotlight instead, either press "command"+"space bar" or click on spotlight directly (magnifying glass icon at top right of screen), type "network utility" and hit "return"

5- In the Network Utility window, click on the Ping tab

6- In the field under "Please enter the network address to ping," like montreal.voip.ms

''If pings results are not consistent, you may have an issue with Jitter. You can work on this issue by adjusting the "Network Jitter Level" setting on your VoIP device. Usually a ping of under 150 ms is recommended in order to have good quality. The latency time to the server is important, however there are also other factors that could affect the quality of the calls such as packet loss (VoIP communications are very sensitive to this), and the Jitter level of your Internet connection.''

The following is the output of running ping with the target losangeles.voip.ms.

#ping losangeles.voip.ms
Ping to losangeles.voip.ms [67.215.241.250] with 32 bytes de datos:
Response from 67.215.241.250: bytes=32 time=67ms TTL=52
Response from 67.215.241.250: bytes=32 time=69ms TTL=52
Response from 67.215.241.250: bytes=32 time=68ms TTL=52
Response from 67.215.241.250: bytes=32 time=67ms TTL=52
ping statistics from 67.215.241.250:
4 packets transmitted, 4 received, 0% packet lost. rtt min/avg/max/mdev = 67ms, 69ms, 67ms

Sample ping output in windows:
C:\Windows\system32>ping montreal.voip.ms

Pinging montreal.voip.ms [67.205.74.184] with 32 bytes of data:
Reply from 67.205.74.184: bytes=32 time=85ms TTL=49
Reply from 67.205.74.184: bytes=32 time=86ms TTL=49
Reply from 67.205.74.184: bytes=32 time=86ms TTL=49
Reply from 67.205.74.184: bytes=32 time=85ms TTL=49

Ping statistics for 67.205.74.184:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 85ms, Maximum = 86ms, Average = 85ms

= Latency Testing Scripts (User Submitted) =
<p>All the following scripts were produced by voip.ms users who felt others might also benefit from the output of their efforts. They were written over a span of Years and probably need adjusting before you use them, to cater for changes in servers over time and changes in policies (like not testing heavily subscribed servers which are not open to new registrations)</p>
<p>If you aren't satisfied that the scripts are safe or simply don’t like the way they syntactically appear, you can still manually ping a selection of servers and choose a server based on the best latency. The following scripts are essentially just wrappers around the ping command which support lists of servers to feed to ping and present the output in a readable format.</p>
<p>If you feel you have a simpler cleaner script that works for another platform or language, please do add it to this wiki via a support ticket.
</p>
=== Bash Script To Handle The Mac Ping Output Format ===

<p>To make use of this script (1) save as a plain text file (2) set permissions on the file to executable (3) invoke script
e.g. Save script below using your favourite editor as pingVoipMS.sh (2) chmod u+x pingVoipMS.sh (3) ./pingVoipMS.sh
This is a bash 3.x script, so it also works in Linux, just change the ping packet loss field from 7 to 6 in the final loop below (or wherever the loss field is in your ping output format). Depending upon your distro curl might need to change to wget.
</p>
<pre>
#!/bin/bash
# Ping several servers and display Latency, Jitter and Packet Loss
# Usage: [-c <count>][-i <wait time>][-r test restricted servers][<server list file>]
#
# The optional server list text file should be formatted with one host name per line.
# The list of voip.ms servers is available at https://wiki.voip.ms/article/Choosing_Server
# If no args are supplied, this script will scrape a ping server list from voip.ms
#
USER_FILE=""
COUNT=3; INTERVAL=5; RESTRICTED=0
restrictedList=(atlanta.voip.ms chicago.voip.ms
montreal.voip.ms montreal2.voip.ms montreal3.voip.ms montreal4.voip.ms
newyork.voip.ms newyork4.voip.ms seattle.voip.ms
toronto.voip.ms toronto2.voip.ms toronto3.voip.ms toronto4.voip.ms)

# Handle any passed in script arguments
while getopts c:i:r parm
do
case $parm in
c)count_opt=$OPTARG;;
i)interval_opt=$OPTARG;;
r)RESTRICTED=1;;
*)echo -e "Invalid arg\nUsage:\t[ -c <count of ECHO_REQUESTs to Tx, default 3> ] \
\n\t[ -i <wait time (s) between datagrams, default 5> ] \
\n\t[ -r ] Include restricted servers in latency test \
\n\t[FILE <ping server list> ]";exit 1;;
esac
done

# Test if an option was specified and whether it's a +ve non-zero integer
[[ -n $count_opt && ($count_opt =~ ^[[:digit:]]+$) && $count_opt -gt 0 ]] &&
COUNT=$count_opt
[[ -n $interval_opt && ($interval_opt =~ ^[[:digit:]]+$) && $interval_opt -gt 0 ]] &&
INTERVAL=$interval_opt

shift $((OPTIND - 1))

# Validate supplied file (server list)
[[ -n $1 && ! (-f $1 && -r $1) ]] &&
{ echo "\"$1\" file does not exist or is not readable"; exit 1; }
[[ -n $1 && -f $1 && -r $1 ]] && USER_FILE="$1"

if [[ -n $USER_FILE ]]
then
# Bash 3.x in macOS does not support readarray, need to do cumbersome array loops instead
while IFS= read -r servers; do
serverList+=( "$servers" )
done < <(grep -Eo '^\b[[:alpha:]]+?[[:alnum:]]\.voip\.ms\b$' "$USER_FILE" | \
grep -v '^\s*#' | awk NF | sort)
else
# N.B. The script looks for the html boldface tags <b> </b> inside a bracket
# If the website alters and the parse fails, manually create the list and
# supply as a script arg (or perhaps update the parsing to work again :)
while IFS= read -r servers; do
serverList+=( "$servers" )
done < <(curl -sm 10 https://wiki.voip.ms/article/Choosing_Server | \
grep -E '(<b>[[:alpha:]]+?[[:alnum:]]\.voip\.ms</b>)' | \
tr "<>" " " | awk '{print $(NF-3)}' | sort )
fi

# Newer voip.ms clients can't register onto these over-subscribed servers
# Don't test the restricted list unless explicitly asked (with the -r cmd line option)
if [[ $RESTRICTED -eq 0 ]]
then
for server in "${restrictedList[@]}"
do
ix=$(printf "%s\n" "${serverList[@]}" | grep -n "^${server}" | cut -d ":" -f1)
while IFS= read -ra idx; do
keys+=( "${idx[@]}" )
done < <([[ $ix -gt 0 ]] && echo $((ix-1)))
done
for ((i=${#keys[@]} - 1; i >= 0; i--)); do unset "serverList[keys[i]]"; done
fi

if [[ ${#serverList[@]} -eq 0 ]]
then
echo "No unrestricted Voip.ms servers could be found, please supply a server list"
exit 1
fi

runTime=$((COUNT * INTERVAL * ${#serverList[@]}))

echo "PING will send $COUNT packet(s) with a wait of $INTERVAL sec(s) between each packet"
echo "Change the PING options by invoking this script with -c and/or -i, default \"-c 3 -i 5\""
echo "Over $((${#serverList[@]})) server(s) the estimated script Run Time will be $runTime seconds"
echo "================================================================"
printf "%-20s %-18s %7s %8s %6s %s\n" "VoIP Server" "IP Address" "Latency" "Jitter" "Loss" "Countdown"
echo "================================================================ (seconds)"

for myLn in "${serverList[@]}"
do
while IFS=$'\n' read -r pings; do
pingList+=( "$pings" )
printf "%-64s %5d %2d/%-2d\n" "$pings" \
"$((runTime - COUNT * INTERVAL * ${#pingList[@]}))" \
"${#pingList[@]}" "${#serverList[@]}"
done < <( ping -c "$COUNT" -i "$INTERVAL" -q "$myLn" | awk \
'
/^PING / {myH=$2}
/^PING / {
IP = substr($3,2,15)
split(IP,myIP,")") }
/packet loss/ {myPL=$7}
/min\/avg\/max/ {
split($4,myS,"/")
printf("%-20s %-18s %7.3f %8.3f %6s\n",
myH, myIP[1], myS[2], myS[4], myPL ) }
' )
done

echo "================================================================"
echo -e "\nMost appropriate server listed in order of best latency\n"
echo "================================================================"
printf "%-20s %-18s %7s %8s %6s\n" "VoIP Server" "IP Address" "Latency" "Jitter" "Loss"
echo "================================================================"
printf "%s\n" "${pingList[@]}" | LC_ALL=C sort -n -k 3,3 -k 5,5 -k 4,4 | \
awk '{printf("%s $%2d$\n",$0, NR)}'
echo "================================================================"
</pre>

=== Perl Script ===
Pings list of voip.ms servers round robin with optional output csv file.

# usage ping_voip.ms.pl <number of times> <seconds in between> <output.csv>
use Net::Ping;
use Time::HiRes;
use strict;

# input list
my @hosts = qw(
atlanta.voip.ms
atlanta2.voip.ms
chicago.voip.ms
chicago2.voip.ms
chicago3.voip.ms
chicago4.voip.ms
dallas.voip.ms
denver.voip.ms
denver2.voip.ms
houston.voip.ms
losangeles.voip.ms
losangeles2.voip.ms
newyork.voip.ms
newyork2.voip.ms
newyork3.voip.ms
newyork4.voip.ms
seattle.voip.ms
seattle2.voip.ms
seattle3.voip.ms
tampa.voip.ms
washington.voip.ms
washington2.voip.ms
montreal.voip.ms
montreal2.voip.ms
montreal3.voip.ms
montreal4.voip.ms
toronto2.voip.ms
toronto3.voip.ms
toronto4.voip.ms
toronto.voip.ms
london.voip.ms
);

$| = 1; #autoflush
# High precision syntax (requires Time::HiRes)
my $p = Net::Ping->new("icmp",1);
$p->hires();
my $max_name_length = (reverse sort { $a <=> $b } map { length($_) } @hosts)[0];
my $count = 4; # number of times to ping
my $interval = 5; # seconds between ping rounds
my $output_file = "";
my @data;

# check for arguments
my $num_args = @ARGV;
if ($num_args >= 1) {$count = $ARGV[0];}
if ($num_args >= 2) {$interval = $ARGV[1];}
if ($num_args >= 3) {$output_file = $ARGV[2];}

# check argument validity
$0 =~ /^.*\\(.*)$/;
my $script = $1;
if ($count !~ /^\d+$/ or $interval !~ /^\d+$/) {die "Usage: $script <number of rounds> <seconds between rounds> <output.csv>\n";}
if (length($output_file) > 0 and $output_file !~ /\.csv$/) {$output_file .= ".csv";}

# main loop
for my $i (1..$count)
{
sleep $interval unless $i == 1;
print "Round $i\n";
my $host_num=0;
foreach my $host (@hosts)
{
(my $ret, my $duration, my $ip) = $p->ping($host);
$ip =~ /(\d+)\.(\d+)\.(\d+)\.(\d+)/;
if ($ret)
{
printf("%*s [ip: %3s.%3s.%3s.%3s] is alive (%6.2f ms)\n", $max_name_length, $host, $1, $2, $3, $4, $duration*1000);
$data[$host_num][$i]=$duration*1000;
}
else
{
printf("%*s [ip: %3s.%3s.%3s.%3s] is dead\n", $max_name_length, $host, $1, $2, $3, $4);
}
$host_num++;
}
print "\n";
}
$p->close();

# if output file name given
if (length($output_file)>0)
{
# print output to file
open FILE, ">$output_file" or die "$!\n";

# print column headers
print FILE "Server\\Round";
for my $i (1..$count)
{
print FILE ", $i";
}
print FILE ", Average\n";

# print data
my $i = 0;
foreach my $host (@hosts)
{
print FILE "$host";
my $sum = 0;
for my $j (1..$count)
{
$sum += $data[$i][$j];
printf FILE ", %8.4f",$data[$i][$j];
}
printf FILE ", %8.4f\n",$sum/$count;
$i++;
}

close FILE;
print "Data written to $output_file\n";
}

# print summary to screen
my $i = 0;
printf("%-*s Average (ms)\n", $max_name_length, "Server");
foreach my $host (@hosts)
{
my $sum = 0;
for my $j (1..$count)
{
$sum += $data[$i][$j];
}
printf("%-*s %8.4f\n", $max_name_length+1, $host, $sum/$count);
$i++;
}

Output:
Round 1
atlanta.voip.ms [ip: 174. 34.146.162] is alive ( 88.97 ms)
atlanta2.voip.ms [ip: 72. 9.246.170] is alive ( 92.99 ms)
chicago.voip.ms [ip: 208.100. 39. 52] is alive ( 49.70 ms)
chicago2.voip.ms [ip: 208.100. 39. 53] is alive ( 59.76 ms)
chicago3.voip.ms [ip: 208.100. 39. 54] is alive ( 59.53 ms)
chicago4.voip.ms [ip: 208.100. 39. 55] is alive ( 49.73 ms)
dallas.voip.ms [ip: 74. 54. 54.178] is alive ( 94.99 ms)
denver.voip.ms [ip: 173.248.161. 90] is alive ( 94.05 ms)
denver2.voip.ms [ip: 173.248.159.210] is alive ( 85.13 ms)
houston.voip.ms [ip: 209. 62. 1. 2] is alive (102.87 ms)
losangeles.voip.ms [ip: 96. 44.149.186] is alive ( 64.92 ms)
losangeles2.voip.ms [ip: 96. 44.149.202] is alive ( 63.41 ms)
newyork.voip.ms [ip: 74. 63. 41.218] is alive (131.75 ms)
newyork2.voip.ms [ip: 107. 6. 67.236] is alive (120.64 ms)
newyork3.voip.ms [ip: 107. 6. 67.237] is alive (120.49 ms)
newyork4.voip.ms [ip: 107. 6. 67.238] is alive (111.43 ms)
seattle.voip.ms [ip: 50. 23.160. 50] is alive ( 94.25 ms)
seattle2.voip.ms [ip: 50. 23.160. 51] is alive ( 95.86 ms)
seattle3.voip.ms [ip: 50. 23.160. 52] is alive ( 90.85 ms)
tampa.voip.ms [ip: 68.233.226. 97] is alive (123.29 ms)
washington.voip.ms [ip: 208. 43.234.226] is alive ( 98.71 ms)
washington2.voip.ms [ip: 208. 43.234.227] is alive (101.19 ms)
montreal.voip.ms [ip: 67.205. 74.184] is alive ( 81.82 ms)
montreal2.voip.ms [ip: 67.205. 74.187] is alive ( 86.13 ms)
montreal3.voip.ms [ip: 72. 55.168. 18] is alive ( 77.09 ms)
montreal4.voip.ms [ip: 67.205. 74.179] is alive ( 96.18 ms)
toronto2.voip.ms [ip: 184. 75.215.114] is alive (103.70 ms)
toronto3.voip.ms [ip: 184. 75.215.146] is alive (131.27 ms)
toronto4.voip.ms [ip: 184. 75.213.210] is alive (125.13 ms)
toronto.voip.ms [ip: 184. 75.215.106] is alive (103.26 ms)
london.voip.ms [ip: 5. 77. 36.136] is alive (152.77 ms)

Round 2
atlanta.voip.ms [ip: 174. 34.146.162] is alive ( 88.14 ms)
atlanta2.voip.ms [ip: 72. 9.246.170] is alive ( 92.86 ms)
chicago.voip.ms [ip: 208.100. 39. 52] is alive ( 50.03 ms)
chicago2.voip.ms [ip: 208.100. 39. 53] is alive ( 59.44 ms)
chicago3.voip.ms [ip: 208.100. 39. 54] is alive ( 59.33 ms)
chicago4.voip.ms [ip: 208.100. 39. 55] is alive ( 50.22 ms)
dallas.voip.ms [ip: 74. 54. 54.178] is alive ( 95.58 ms)
denver.voip.ms [ip: 173.248.161. 90] is alive ( 95.94 ms)
denver2.voip.ms [ip: 173.248.159.210] is alive ( 85.29 ms)
houston.voip.ms [ip: 209. 62. 1. 2] is alive (102.73 ms)
losangeles.voip.ms [ip: 96. 44.149.186] is alive ( 65.59 ms)
losangeles2.voip.ms [ip: 96. 44.149.202] is alive ( 64.27 ms)
newyork.voip.ms [ip: 74. 63. 41.218] is alive (112.74 ms)
newyork2.voip.ms [ip: 107. 6. 67.236] is alive (121.22 ms)
newyork3.voip.ms [ip: 107. 6. 67.237] is alive (121.34 ms)
newyork4.voip.ms [ip: 107. 6. 67.238] is alive (110.75 ms)
seattle.voip.ms [ip: 50. 23.160. 50] is alive ( 94.06 ms)
seattle2.voip.ms [ip: 50. 23.160. 51] is alive ( 95.33 ms)
seattle3.voip.ms [ip: 50. 23.160. 52] is alive ( 91.58 ms)
tampa.voip.ms [ip: 68.233.226. 97] is alive (122.94 ms)
washington.voip.ms [ip: 169.62.41.189] is alive ( 98.28 ms)
washington2.voip.ms [ip: 169.62.41.187] is alive (101.40 ms)
montreal.voip.ms [ip: 67.205. 74.184] is alive ( 81.91 ms)
montreal2.voip.ms [ip: 67.205. 74.187] is alive ( 85.64 ms)
montreal3.voip.ms [ip: 72. 55.168. 18] is alive ( 75.15 ms)
montreal4.voip.ms [ip: 67.205. 74.179] is alive ( 96.79 ms)
toronto2.voip.ms [ip: 184. 75.215.114] is alive (103.10 ms)
toronto3.voip.ms [ip: 184. 75.215.146] is alive (150.85 ms)
toronto4.voip.ms [ip: 184. 75.213.210] is alive (138.40 ms)
toronto.voip.ms [ip: 184. 75.215.106] is alive (103.45 ms)
london.voip.ms [ip: 5. 77. 36.136] is alive (170.79 ms)

Round 3
atlanta.voip.ms [ip: 174. 34.146.162] is alive ( 88.76 ms)
atlanta2.voip.ms [ip: 72. 9.246.170] is alive ( 92.86 ms)
chicago.voip.ms [ip: 208.100. 39. 52] is alive ( 49.65 ms)
chicago2.voip.ms [ip: 208.100. 39. 53] is alive ( 60.01 ms)
chicago3.voip.ms [ip: 208.100. 39. 54] is alive ( 59.05 ms)
chicago4.voip.ms [ip: 208.100. 39. 55] is alive ( 49.53 ms)
dallas.voip.ms [ip: 74. 54. 54.178] is alive ( 95.82 ms)
denver.voip.ms [ip: 173.248.161. 90] is alive ( 95.02 ms)
denver2.voip.ms [ip: 173.248.159.210] is alive ( 85.60 ms)
houston.voip.ms [ip: 209. 62. 1. 2] is alive (103.35 ms)
losangeles.voip.ms [ip: 96. 44.149.186] is alive ( 65.79 ms)
losangeles2.voip.ms [ip: 96. 44.149.202] is alive ( 64.05 ms)
newyork.voip.ms [ip: 74. 63. 41.218] is alive (113.01 ms)
newyork2.voip.ms [ip: 107. 6. 67.236] is alive (121.41 ms)
newyork3.voip.ms [ip: 107. 6. 67.237] is alive (122.23 ms)
newyork4.voip.ms [ip: 107. 6. 67.238] is alive (110.62 ms)
seattle.voip.ms [ip: 50. 23.160. 50] is alive ( 93.65 ms)
seattle2.voip.ms [ip: 50. 23.160. 51] is alive ( 95.19 ms)
seattle3.voip.ms [ip: 50. 23.160. 52] is alive ( 90.75 ms)
tampa.voip.ms [ip: 68.233.226. 97] is alive (125.12 ms)
washington.voip.ms [ip: 208. 43.234.226] is alive ( 98.19 ms)
washington2.voip.ms [ip: 208. 43.234.227] is alive (101.98 ms)
montreal.voip.ms [ip: 67.205. 74.184] is alive ( 80.16 ms)
montreal2.voip.ms [ip: 67.205. 74.187] is alive ( 87.16 ms)
montreal3.voip.ms [ip: 72. 55.168. 18] is alive ( 76.54 ms)
montreal4.voip.ms [ip: 67.205. 74.179] is alive ( 97.51 ms)
toronto2.voip.ms [ip: 184. 75.215.114] is alive (104.18 ms)
toronto3.voip.ms [ip: 184. 75.215.146] is alive (142.81 ms)
toronto4.voip.ms [ip: 184. 75.213.210] is alive (138.95 ms)
toronto.voip.ms [ip: 184. 75.215.106] is alive (103.78 ms)
london.voip.ms [ip: 5. 77. 36.136] is alive (153.14 ms)

Round 4
atlanta.voip.ms [ip: 174. 34.146.162] is alive ( 89.19 ms)
atlanta2.voip.ms [ip: 72. 9.246.170] is alive ( 92.98 ms)
chicago.voip.ms [ip: 208.100. 39. 52] is alive ( 49.21 ms)
chicago2.voip.ms [ip: 208.100. 39. 53] is alive ( 60.50 ms)
chicago3.voip.ms [ip: 208.100. 39. 54] is alive ( 59.68 ms)
chicago4.voip.ms [ip: 208.100. 39. 55] is alive ( 50.18 ms)
dallas.voip.ms [ip: 74. 54. 54.178] is alive ( 93.93 ms)
denver.voip.ms [ip: 173.248.161. 90] is alive ( 94.22 ms)
denver2.voip.ms [ip: 173.248.159.210] is alive ( 85.10 ms)
houston.voip.ms [ip: 209. 62. 1. 2] is alive (103.67 ms)
losangeles.voip.ms [ip: 96. 44.149.186] is alive ( 65.58 ms)
losangeles2.voip.ms [ip: 96. 44.149.202] is alive ( 63.60 ms)
newyork.voip.ms [ip: 74. 63. 41.218] is alive (114.76 ms)
newyork2.voip.ms [ip: 107. 6. 67.236] is alive (120.44 ms)
newyork3.voip.ms [ip: 107. 6. 67.237] is alive (121.05 ms)
newyork4.voip.ms [ip: 107. 6. 67.238] is alive (110.51 ms)
seattle.voip.ms [ip: 50. 23.160. 50] is alive ( 94.04 ms)
seattle2.voip.ms [ip: 50. 23.160. 51] is alive ( 96.92 ms)
seattle3.voip.ms [ip: 50. 23.160. 52] is alive ( 91.23 ms)
tampa.voip.ms [ip: 68.233.226. 97] is alive (123.28 ms)
washington.voip.ms [ip: 208. 43.234.226] is alive ( 98.45 ms)
washington2.voip.ms [ip: 208. 43.234.227] is alive (100.94 ms)
montreal.voip.ms [ip: 67.205. 74.184] is alive ( 82.33 ms)
montreal2.voip.ms [ip: 67.205. 74.187] is alive ( 85.02 ms)
montreal3.voip.ms [ip: 72. 55.168. 18] is alive ( 76.85 ms)
montreal4.voip.ms [ip: 67.205. 74.179] is alive ( 96.32 ms)
toronto2.voip.ms [ip: 184. 75.215.114] is alive (104.22 ms)
toronto3.voip.ms [ip: 184. 75.215.146] is alive (148.33 ms)
toronto4.voip.ms [ip: 184. 75.213.210] is alive (141.61 ms)
toronto.voip.ms [ip: 184. 75.215.106] is alive (105.91 ms)
london.voip.ms [ip: 5. 77. 36.136] is alive (152.85 ms)

Server Average (ms)
atlanta.voip.ms 88.7630
atlanta2.voip.ms 92.9233
chicago.voip.ms 49.6477
chicago2.voip.ms 59.9305
chicago3.voip.ms 59.3972
chicago4.voip.ms 49.9152
dallas.voip.ms 95.0790
denver.voip.ms 94.8077
denver2.voip.ms 85.2797
houston.voip.ms 103.1562
losangeles.voip.ms 65.4693
losangeles2.voip.ms 63.8347
newyork.voip.ms 118.0643
newyork2.voip.ms 120.9265
newyork3.voip.ms 121.2778
newyork4.voip.ms 110.8275
seattle.voip.ms 93.9993
seattle2.voip.ms 95.8267
seattle3.voip.ms 91.1035
tampa.voip.ms 123.6570
washington.voip.ms 98.4065
washington2.voip.ms 101.3774
montreal.voip.ms 81.5525
montreal2.voip.ms 85.9863
montreal3.voip.ms 76.4058
montreal4.voip.ms 96.7013
toronto2.voip.ms 103.7986
toronto3.voip.ms 143.3156
toronto4.voip.ms 136.0254
toronto.voip.ms 104.1012
london.voip.ms 157.3885

=== Powershell ===

Dec 2017 - A bug in the code shown washington2.voip.ms as the best server, this was corrected.

<pre>
# Usage: Copy and paste the following code into a powershell window
# To run it from a command prompt, save this file with extension ps1.
# Then run Powershell.exe -file "pathtothisscript.ps1"
Clear-Variable best* -Scope Global #Clear the best* variables in case you run it more than once...
#Get the list of servers into an array
$Servers =
@("amsterdam.voip.ms","atlanta.voip.ms","atlanta2.voip.ms","chicago.voip.ms","chicago2.voip.ms","chicago3.voip.ms",
"chicago4.voip.ms","dallas.voip.ms","dallas2.voip.ms","denver.voip.ms","denver2.voip.ms","houston.voip.ms",
"houston2.voip.ms","london.voip.ms","losangeles.voip.ms","losangeles2.voip.ms","melbourne.voip.ms","montreal.voip.ms",
"montreal2.voip.ms","montreal3.voip.ms","montreal4.voip.ms","montreal5.voip.ms","montreal6.voip.ms","montreal7.voip.ms",
"montreal8.voip.ms","newyork.voip.ms","newyork2.voip.ms","newyork3.voip.ms","newyork4.voip.ms","newyork5.voip.ms",
"newyork6.voip.ms","newyork7.voip.ms","newyork8.voip.ms","paris.voip.ms","sanjose.voip.ms","sanjose2.voip.ms",
"seattle.voip.ms","seattle2.voip.ms","seattle3.voip.ms","tampa.voip.ms","tampa2.voip.ms","toronto.voip.ms",
"toronto2.voip.ms","toronto3.voip.ms","toronto4.voip.ms","toronto5.voip.ms","toronto6.voip.ms","toronto7.voip.ms",
"toronto8.voip.ms","vancouver.voip.ms","vancouver2.voip.ms","washington.voip.ms","washington2.voip.ms")
$k = 0 #Counting variable so we know what server number we are testing
#num of servers to test
$servercount = $servers.length
#Do the following code for each server in our array
ForEach($server in $servers)
{
#Add one to the counting variable....we are on server #1...then server 2, then server 3 etc...
$k++
#Update the progress bar
Write-Progress -Activity "Testing Server: ${server}" -status "Testing Server $k out of $servercount" -percentComplete ($k / $servercount*100)
#Counting variable for number of times we tried to ping a given server
$i = 0
Do{
#assume a failure
$pingsuccess = $false
$i++ #Add one to the counting variable.....1st try....2nd try....3rd try etc...
Try{
#Try to ping
$currentping = (test-connection $server -count 1 -ErrorAction Stop).responsetime
#If success full, set success variable
$pingsuccess = $true
}
#Catch the failure and set the success variable to false
Catch {
$pingsuccess = $false
}
}
#Try everything between Do and While up to 5 times, or while $pingsuccess is not true
While($pingsuccess -eq $false -and $i -le 5)
#Compare the last ping test with the best known ping test....if there is no known best ping test, assume this one is the best $bestping = $currentping
If($pingsuccess -and ($currentping -lt $bestping -or (!($bestping)))){
#If this is the best ping...save it
$bestserver = $server #Save the best server
$bestping = $currentping #Save the best ping results
}
write-host "tested: $server at $currentping ms after $i attempts" #write the results of the test for this server
}
write-host "`r`n The server with the best ping is: $bestserver at $bestping ms`r`n" #write the end result
Pause
</pre>

=== Linux Shell Script ===
Pings several voip.ms servers

#!/bin/sh
# Ping several servers and display Latency, Jitter and Packet Loss
#
# First, create a text file with all servers you want to ping - one host name per line.
# The list of voip.ms servers is available at http://wiki.voip.ms/article/Choosing_Server
myHF="voip_ping_hosts.txt"
# Sample file:
# toronto.voip.ms
# montreal.voip.ms
# seattle.voip.ms
# chicago.voip.ms
# newyork.voip.ms
#
echo "============================================"
printf "%-20s %7s %8s %6s\n" "VoIP Server" "Latency" "Jitter" "Loss"
echo "============================================"
cat ${myHF} |\
while read myLn
do
ping -c 3 -i 5 -q $myLn |\
awk '/^PING / {myH=$2}
/packet loss/ {myPL=$6}
/min\/avg\/max/ {
split($4,myS,"/")
printf( "%-20s %3.1f %1.3f %4s\n", myH, myS[2], myS[4], myPL)
}'
done
echo "============================================"

Output:

============================================
VoIP Server Latency Jitter Loss
============================================
toronto.voip.ms 68.3 0.439 0%
montreal.voip.ms 89.6 0.197 0%
seattle.voip.ms 71.2 0.387 0%
chicago.voip.ms 71.6 0.084 0%
newyork.voip.ms 79.1 0.411 0%
============================================

= Latency and its importance =

Latency is very important for Voip, this will determine the time that will take for the data package transmission to reach the destination. A high latency will lead to a delay and echoes in the communication.

Latency is measured in milliseconds (ms) For example: a latency of 150ms is barely noticeable, thus acceptable. Higher than that, quality starts to suffer. When it gets higher than 300 ms, it becomes unacceptable.

[[category:guides]]

Grandstream DP750/DP720

2020-11-03T14:21:46Z

B13n:

== Grandstream DP750 Configuration Detail (Applies to model DP752 too) ==

[[File:DP750-720.png|thumb|none|600px]]

1. Type the DP715 Base Station IP address in your PC browser e.g. ''http://192.168.2.1''

2. Log in using username and password of "admin" to configure the DP750 Base Station.

3. Navigate to the Profiles > Profiles 1, and select ' '''General Settings''' '.

[[File:DP750-Profile1-General.png|thumb|none|600px]]

* Select a name. This is only for your own use.
* One of VoIP.ms multiple [[Choosing Server | servers]], you can choose the one closest to your location
* Click on the '''Save and Apply''' button.

4. Navigate to the SIP Settings > Basic Settings menu on the left.

[[File:Sip_-_Basic_Settings_-_1.png|thumb|none|600px]]

* Select either '''UDP''', or if your account is configured to use [[Call_Encryption_-_TLS/SRTP | SRTP encryption]], select '''TLS/TCP'''.
* Set the Local SIP Port to 5060 for UDP, if your account is configured to use [[Call_Encryption_-_TLS/SRTP | SRTP encryption]], use the port 5061.
* Click on the '''Save and Apply''' button.

[[File:Profile_1_sip_basic_2.png|thumb|none|600px]]

5. Navigate to the Profiles > Profile 1 > '''Audio Settings'''.

[[File:Profile_1_Audio_Settings.png|thumb|none|600px]]

* Select both '''In-Audio''' and '''via RTP''' for the send DTMF option.

[[File:Profile_1_Audio_2.png|thumb|none|600px]]

* If you are using '''SRTP / TLS/TCP''', ensure the '''SRTP Mode''' option is set to '''Enabled and Forced'''.
* Click on the '''Save and Apply''' button.

6. Navigate to '''DECT''' > '''Sip Account Settings'''.

[[File:Sip_Account_Settings.png|thumb|none|600px]]

* In the Account 1 line, enter your SIP User ID into both the '''SIP User ID''' and '''Authenticate ID''' fields.
* Enter the password for the SIP account in the password field.
* Enter a name for the SIP account in the '''Name''' field. This your '''Outbound Caller ID Name''' when you call a Canadian number which will be displayed on the Display screen.

* Click on the '''Save and Apply''' button.

'''IMPORTANT INFO FOR CALLER ID NAME''':
- We suggest entering your outbound Caller ID Name must be in '''capital letters'''. This will appears more clearly/visible on some devices.
- You must NOT use any special characters, they will not be displayed.
- Some of regular Canadian providers will not show more than 15 characters. We suggest shrinking or adapt your caller ID.
- Spaces are allowed in a caller id name.

7. Navigate to '''DECT''' > '''Handset Line Settings'''.

[[File:Handset_Line_Settings.png|thumb|none|600px]]

* Ensure the SIP account that you created in step 6 is select in the '''Line 1''' column for each handset.
* Click on the '''Save and Apply''' button.

==Guide Links==
In the event where you need the guides directly from Grandstream, you may find the user and admin manual guides below:

User Manual : [http://www.grandstream.com/sites/default/files/Resources/DP750_DP720_User_Guide.pdf Download PDF]

Admin Manual : [http://www.grandstream.com/sites/default/files/Resources/DP750_DP720_Administration_Guide.pdf Download PDF]

Servers

2020-09-03T15:08:11Z

B13n:

<div style="text-align:center; font-family:Arial; font-size:200%">
This page only shows the [http://www.voip.ms VoIP.ms] servers name, domain, and IP. For further information about how to properly select the best option for you, please refer to our wiki entry "[[Choosing Server]]"
</div>

== Canada ==

{| class="wikitable" style="border: none; width: 60%; height: 200px; text-align: justify;"
! colspan="3" | Canada Servers
|-
! scope="col" | Server's name
! scope="col" | Server's domain
! scope="col" | Server's IP
|-
|Montreal 1, QC || '''montreal.voip.ms''' || 67.205.74.184
|-
|Montreal 2, QC || '''montreal2.voip.ms''' || 67.205.74.187
|-
|Montreal 3, QC || '''montreal3.voip.ms''' || 192.175.96.68
|-
|Montreal 4, QC || '''montreal4.voip.ms''' || 67.205.74.179
|-
|Montreal 5, QC || '''montreal5.voip.ms''' || 192.175.96.69
|-
|Montreal 6, QC || '''montreal6.voip.ms''' || 192.175.96.70
|-
|Montreal 7, QC || '''montreal7.voip.ms''' || 192.175.96.71
|-
|Montreal 8, QC || '''montreal8.voip.ms''' || 192.175.96.72
|-
|Montreal 9, QC || '''montreal9.voip.ms''' || 67.205.74.184
|-
|Montreal 10, QC || '''montreal10.voip.ms''' || 67.205.74.187
|-
|Toronto 1, ON || '''toronto.voip.ms''' || 158.85.70.148
|-
|Toronto 2, ON || '''toronto2.voip.ms''' || 158.85.70.149
|-
|Toronto 3, ON || '''toronto3.voip.ms''' || 158.85.70.150
|-
|Toronto 4, ON || '''toronto4.voip.ms''' || 158.85.70.151
|-
|Toronto 5, ON || '''toronto5.voip.ms''' || 184.75.215.106
|-
|Toronto 6, ON || '''toronto6.voip.ms''' || 184.75.215.114
|-
|Toronto 7, ON || '''toronto7.voip.ms''' || 184.75.215.146
|-
|Toronto 8, ON || '''toronto8.voip.ms''' || 184.75.213.210
|-
|Toronto 9, ON || '''toronto9.voip.ms''' || 158.85.70.154
|-
|Toronto 10, ON || '''toronto10.voip.ms''' || 158.85.70.158
|-
|Vancouver 1, BC || '''vancouver.voip.ms''' || 162.213.157.220
|-
|Vancouver 2, BC || '''vancouver2.voip.ms''' || 162.213.157.117
|-
|Vancouver 3, BC || '''vancouver3.voip.ms''' || 162.213.157.82
|}

== USA ==

{| class="wikitable" style="border: none; width: 60%; height: 200px; text-align: justify;"
! colspan="3" | USA Servers
|-
! scope="col" | Server's name
! scope="col" | Server's domain
! scope="col" | Server's IP
|-
| Atlanta 1, GA || '''atlanta.voip.ms'''|| 75.127.65.130
|-
| Atlanta 2, GA || '''atlanta2.voip.ms'''|| 72.9.246.170
|-
| Chicago 1, IL || '''chicago.voip.ms'''|| 69.162.175.27
|-
| Chicago 2, IL || '''chicago2.voip.ms'''|| 69.162.175.28
|-
| Chicago 3, IL || '''chicago3.voip.ms'''|| 69.162.175.29
|-
| Chicago 4, IL || '''chicago4.voip.ms'''|| 208.100.39.55
|-
| Chicago 5, IL || '''chicago5.voip.ms'''|| 50.31.115.149
|-
| Chicago 6, IL || '''chicago6.voip.ms'''|| 50.31.115.150
|-
| Chicago 7, IL || '''chicago7.voip.ms'''|| 50.31.115.151
|-
| Dallas, TX || '''dallas.voip.ms'''|| 158.85.149.162
|-
| Dallas 2, TX || '''dallas2.voip.ms'''|| 158.85.149.163
|-
| Denver 1, CO || '''denver.voip.ms'''|| 23.239.211.90
|-
| Denver 2, CO || '''denver2.voip.ms'''|| 64.27.52.226
|-
| Houston, TX || '''houston.voip.ms'''|| 173.193.85.18
|-
| Houston 2, TX || '''houston2.voip.ms'''|| 173.193.85.19
|-
| Los Angeles 1, CA || '''losangeles.voip.ms'''|| 96.44.149.186
|-
| Los Angeles 2, CA || '''losangeles2.voip.ms'''|| 96.44.149.202
|-
| Los Angeles 3, CA || '''losangeles3.voip.ms'''|| 64.188.6.162
|-
| Los Angeles 4, CA || '''losangeles4.voip.ms'''|| 64.188.6.170
|-
| New York 1, NY || '''newyork.voip.ms'''|| 72.251.239.196
|-
| New York 2, NY || '''newyork2.voip.ms'''|| 72.251.239.205
|-
| New York 3, NY || '''newyork3.voip.ms'''|| 72.251.239.206
|-
| New York 4, NY || '''newyork4.voip.ms'''|| 72.251.239.207
|-
| New York 5, NY || '''newyork5.voip.ms'''|| 23.29.136.28
|-
| New York 6, NY || '''newyork6.voip.ms'''|| 23.29.136.29
|-
| New York 7, NY || '''newyork7.voip.ms'''|| 23.29.136.38
|-
| New York 8, NY || '''newyork8.voip.ms'''|| 23.29.136.40
|-
| San Jose, CA || '''sanjose.voip.ms'''|| 23.246.247.146
|-
| San Jose 2, CA || '''sanjose2.voip.ms'''|| 23.246.247.147
|-
| Seattle 1, WA || '''seattle.voip.ms'''|| 50.23.160.53
|-
| Seattle 2, WA || '''seattle2.voip.ms'''|| 50.23.149.166
|-
| Seattle 3, WA || '''seattle3.voip.ms'''|| 50.23.160.54
|-
| Tampa, FL || '''tampa.voip.ms'''|| 162.254.144.173
|-
| Tampa 2, FL || '''tampa2.voip.ms'''|| 162.254.144.176
|-
| Tampa 3, FL || '''tampa3.voip.ms'''|| 23.111.187.139
|-
| Tampa 4, FL || '''tampa4.voip.ms'''|| 23.111.166.202
|-
| Washington 1, DC || '''washington.voip.ms'''|| 208.43.234.226
|-
| Washington 2, DC || '''washington2.voip.ms'''|| 208.43.234.227
|}

== International ==

{| class="wikitable" style="border: none; width: 60%; height: 200px; text-align: justify;"
! colspan="3" | International Servers
|-
! scope="col" | Server's name
! scope="col" | Server's domain
! scope="col" | Server's IP
|-
|Amsterdam, NL || '''amsterdam.voip.ms''' || 37.58.88.242
|-
|London, UK || '''london.voip.ms''' || 159.8.157.212
|-
|Melbourne, AU || '''melbourne.voip.ms''' || 168.1.73.84
|-
|Paris, FR || '''paris.voip.ms''' || 159.8.85.180
|}

Choosing Server

2020-09-03T15:06:03Z

B13n:

[[File:ChooseServerImg.png|thumb|none|1280px|VoIP.ms servers]]

= Choosing a Server =

[http://www.voip.ms VoIP.ms] offers many different servers, but which one should you choose? One misconception is that you should pick the closest to your location, however this is not needed most of the time. For example, if you are in the USA, any of the US servers will provide a really good latency and service quality. The newest server within a city is indicated with the highest number attached to the name, as they are classified in ascending order. Also worth noting is that there is a network tool that will help you when deciding which server you want to use, generally named a "ping", which will provide you the latency between you and the server. Therefore the server which provides you less latency should be used.

'''Note:''' Please bear in mind that some servers might not be available for your DID number to be used as POP (Point of presence) at the ''Manage DIDs'' section.
Make sure that your SIP/IAX device and your phone number are pointing to the same server.

=== IPs ===

<div><ul>
<li style="display: inline-block; vertical-align:top;">
'''Canada'''
*Montreal 1, QC ('''montreal.voip.ms''') 192.175.96.73
*Montreal 2, QC ('''montreal2.voip.ms''') 192.175.96.74
*Montreal 3, QC ('''montreal3.voip.ms''') 192.175.96.68
*Montreal 4, QC ('''montreal4.voip.ms''') 67.205.74.179
*Montreal 5, QC ('''montreal5.voip.ms''') 192.175.96.69
*Montreal 6, QC ('''montreal6.voip.ms''') 192.175.96.70
*Montreal 7, QC ('''montreal7.voip.ms''') 192.175.96.71
*Montreal 8, QC ('''montreal8.voip.ms''') 192.175.96.72
*Montreal 9, QC ('''montreal9.voip.ms''') 67.205.74.184
*Montreal 10, QC ('''montreal10.voip.ms''') 67.205.74.187
*Toronto 1, ON ('''toronto.voip.ms''') 158.85.70.148
*Toronto 2, ON ('''toronto2.voip.ms''') 158.85.70.149
*Toronto 3, ON ('''toronto3.voip.ms''') 158.85.70.150
*Toronto 4, ON ('''toronto4.voip.ms''') 158.85.70.151
*Toronto 5, ON ('''toronto5.voip.ms''') 184.75.215.106
*Toronto 6, ON ('''toronto6.voip.ms''') 184.75.215.114
*Toronto 7, ON ('''toronto7.voip.ms''') 184.75.215.146
*Toronto 8, ON ('''toronto8.voip.ms''') 184.75.213.210
*Toronto 9, ON ('''toronto9.voip.ms''') 158.85.70.154
*Toronto 10, ON ('''toronto10.voip.ms''') 158.85.70.158
*Vancouver 1, BC ('''vancouver.voip.ms''') 162.213.157.220
*Vancouver 2, BC ('''vancouver2.voip.ms''') 162.213.157.117
*Vancouver 3, BC ('''vancouver3.voip.ms''') 162.213.157.82
</li>

<li style="display: inline-block; vertical-align:top;">
'''United States'''
*Atlanta 1, GA ('''atlanta.voip.ms''') 75.127.65.130
*Atlanta 2, GA ('''atlanta2.voip.ms''') 209.217.224.50
*Chicago 1, IL ('''chicago.voip.ms''') 69.162.175.27
*Chicago 2, IL ('''chicago2.voip.ms''') 69.162.175.28
*Chicago 3, IL ('''chicago3.voip.ms''') 69.162.175.29
*Chicago 4, IL ('''chicago4.voip.ms''') 208.100.39.55
*Chicago 5, IL ('''chicago5.voip.ms''') 50.31.115.149
*Chicago 6, IL ('''chicago6.voip.ms''') 50.31.115.150
*Chicago 7, IL ('''chicago7.voip.ms''') 50.31.115.151
*Dallas, TX ('''dallas.voip.ms''') 158.85.149.162
*Dallas 2, TX ('''dallas2.voip.ms''') 158.85.149.163
*Denver 1, CO ('''denver.voip.ms''') 23.239.211.90
*Denver 2, CO ('''denver2.voip.ms''') 64.27.52.226
*Houston, TX ('''houston.voip.ms''') 173.193.85.18
*Houston 2, TX ('''houston2.voip.ms''') 173.193.85.19
*Los Angeles 1, CA ('''losangeles.voip.ms''') 96.44.149.186
*Los Angeles 2, CA ('''losangeles2.voip.ms''') 96.44.149.202
*Los Angeles 3, CA ('''losangeles3.voip.ms''') 64.188.6.162
*Los Angeles 4, CA ('''losangeles4.voip.ms''') 64.188.6.170
*New York 1, NY ('''newyork.voip.ms''') 72.251.239.196
*New York 2, NY ('''newyork2.voip.ms''') 72.251.239.205
*New York 3, NY ('''newyork3.voip.ms''') 72.251.239.206
*New York 4, NY ('''newyork4.voip.ms''') 72.251.239.207
*New York 5, NY ('''newyork5.voip.ms''') 23.29.136.28
*New York 6, NY ('''newyork6.voip.ms''') 23.29.136.29
*New York 7, NY ('''newyork7.voip.ms''') 23.29.136.38
*New York 8, NY ('''newyork8.voip.ms''') 23.29.136.40
*San Jose, CA ('''sanjose.voip.ms''') 23.246.247.146
*San Jose 2, CA ('''sanjose2.voip.ms''') 23.246.247.147
*Seattle 1, WA ('''seattle.voip.ms''') 50.23.160.53
*Seattle 2, WA ('''seattle2.voip.ms''') 50.23.149.166
*Seattle 3, WA ('''seattle3.voip.ms''') 50.23.160.54
*Tampa, FL ('''tampa.voip.ms''') 162.254.144.173
*Tampa 2, FL ('''tampa2.voip.ms''') 162.254.144.176
*Tampa 3, FL ('''tampa3.voip.ms''') 23.111.187.139
*Tampa 4, FL ('''tampa4.voip.ms''') 23.111.166.202
*Washington 1, DC ('''washington.voip.ms''') 208.43.234.226
*Washington 2, DC ('''washington2.voip.ms''') 208.43.234.227
</li>

<li style="display: inline-block; vertical-align:top;">
'''International'''
*Amsterdam, NL ('''amsterdam.voip.ms''') 37.58.88.242
*London, UK ('''london.voip.ms''') 159.8.157.212
*Melbourne, AU ('''melbourne.voip.ms''') 168.1.73.84
*Paris, FR ('''paris.voip.ms''') 159.8.85.180
</li>
</ul></div>

===Server Realms===

For IOS, Please click here [http://wiki.voip.ms/article/Server_Realms Server Realms] to get the Realm Name for the server you plan on using, this can differ from the Domain Name being used.

= What is a Ping? =

Ping is a standard tool used to test network connections. It is mostly used to determine if a server or device can be reached across the network and the latency of the response(the time it takes to send a packet to the destination and for it to return to your computer).

Ping tools are part of Windows, Mac OS X and Linux as well as some routers.

== How does the ping work? ==

It sends request messages to a target network address or DNS names at periodic intervals and measures the time it takes for a response message to arrive and return(better known as latency).

==How to ping on a PC==

Pinging is a command which tells you if the connection between your computer and a particular domain is working correctly.

In Windows, select Start > Programs > Accessories > Command Prompt. This will give you a window like the one below.

Enter the word ping, followed by a space, then the domain name.(montreal.voip.ms) in this case domain is our server name.

If the results show a series of replies, the connection is working. The time shows you how fast the connection is. If you see a "timed out" error instead of a reply, there is a breakdown somewhere between your computer and the domain.

[[File:Ping.gif|thumb|none|600px|Ping]]

==How to ping on a Mac Computer==

1- Click on Finder in the dock.

2- Click on Applications.

3- Click on Utilities.

4- Double-click on Network Utility. *

* In OS X Mavericks (10.9.x) this utility app changed location. Launch it from spotlight instead, either press "command"+"space bar" or click on spotlight directly (magnifying glass icon at top right of screen), type "network utility" and hit "return"

5- In the Network Utility window, click on the Ping tab

6- In the field under "Please enter the network address to ping," like montreal.voip.ms

''If pings results are not consistent, you may have an issue with Jitter. You can work on this issue by adjusting the "Network Jitter Level" setting on your VoIP device. Usually a ping of under 150 ms is recommended in order to have good quality. The latency time to the server is important, however there are also other factors that could affect the quality of the calls such as packet loss (VoIP communications are very sensitive to this), and the Jitter level of your Internet connection.''

The following is the output of running ping with the target losangeles.voip.ms.

#ping losangeles.voip.ms
Ping to losangeles.voip.ms [67.215.241.250] with 32 bytes de datos:
Response from 67.215.241.250: bytes=32 time=67ms TTL=52
Response from 67.215.241.250: bytes=32 time=69ms TTL=52
Response from 67.215.241.250: bytes=32 time=68ms TTL=52
Response from 67.215.241.250: bytes=32 time=67ms TTL=52
ping statistics from 67.215.241.250:
4 packets transmitted, 4 received, 0% packet lost. rtt min/avg/max/mdev = 67ms, 69ms, 67ms

Sample ping output in windows:
C:\Windows\system32>ping montreal.voip.ms

Pinging montreal.voip.ms [67.205.74.184] with 32 bytes of data:
Reply from 67.205.74.184: bytes=32 time=85ms TTL=49
Reply from 67.205.74.184: bytes=32 time=86ms TTL=49
Reply from 67.205.74.184: bytes=32 time=86ms TTL=49
Reply from 67.205.74.184: bytes=32 time=85ms TTL=49

Ping statistics for 67.205.74.184:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 85ms, Maximum = 86ms, Average = 85ms

= Latency Testing Scripts (User Submitted) =
<p>All the following scripts were produced by voip.ms users who felt others might also benefit from the output of their efforts. They were written over a span of Years and probably need adjusting before you use them, to cater for changes in servers over time and changes in policies (like not testing heavily subscribed servers which are not open to new registrations)</p>
<p>If you aren't satisfied that the scripts are safe or simply don’t like the way they syntactically appear, you can still manually ping a selection of servers and choose a server based on the best latency. The following scripts are essentially just wrappers around the ping command which support lists of servers to feed to ping and present the output in a readable format.</p>
<p>If you feel you have a simpler cleaner script that works for another platform or language, please do add it to this wiki via a support ticket.
</p>
=== Bash Script To Handle The Mac Ping Output Format ===

<p>To make use of this script (1) save as a plain text file (2) set permissions on the file to executable (3) invoke script
e.g. Save script below using your favourite editor as pingVoipMS.sh (2) chmod u+x pingVoipMS.sh (3) ./pingVoipMS.sh
This is a bash 3.x script, so it also works in Linux, just change the ping packet loss field from 7 to 6 in the final loop below (or wherever the loss field is in your ping output format). Depending upon your distro curl might need to change to wget.
</p>
<pre>
#!/bin/bash
# Ping several servers and display Latency, Jitter and Packet Loss
# Usage: [-c <count>][-i <wait time>][-r test restricted servers][<server list file>]
#
# The optional server list text file should be formatted with one host name per line.
# The list of voip.ms servers is available at https://wiki.voip.ms/article/Choosing_Server
# If no args are supplied, this script will scrape a ping server list from voip.ms
#
USER_FILE=""
COUNT=3; INTERVAL=5; RESTRICTED=0
restrictedList=(atlanta.voip.ms chicago.voip.ms
montreal.voip.ms montreal2.voip.ms montreal3.voip.ms montreal4.voip.ms
newyork.voip.ms newyork4.voip.ms seattle.voip.ms
toronto.voip.ms toronto2.voip.ms toronto3.voip.ms toronto4.voip.ms)

# Handle any passed in script arguments
while getopts c:i:r parm
do
case $parm in
c)count_opt=$OPTARG;;
i)interval_opt=$OPTARG;;
r)RESTRICTED=1;;
*)echo -e "Invalid arg\nUsage:\t[ -c <count of ECHO_REQUESTs to Tx, default 3> ] \
\n\t[ -i <wait time (s) between datagrams, default 5> ] \
\n\t[ -r ] Include restricted servers in latency test \
\n\t[FILE <ping server list> ]";exit 1;;
esac
done

# Test if an option was specified and whether it's a +ve non-zero integer
[[ -n $count_opt && ($count_opt =~ ^[[:digit:]]+$) && $count_opt -gt 0 ]] &&
COUNT=$count_opt
[[ -n $interval_opt && ($interval_opt =~ ^[[:digit:]]+$) && $interval_opt -gt 0 ]] &&
INTERVAL=$interval_opt

shift $((OPTIND - 1))

# Validate supplied file (server list)
[[ -n $1 && ! (-f $1 && -r $1) ]] &&
{ echo "\"$1\" file does not exist or is not readable"; exit 1; }
[[ -n $1 && -f $1 && -r $1 ]] && USER_FILE="$1"

if [[ -n $USER_FILE ]]
then
# Bash 3.x in macOS does not support readarray, need to do cumbersome array loops instead
while IFS= read -r servers; do
serverList+=( "$servers" )
done < <(grep -Eo '^\b[[:alpha:]]+?[[:alnum:]]\.voip\.ms\b$' "$USER_FILE" | \
grep -v '^\s*#' | awk NF | sort)
else
# N.B. The script looks for the html boldface tags <b> </b> inside a bracket
# If the website alters and the parse fails, manually create the list and
# supply as a script arg (or perhaps update the parsing to work again :)
while IFS= read -r servers; do
serverList+=( "$servers" )
done < <(curl -sm 10 https://wiki.voip.ms/article/Choosing_Server | \
grep -E '(<b>[[:alpha:]]+?[[:alnum:]]\.voip\.ms</b>)' | \
tr "<>" " " | awk '{print $(NF-3)}' | sort )
fi

# Newer voip.ms clients can't register onto these over-subscribed servers
# Don't test the restricted list unless explicitly asked (with the -r cmd line option)
if [[ $RESTRICTED -eq 0 ]]
then
for server in "${restrictedList[@]}"
do
ix=$(printf "%s\n" "${serverList[@]}" | grep -n "^${server}" | cut -d ":" -f1)
while IFS= read -ra idx; do
keys+=( "${idx[@]}" )
done < <([[ $ix -gt 0 ]] && echo $((ix-1)))
done
for ((i=${#keys[@]} - 1; i >= 0; i--)); do unset "serverList[keys[i]]"; done
fi

if [[ ${#serverList[@]} -eq 0 ]]
then
echo "No unrestricted Voip.ms servers could be found, please supply a server list"
exit 1
fi

runTime=$((COUNT * INTERVAL * ${#serverList[@]}))

echo "PING will send $COUNT packet(s) with a wait of $INTERVAL sec(s) between each packet"
echo "Change the PING options by invoking this script with -c and/or -i, default \"-c 3 -i 5\""
echo "Over $((${#serverList[@]})) server(s) the estimated script Run Time will be $runTime seconds"
echo "================================================================"
printf "%-20s %-18s %7s %8s %6s %s\n" "VoIP Server" "IP Address" "Latency" "Jitter" "Loss" "Countdown"
echo "================================================================ (seconds)"

for myLn in "${serverList[@]}"
do
while IFS=$'\n' read -r pings; do
pingList+=( "$pings" )
printf "%-64s %5d %2d/%-2d\n" "$pings" \
"$((runTime - COUNT * INTERVAL * ${#pingList[@]}))" \
"${#pingList[@]}" "${#serverList[@]}"
done < <( ping -c "$COUNT" -i "$INTERVAL" -q "$myLn" | awk \
'
/^PING / {myH=$2}
/^PING / {
IP = substr($3,2,15)
split(IP,myIP,")") }
/packet loss/ {myPL=$7}
/min\/avg\/max/ {
split($4,myS,"/")
printf("%-20s %-18s %7.3f %8.3f %6s\n",
myH, myIP[1], myS[2], myS[4], myPL ) }
' )
done

echo "================================================================"
echo -e "\nMost appropriate server listed in order of best latency\n"
echo "================================================================"
printf "%-20s %-18s %7s %8s %6s\n" "VoIP Server" "IP Address" "Latency" "Jitter" "Loss"
echo "================================================================"
printf "%s\n" "${pingList[@]}" | LC_ALL=C sort -n -k 3,3 -k 5,5 -k 4,4 | \
awk '{printf("%s $%2d$\n",$0, NR)}'
echo "================================================================"
</pre>

=== Perl Script ===
Pings list of voip.ms servers round robin with optional output csv file.

# usage ping_voip.ms.pl <number of times> <seconds in between> <output.csv>
use Net::Ping;
use Time::HiRes;
use strict;

# input list
my @hosts = qw(
atlanta.voip.ms
atlanta2.voip.ms
chicago.voip.ms
chicago2.voip.ms
chicago3.voip.ms
chicago4.voip.ms
dallas.voip.ms
denver.voip.ms
denver2.voip.ms
houston.voip.ms
losangeles.voip.ms
losangeles2.voip.ms
newyork.voip.ms
newyork2.voip.ms
newyork3.voip.ms
newyork4.voip.ms
seattle.voip.ms
seattle2.voip.ms
seattle3.voip.ms
tampa.voip.ms
washington.voip.ms
washington2.voip.ms
montreal.voip.ms
montreal2.voip.ms
montreal3.voip.ms
montreal4.voip.ms
toronto2.voip.ms
toronto3.voip.ms
toronto4.voip.ms
toronto.voip.ms
london.voip.ms
);

$| = 1; #autoflush
# High precision syntax (requires Time::HiRes)
my $p = Net::Ping->new("icmp",1);
$p->hires();
my $max_name_length = (reverse sort { $a <=> $b } map { length($_) } @hosts)[0];
my $count = 4; # number of times to ping
my $interval = 5; # seconds between ping rounds
my $output_file = "";
my @data;

# check for arguments
my $num_args = @ARGV;
if ($num_args >= 1) {$count = $ARGV[0];}
if ($num_args >= 2) {$interval = $ARGV[1];}
if ($num_args >= 3) {$output_file = $ARGV[2];}

# check argument validity
$0 =~ /^.*\\(.*)$/;
my $script = $1;
if ($count !~ /^\d+$/ or $interval !~ /^\d+$/) {die "Usage: $script <number of rounds> <seconds between rounds> <output.csv>\n";}
if (length($output_file) > 0 and $output_file !~ /\.csv$/) {$output_file .= ".csv";}

# main loop
for my $i (1..$count)
{
sleep $interval unless $i == 1;
print "Round $i\n";
my $host_num=0;
foreach my $host (@hosts)
{
(my $ret, my $duration, my $ip) = $p->ping($host);
$ip =~ /(\d+)\.(\d+)\.(\d+)\.(\d+)/;
if ($ret)
{
printf("%*s [ip: %3s.%3s.%3s.%3s] is alive (%6.2f ms)\n", $max_name_length, $host, $1, $2, $3, $4, $duration*1000);
$data[$host_num][$i]=$duration*1000;
}
else
{
printf("%*s [ip: %3s.%3s.%3s.%3s] is dead\n", $max_name_length, $host, $1, $2, $3, $4);
}
$host_num++;
}
print "\n";
}
$p->close();

# if output file name given
if (length($output_file)>0)
{
# print output to file
open FILE, ">$output_file" or die "$!\n";

# print column headers
print FILE "Server\\Round";
for my $i (1..$count)
{
print FILE ", $i";
}
print FILE ", Average\n";

# print data
my $i = 0;
foreach my $host (@hosts)
{
print FILE "$host";
my $sum = 0;
for my $j (1..$count)
{
$sum += $data[$i][$j];
printf FILE ", %8.4f",$data[$i][$j];
}
printf FILE ", %8.4f\n",$sum/$count;
$i++;
}

close FILE;
print "Data written to $output_file\n";
}

# print summary to screen
my $i = 0;
printf("%-*s Average (ms)\n", $max_name_length, "Server");
foreach my $host (@hosts)
{
my $sum = 0;
for my $j (1..$count)
{
$sum += $data[$i][$j];
}
printf("%-*s %8.4f\n", $max_name_length+1, $host, $sum/$count);
$i++;
}

Output:
Round 1
atlanta.voip.ms [ip: 174. 34.146.162] is alive ( 88.97 ms)
atlanta2.voip.ms [ip: 72. 9.246.170] is alive ( 92.99 ms)
chicago.voip.ms [ip: 208.100. 39. 52] is alive ( 49.70 ms)
chicago2.voip.ms [ip: 208.100. 39. 53] is alive ( 59.76 ms)
chicago3.voip.ms [ip: 208.100. 39. 54] is alive ( 59.53 ms)
chicago4.voip.ms [ip: 208.100. 39. 55] is alive ( 49.73 ms)
dallas.voip.ms [ip: 74. 54. 54.178] is alive ( 94.99 ms)
denver.voip.ms [ip: 173.248.161. 90] is alive ( 94.05 ms)
denver2.voip.ms [ip: 173.248.159.210] is alive ( 85.13 ms)
houston.voip.ms [ip: 209. 62. 1. 2] is alive (102.87 ms)
losangeles.voip.ms [ip: 96. 44.149.186] is alive ( 64.92 ms)
losangeles2.voip.ms [ip: 96. 44.149.202] is alive ( 63.41 ms)
newyork.voip.ms [ip: 74. 63. 41.218] is alive (131.75 ms)
newyork2.voip.ms [ip: 107. 6. 67.236] is alive (120.64 ms)
newyork3.voip.ms [ip: 107. 6. 67.237] is alive (120.49 ms)
newyork4.voip.ms [ip: 107. 6. 67.238] is alive (111.43 ms)
seattle.voip.ms [ip: 50. 23.160. 50] is alive ( 94.25 ms)
seattle2.voip.ms [ip: 50. 23.160. 51] is alive ( 95.86 ms)
seattle3.voip.ms [ip: 50. 23.160. 52] is alive ( 90.85 ms)
tampa.voip.ms [ip: 68.233.226. 97] is alive (123.29 ms)
washington.voip.ms [ip: 208. 43.234.226] is alive ( 98.71 ms)
washington2.voip.ms [ip: 208. 43.234.227] is alive (101.19 ms)
montreal.voip.ms [ip: 67.205. 74.184] is alive ( 81.82 ms)
montreal2.voip.ms [ip: 67.205. 74.187] is alive ( 86.13 ms)
montreal3.voip.ms [ip: 72. 55.168. 18] is alive ( 77.09 ms)
montreal4.voip.ms [ip: 67.205. 74.179] is alive ( 96.18 ms)
toronto2.voip.ms [ip: 184. 75.215.114] is alive (103.70 ms)
toronto3.voip.ms [ip: 184. 75.215.146] is alive (131.27 ms)
toronto4.voip.ms [ip: 184. 75.213.210] is alive (125.13 ms)
toronto.voip.ms [ip: 184. 75.215.106] is alive (103.26 ms)
london.voip.ms [ip: 5. 77. 36.136] is alive (152.77 ms)

Round 2
atlanta.voip.ms [ip: 174. 34.146.162] is alive ( 88.14 ms)
atlanta2.voip.ms [ip: 72. 9.246.170] is alive ( 92.86 ms)
chicago.voip.ms [ip: 208.100. 39. 52] is alive ( 50.03 ms)
chicago2.voip.ms [ip: 208.100. 39. 53] is alive ( 59.44 ms)
chicago3.voip.ms [ip: 208.100. 39. 54] is alive ( 59.33 ms)
chicago4.voip.ms [ip: 208.100. 39. 55] is alive ( 50.22 ms)
dallas.voip.ms [ip: 74. 54. 54.178] is alive ( 95.58 ms)
denver.voip.ms [ip: 173.248.161. 90] is alive ( 95.94 ms)
denver2.voip.ms [ip: 173.248.159.210] is alive ( 85.29 ms)
houston.voip.ms [ip: 209. 62. 1. 2] is alive (102.73 ms)
losangeles.voip.ms [ip: 96. 44.149.186] is alive ( 65.59 ms)
losangeles2.voip.ms [ip: 96. 44.149.202] is alive ( 64.27 ms)
newyork.voip.ms [ip: 74. 63. 41.218] is alive (112.74 ms)
newyork2.voip.ms [ip: 107. 6. 67.236] is alive (121.22 ms)
newyork3.voip.ms [ip: 107. 6. 67.237] is alive (121.34 ms)
newyork4.voip.ms [ip: 107. 6. 67.238] is alive (110.75 ms)
seattle.voip.ms [ip: 50. 23.160. 50] is alive ( 94.06 ms)
seattle2.voip.ms [ip: 50. 23.160. 51] is alive ( 95.33 ms)
seattle3.voip.ms [ip: 50. 23.160. 52] is alive ( 91.58 ms)
tampa.voip.ms [ip: 68.233.226. 97] is alive (122.94 ms)
washington.voip.ms [ip: 208. 43.234.226] is alive ( 98.28 ms)
washington2.voip.ms [ip: 208. 43.234.227] is alive (101.40 ms)
montreal.voip.ms [ip: 67.205. 74.184] is alive ( 81.91 ms)
montreal2.voip.ms [ip: 67.205. 74.187] is alive ( 85.64 ms)
montreal3.voip.ms [ip: 72. 55.168. 18] is alive ( 75.15 ms)
montreal4.voip.ms [ip: 67.205. 74.179] is alive ( 96.79 ms)
toronto2.voip.ms [ip: 184. 75.215.114] is alive (103.10 ms)
toronto3.voip.ms [ip: 184. 75.215.146] is alive (150.85 ms)
toronto4.voip.ms [ip: 184. 75.213.210] is alive (138.40 ms)
toronto.voip.ms [ip: 184. 75.215.106] is alive (103.45 ms)
london.voip.ms [ip: 5. 77. 36.136] is alive (170.79 ms)

Round 3
atlanta.voip.ms [ip: 174. 34.146.162] is alive ( 88.76 ms)
atlanta2.voip.ms [ip: 72. 9.246.170] is alive ( 92.86 ms)
chicago.voip.ms [ip: 208.100. 39. 52] is alive ( 49.65 ms)
chicago2.voip.ms [ip: 208.100. 39. 53] is alive ( 60.01 ms)
chicago3.voip.ms [ip: 208.100. 39. 54] is alive ( 59.05 ms)
chicago4.voip.ms [ip: 208.100. 39. 55] is alive ( 49.53 ms)
dallas.voip.ms [ip: 74. 54. 54.178] is alive ( 95.82 ms)
denver.voip.ms [ip: 173.248.161. 90] is alive ( 95.02 ms)
denver2.voip.ms [ip: 173.248.159.210] is alive ( 85.60 ms)
houston.voip.ms [ip: 209. 62. 1. 2] is alive (103.35 ms)
losangeles.voip.ms [ip: 96. 44.149.186] is alive ( 65.79 ms)
losangeles2.voip.ms [ip: 96. 44.149.202] is alive ( 64.05 ms)
newyork.voip.ms [ip: 74. 63. 41.218] is alive (113.01 ms)
newyork2.voip.ms [ip: 107. 6. 67.236] is alive (121.41 ms)
newyork3.voip.ms [ip: 107. 6. 67.237] is alive (122.23 ms)
newyork4.voip.ms [ip: 107. 6. 67.238] is alive (110.62 ms)
seattle.voip.ms [ip: 50. 23.160. 50] is alive ( 93.65 ms)
seattle2.voip.ms [ip: 50. 23.160. 51] is alive ( 95.19 ms)
seattle3.voip.ms [ip: 50. 23.160. 52] is alive ( 90.75 ms)
tampa.voip.ms [ip: 68.233.226. 97] is alive (125.12 ms)
washington.voip.ms [ip: 208. 43.234.226] is alive ( 98.19 ms)
washington2.voip.ms [ip: 208. 43.234.227] is alive (101.98 ms)
montreal.voip.ms [ip: 67.205. 74.184] is alive ( 80.16 ms)
montreal2.voip.ms [ip: 67.205. 74.187] is alive ( 87.16 ms)
montreal3.voip.ms [ip: 72. 55.168. 18] is alive ( 76.54 ms)
montreal4.voip.ms [ip: 67.205. 74.179] is alive ( 97.51 ms)
toronto2.voip.ms [ip: 184. 75.215.114] is alive (104.18 ms)
toronto3.voip.ms [ip: 184. 75.215.146] is alive (142.81 ms)
toronto4.voip.ms [ip: 184. 75.213.210] is alive (138.95 ms)
toronto.voip.ms [ip: 184. 75.215.106] is alive (103.78 ms)
london.voip.ms [ip: 5. 77. 36.136] is alive (153.14 ms)

Round 4
atlanta.voip.ms [ip: 174. 34.146.162] is alive ( 89.19 ms)
atlanta2.voip.ms [ip: 72. 9.246.170] is alive ( 92.98 ms)
chicago.voip.ms [ip: 208.100. 39. 52] is alive ( 49.21 ms)
chicago2.voip.ms [ip: 208.100. 39. 53] is alive ( 60.50 ms)
chicago3.voip.ms [ip: 208.100. 39. 54] is alive ( 59.68 ms)
chicago4.voip.ms [ip: 208.100. 39. 55] is alive ( 50.18 ms)
dallas.voip.ms [ip: 74. 54. 54.178] is alive ( 93.93 ms)
denver.voip.ms [ip: 173.248.161. 90] is alive ( 94.22 ms)
denver2.voip.ms [ip: 173.248.159.210] is alive ( 85.10 ms)
houston.voip.ms [ip: 209. 62. 1. 2] is alive (103.67 ms)
losangeles.voip.ms [ip: 96. 44.149.186] is alive ( 65.58 ms)
losangeles2.voip.ms [ip: 96. 44.149.202] is alive ( 63.60 ms)
newyork.voip.ms [ip: 74. 63. 41.218] is alive (114.76 ms)
newyork2.voip.ms [ip: 107. 6. 67.236] is alive (120.44 ms)
newyork3.voip.ms [ip: 107. 6. 67.237] is alive (121.05 ms)
newyork4.voip.ms [ip: 107. 6. 67.238] is alive (110.51 ms)
seattle.voip.ms [ip: 50. 23.160. 50] is alive ( 94.04 ms)
seattle2.voip.ms [ip: 50. 23.160. 51] is alive ( 96.92 ms)
seattle3.voip.ms [ip: 50. 23.160. 52] is alive ( 91.23 ms)
tampa.voip.ms [ip: 68.233.226. 97] is alive (123.28 ms)
washington.voip.ms [ip: 208. 43.234.226] is alive ( 98.45 ms)
washington2.voip.ms [ip: 208. 43.234.227] is alive (100.94 ms)
montreal.voip.ms [ip: 67.205. 74.184] is alive ( 82.33 ms)
montreal2.voip.ms [ip: 67.205. 74.187] is alive ( 85.02 ms)
montreal3.voip.ms [ip: 72. 55.168. 18] is alive ( 76.85 ms)
montreal4.voip.ms [ip: 67.205. 74.179] is alive ( 96.32 ms)
toronto2.voip.ms [ip: 184. 75.215.114] is alive (104.22 ms)
toronto3.voip.ms [ip: 184. 75.215.146] is alive (148.33 ms)
toronto4.voip.ms [ip: 184. 75.213.210] is alive (141.61 ms)
toronto.voip.ms [ip: 184. 75.215.106] is alive (105.91 ms)
london.voip.ms [ip: 5. 77. 36.136] is alive (152.85 ms)

Server Average (ms)
atlanta.voip.ms 88.7630
atlanta2.voip.ms 92.9233
chicago.voip.ms 49.6477
chicago2.voip.ms 59.9305
chicago3.voip.ms 59.3972
chicago4.voip.ms 49.9152
dallas.voip.ms 95.0790
denver.voip.ms 94.8077
denver2.voip.ms 85.2797
houston.voip.ms 103.1562
losangeles.voip.ms 65.4693
losangeles2.voip.ms 63.8347
newyork.voip.ms 118.0643
newyork2.voip.ms 120.9265
newyork3.voip.ms 121.2778
newyork4.voip.ms 110.8275
seattle.voip.ms 93.9993
seattle2.voip.ms 95.8267
seattle3.voip.ms 91.1035
tampa.voip.ms 123.6570
washington.voip.ms 98.4065
washington2.voip.ms 101.3774
montreal.voip.ms 81.5525
montreal2.voip.ms 85.9863
montreal3.voip.ms 76.4058
montreal4.voip.ms 96.7013
toronto2.voip.ms 103.7986
toronto3.voip.ms 143.3156
toronto4.voip.ms 136.0254
toronto.voip.ms 104.1012
london.voip.ms 157.3885

=== Powershell ===

Dec 2017 - A bug in the code shown washington2.voip.ms as the best server, this was corrected.

<pre>
# Usage: Copy and paste the following code into a powershell window
# To run it from a command prompt, save this file with extension ps1.
# Then run Powershell.exe -file "pathtothisscript.ps1"
Clear-Variable best* -Scope Global #Clear the best* variables in case you run it more than once...
#Get the list of servers into an array
$Servers =
@("amsterdam.voip.ms","atlanta.voip.ms","atlanta2.voip.ms","chicago.voip.ms","chicago2.voip.ms","chicago3.voip.ms",
"chicago4.voip.ms","dallas.voip.ms","dallas2.voip.ms","denver.voip.ms","denver2.voip.ms","houston.voip.ms",
"houston2.voip.ms","london.voip.ms","losangeles.voip.ms","losangeles2.voip.ms","melbourne.voip.ms","montreal.voip.ms",
"montreal2.voip.ms","montreal3.voip.ms","montreal4.voip.ms","montreal5.voip.ms","montreal6.voip.ms","montreal7.voip.ms",
"montreal8.voip.ms","newyork.voip.ms","newyork2.voip.ms","newyork3.voip.ms","newyork4.voip.ms","newyork5.voip.ms",
"newyork6.voip.ms","newyork7.voip.ms","newyork8.voip.ms","paris.voip.ms","sanjose.voip.ms","sanjose2.voip.ms",
"seattle.voip.ms","seattle2.voip.ms","seattle3.voip.ms","tampa.voip.ms","tampa2.voip.ms","toronto.voip.ms",
"toronto2.voip.ms","toronto3.voip.ms","toronto4.voip.ms","toronto5.voip.ms","toronto6.voip.ms","toronto7.voip.ms",
"toronto8.voip.ms","vancouver.voip.ms","vancouver2.voip.ms","washington.voip.ms","washington2.voip.ms")
$k = 0 #Counting variable so we know what server number we are testing
#num of servers to test
$servercount = $servers.length
#Do the following code for each server in our array
ForEach($server in $servers)
{
#Add one to the counting variable....we are on server #1...then server 2, then server 3 etc...
$k++
#Update the progress bar
Write-Progress -Activity "Testing Server: ${server}" -status "Testing Server $k out of $servercount" -percentComplete ($k / $servercount*100)
#Counting variable for number of times we tried to ping a given server
$i = 0
Do{
#assume a failure
$pingsuccess = $false
$i++ #Add one to the counting variable.....1st try....2nd try....3rd try etc...
Try{
#Try to ping
$currentping = (test-connection $server -count 1 -ErrorAction Stop).responsetime
#If success full, set success variable
$pingsuccess = $true
}
#Catch the failure and set the success variable to false
Catch {
$pingsuccess = $false
}
}
#Try everything between Do and While up to 5 times, or while $pingsuccess is not true
While($pingsuccess -eq $false -and $i -le 5)
#Compare the last ping test with the best known ping test....if there is no known best ping test, assume this one is the best $bestping = $currentping
If($pingsuccess -and ($currentping -lt $bestping -or (!($bestping)))){
#If this is the best ping...save it
$bestserver = $server #Save the best server
$bestping = $currentping #Save the best ping results
}
write-host "tested: $server at $currentping ms after $i attempts" #write the results of the test for this server
}
write-host "`r`n The server with the best ping is: $bestserver at $bestping ms`r`n" #write the end result
Pause
</pre>

=== Linux Shell Script ===
Pings several voip.ms servers

#!/bin/sh
# Ping several servers and display Latency, Jitter and Packet Loss
#
# First, create a text file with all servers you want to ping - one host name per line.
# The list of voip.ms servers is available at http://wiki.voip.ms/article/Choosing_Server
myHF="voip_ping_hosts.txt"
# Sample file:
# toronto.voip.ms
# montreal.voip.ms
# seattle.voip.ms
# chicago.voip.ms
# newyork.voip.ms
#
echo "============================================"
printf "%-20s %7s %8s %6s\n" "VoIP Server" "Latency" "Jitter" "Loss"
echo "============================================"
cat ${myHF} |\
while read myLn
do
ping -c 3 -i 5 -q $myLn |\
awk '/^PING / {myH=$2}
/packet loss/ {myPL=$6}
/min\/avg\/max/ {
split($4,myS,"/")
printf( "%-20s %3.1f %1.3f %4s\n", myH, myS[2], myS[4], myPL)
}'
done
echo "============================================"

Output:

============================================
VoIP Server Latency Jitter Loss
============================================
toronto.voip.ms 68.3 0.439 0%
montreal.voip.ms 89.6 0.197 0%
seattle.voip.ms 71.2 0.387 0%
chicago.voip.ms 71.6 0.084 0%
newyork.voip.ms 79.1 0.411 0%
============================================

= Latency and its importance =

Latency is very important for Voip, this will determine the time that will take for the data package transmission to reach the destination. A high latency will lead to a delay and echoes in the communication.

Latency is measured in milliseconds (ms) For example: a latency of 150ms is barely noticeable, thus acceptable. Higher than that, quality starts to suffer. When it gets higher than 300 ms, it becomes unacceptable.

[[category:guides]]

Servers

2020-08-03T20:38:07Z

B13n:

<div style="text-align:center; font-family:Arial; font-size:200%">
This page only shows the [http://www.voip.ms VoIP.ms] servers name, domain, and IP. For further information about how to properly select the best option for you, please refer to our wiki entry "[[Choosing Server]]"
</div>

== Canada ==

{| class="wikitable" style="border: none; width: 60%; height: 200px; text-align: justify;"
! colspan="3" | Canada Servers
|-
! scope="col" | Server's name
! scope="col" | Server's domain
! scope="col" | Server's IP
|-
|Montreal 1, QC || '''montreal.voip.ms''' || 67.205.74.184
|-
|Montreal 2, QC || '''montreal2.voip.ms''' || 67.205.74.187
|-
|Montreal 3, QC || '''montreal3.voip.ms''' || 192.175.96.68
|-
|Montreal 4, QC || '''montreal4.voip.ms''' || 67.205.74.179
|-
|Montreal 5, QC || '''montreal5.voip.ms''' || 192.175.96.69
|-
|Montreal 6, QC || '''montreal6.voip.ms''' || 192.175.96.70
|-
|Montreal 7, QC || '''montreal7.voip.ms''' || 192.175.96.71
|-
|Montreal 8, QC || '''montreal8.voip.ms''' || 192.175.96.72
|-
|Montreal 9, QC || '''montreal9.voip.ms''' || 67.205.74.184
|-
|Montreal 10, QC || '''montreal10.voip.ms''' || 67.205.74.187
|-
|Toronto 1, ON || '''toronto.voip.ms''' || 158.85.70.148
|-
|Toronto 2, ON || '''toronto2.voip.ms''' || 158.85.70.149
|-
|Toronto 3, ON || '''toronto3.voip.ms''' || 158.85.70.150
|-
|Toronto 4, ON || '''toronto4.voip.ms''' || 158.85.70.151
|-
|Toronto 5, ON || '''toronto5.voip.ms''' || 184.75.215.106
|-
|Toronto 6, ON || '''toronto6.voip.ms''' || 184.75.215.114
|-
|Toronto 7, ON || '''toronto7.voip.ms''' || 184.75.215.146
|-
|Toronto 8, ON || '''toronto8.voip.ms''' || 184.75.213.210
|-
|Toronto 9, ON || '''toronto9.voip.ms''' || 158.85.70.154
|-
|Toronto 10, ON || '''toronto10.voip.ms''' || 158.85.70.158
|-
|Vancouver 1, BC || '''vancouver.voip.ms''' || 162.213.157.220
|-
|Vancouver 2, BC || '''vancouver2.voip.ms''' || 162.213.157.117
|-
|Vancouver 3, BC || '''vancouver3.voip.ms''' || 162.213.157.82
|}

== USA ==

{| class="wikitable" style="border: none; width: 60%; height: 200px; text-align: justify;"
! colspan="3" | USA Servers
|-
! scope="col" | Server's name
! scope="col" | Server's domain
! scope="col" | Server's IP
|-
| Atlanta 1, GA || '''atlanta.voip.ms'''|| 75.127.65.130
|-
| Atlanta 2, GA || '''atlanta2.voip.ms'''|| 72.9.246.170
|-
| Chicago 1, IL || '''chicago.voip.ms'''|| 208.100.39.52
|-
| Chicago 2, IL || '''chicago2.voip.ms'''|| 208.100.39.53
|-
| Chicago 3, IL || '''chicago3.voip.ms'''|| 208.100.39.54
|-
| Chicago 4, IL || '''chicago4.voip.ms'''|| 208.100.39.55
|-
| Chicago 5, IL || '''chicago5.voip.ms'''|| 50.31.115.149
|-
| Chicago 6, IL || '''chicago6.voip.ms'''|| 50.31.115.150
|-
| Chicago 7, IL || '''chicago7.voip.ms'''|| 50.31.115.151
|-
| Dallas, TX || '''dallas.voip.ms'''|| 158.85.149.162
|-
| Dallas 2, TX || '''dallas2.voip.ms'''|| 158.85.149.163
|-
| Denver 1, CO || '''denver.voip.ms'''|| 23.239.211.90
|-
| Denver 2, CO || '''denver2.voip.ms'''|| 64.27.52.226
|-
| Houston, TX || '''houston.voip.ms'''|| 173.193.85.18
|-
| Houston 2, TX || '''houston2.voip.ms'''|| 173.193.85.19
|-
| Los Angeles 1, CA || '''losangeles.voip.ms'''|| 96.44.149.186
|-
| Los Angeles 2, CA || '''losangeles2.voip.ms'''|| 96.44.149.202
|-
| Los Angeles 3, CA || '''losangeles3.voip.ms'''|| 64.188.6.162
|-
| Los Angeles 4, CA || '''losangeles4.voip.ms'''|| 64.188.6.170
|-
| New York 1, NY || '''newyork.voip.ms'''|| 72.251.239.196
|-
| New York 2, NY || '''newyork2.voip.ms'''|| 72.251.239.205
|-
| New York 3, NY || '''newyork3.voip.ms'''|| 72.251.239.206
|-
| New York 4, NY || '''newyork4.voip.ms'''|| 72.251.239.207
|-
| New York 5, NY || '''newyork5.voip.ms'''|| 23.29.136.28
|-
| New York 6, NY || '''newyork6.voip.ms'''|| 23.29.136.29
|-
| New York 7, NY || '''newyork7.voip.ms'''|| 23.29.136.38
|-
| New York 8, NY || '''newyork8.voip.ms'''|| 23.29.136.40
|-
| San Jose, CA || '''sanjose.voip.ms'''|| 23.246.247.146
|-
| San Jose 2, CA || '''sanjose2.voip.ms'''|| 23.246.247.147
|-
| Seattle 1, WA || '''seattle.voip.ms'''|| 50.23.160.53
|-
| Seattle 2, WA || '''seattle2.voip.ms'''|| 50.23.149.166
|-
| Seattle 3, WA || '''seattle3.voip.ms'''|| 50.23.160.54
|-
| Tampa, FL || '''tampa.voip.ms'''|| 162.254.144.173
|-
| Tampa 2, FL || '''tampa2.voip.ms'''|| 162.254.144.176
|-
| Tampa 3, FL || '''tampa3.voip.ms'''|| 23.111.187.139
|-
| Tampa 4, FL || '''tampa4.voip.ms'''|| 23.111.166.202
|-
| Washington 1, DC || '''washington.voip.ms'''|| 208.43.234.226
|-
| Washington 2, DC || '''washington2.voip.ms'''|| 208.43.234.227
|}

== International ==

{| class="wikitable" style="border: none; width: 60%; height: 200px; text-align: justify;"
! colspan="3" | International Servers
|-
! scope="col" | Server's name
! scope="col" | Server's domain
! scope="col" | Server's IP
|-
|Amsterdam, NL || '''amsterdam.voip.ms''' || 37.58.88.242
|-
|London, UK || '''london.voip.ms''' || 159.8.157.212
|-
|Melbourne, AU || '''melbourne.voip.ms''' || 168.1.73.84
|-
|Paris, FR || '''paris.voip.ms''' || 159.8.85.180
|}

Servers

2020-08-03T20:34:59Z

B13n: Added missing CAN & USA servers

<div style="text-align:center; font-family:Arial; font-size:200%">
This page only shows the [http://www.voip.ms VoIP.ms] servers name, domain, and IP. For further information about how to properly select the best option for you, please refer to our wiki entry "[[Choosing Server]]"
</div>

== Canada ==

{| class="wikitable" style="border: none; width: 60%; height: 200px; text-align: justify;"
! colspan="3" | Canada Servers
|-
! scope="col" | Server's name
! scope="col" | Server's domain
! scope="col" | Server's IP
|-
|Montreal 1, QC || '''montreal.voip.ms''' || 67.205.74.184
|-
|Montreal 2, QC || '''montreal2.voip.ms''' || 67.205.74.187
|-
|Montreal 3, QC || '''montreal3.voip.ms''' || 192.175.96.68
|-
|Montreal 4, QC || '''montreal4.voip.ms''' || 67.205.74.179
|-
|Montreal 5, QC || '''montreal5.voip.ms''' || 192.175.96.69
|-
|Montreal 6, QC || '''montreal6.voip.ms''' || 192.175.96.70
|-
|Montreal 7, QC || '''montreal7.voip.ms''' || 192.175.96.71
|-
|Montreal 8, QC || '''montreal8.voip.ms''' || 192.175.96.72
|-
|Montreal 9, QC || '''montreal9.voip.ms''' || 67.205.74.184
|-
|Montreal 10, QC || '''montreal10.voip.ms''' || 67.205.74.187
|-
|Toronto 1, ON || '''toronto.voip.ms''' || 158.85.70.148
|-
|Toronto 2, ON || '''toronto2.voip.ms''' || 158.85.70.149
|-
|Toronto 3, ON || '''toronto3.voip.ms''' || 158.85.70.150
|-
|Toronto 4, ON || '''toronto4.voip.ms''' || 158.85.70.151
|-
|Toronto 5, ON || '''toronto5.voip.ms''' || 184.75.215.106
|-
|Toronto 6, ON || '''toronto6.voip.ms''' || 184.75.215.114
|-
|Toronto 7, ON || '''toronto7.voip.ms''' || 184.75.215.146
|-
|Toronto 8, ON || '''toronto8.voip.ms''' || 184.75.213.210
|-
|Toronto 9, ON || '''toronto9.voip.ms''' || 158.85.70.154
|-
|Toronto 10, ON || '''toronto10.voip.ms''' || 158.85.70.158
|-
|Vancouver 1, BC || '''vancouver.voip.ms''' || 162.213.157.82
|-
|Vancouver 2, BC || '''vancouver2.voip.ms''' || 162.213.157.117
|-
|Vancouver 3, BC || '''vancouver3.voip.ms''' || 162.213.157.82
|}

== USA ==

{| class="wikitable" style="border: none; width: 60%; height: 200px; text-align: justify;"
! colspan="3" | USA Servers
|-
! scope="col" | Server's name
! scope="col" | Server's domain
! scope="col" | Server's IP
|-
| Atlanta 1, GA || '''atlanta.voip.ms'''|| 75.127.65.130
|-
| Atlanta 2, GA || '''atlanta2.voip.ms'''|| 72.9.246.170
|-
| Chicago 1, IL || '''chicago.voip.ms'''|| 208.100.39.52
|-
| Chicago 2, IL || '''chicago2.voip.ms'''|| 208.100.39.53
|-
| Chicago 3, IL || '''chicago3.voip.ms'''|| 208.100.39.54
|-
| Chicago 4, IL || '''chicago4.voip.ms'''|| 208.100.39.55
|-
| Chicago 5, IL || '''chicago5.voip.ms'''|| 50.31.115.149
|-
| Chicago 6, IL || '''chicago6.voip.ms'''|| 50.31.115.150
|-
| Chicago 7, IL || '''chicago7.voip.ms'''|| 50.31.115.151
|-
| Dallas, TX || '''dallas.voip.ms'''|| 158.85.149.162
|-
| Dallas 2, TX || '''dallas2.voip.ms'''|| 158.85.149.163
|-
| Denver 1, CO || '''denver.voip.ms'''|| 23.239.211.90
|-
| Denver 2, CO || '''denver2.voip.ms'''|| 64.27.52.226
|-
| Houston, TX || '''houston.voip.ms'''|| 173.193.85.18
|-
| Houston 2, TX || '''houston2.voip.ms'''|| 173.193.85.19
|-
| Los Angeles 1, CA || '''losangeles.voip.ms'''|| 96.44.149.186
|-
| Los Angeles 2, CA || '''losangeles2.voip.ms'''|| 96.44.149.202
|-
| Los Angeles 3, CA || '''losangeles3.voip.ms'''|| 64.188.6.162
|-
| Los Angeles 4, CA || '''losangeles4.voip.ms'''|| 64.188.6.170
|-
| New York 1, NY || '''newyork.voip.ms'''|| 72.251.239.196
|-
| New York 2, NY || '''newyork2.voip.ms'''|| 72.251.239.205
|-
| New York 3, NY || '''newyork3.voip.ms'''|| 72.251.239.206
|-
| New York 4, NY || '''newyork4.voip.ms'''|| 72.251.239.207
|-
| New York 5, NY || '''newyork5.voip.ms'''|| 23.29.136.28
|-
| New York 6, NY || '''newyork6.voip.ms'''|| 23.29.136.29
|-
| New York 7, NY || '''newyork7.voip.ms'''|| 23.29.136.38
|-
| New York 8, NY || '''newyork8.voip.ms'''|| 23.29.136.40
|-
| San Jose, CA || '''sanjose.voip.ms'''|| 23.246.247.146
|-
| San Jose 2, CA || '''sanjose2.voip.ms'''|| 23.246.247.147
|-
| Seattle 1, WA || '''seattle.voip.ms'''|| 50.23.160.53
|-
| Seattle 2, WA || '''seattle2.voip.ms'''|| 50.23.149.166
|-
| Seattle 3, WA || '''seattle3.voip.ms'''|| 50.23.160.54
|-
| Tampa, FL || '''tampa.voip.ms'''|| 162.254.144.173
|-
| Tampa 2, FL || '''tampa2.voip.ms'''|| 162.254.144.176
|-
| Tampa 3, FL || '''tampa3.voip.ms'''|| 23.111.187.139
|-
| Tampa 4, FL || '''tampa4.voip.ms'''|| 23.111.166.202
|-
| Washington 1, DC || '''washington.voip.ms'''|| 208.43.234.226
|-
| Washington 2, DC || '''washington2.voip.ms'''|| 208.43.234.227
|}

== International ==

{| class="wikitable" style="border: none; width: 60%; height: 200px; text-align: justify;"
! colspan="3" | International Servers
|-
! scope="col" | Server's name
! scope="col" | Server's domain
! scope="col" | Server's IP
|-
|Amsterdam, NL || '''amsterdam.voip.ms''' || 37.58.88.242
|-
|London, UK || '''london.voip.ms''' || 159.8.157.212
|-
|Melbourne, AU || '''melbourne.voip.ms''' || 168.1.73.84
|-
|Paris, FR || '''paris.voip.ms''' || 159.8.85.180
|}

SNOM D785

2019-08-09T14:54:24Z

B13n:

[[File:D785 device.png|150px|thumb|left]]
<br clear="all" />

The [https://www.snom.com/ip-phones/desk-phones/d7xx-series/d785/ Snom D785] belongs to the latest generation of advanced Snom IP phones. Elegantly designed (Black and white) and featuring a large high-resolution colour display and a convenient second screen for dynamic contact management as well as integrated Bluetooth, this IP phone has all the functions necessary to fulfil even the most demanding requirements.

The Snom D785 is the perfect combination of advanced technology and elegant design and sets new standards with its intuitive user interface. Due to its high-resolution colour display and practical second screen, the D785 marks another milestone in the twenty-year history of the VoIP phone pioneer, Snom.

<br clear="all" />

__TOC__

=='''Accessing The Web Interface'''==

In order to configure the '''SNOM D785''' to be used along our service it is required to access it's web interface settings. For this, the IP address of the device must be acquired.

To perform this click on the "'''''Settings'''''" button of the phone. Once on the settings menu, scroll down to: " '''''Information''''' " , then select: " '''''System info''''' ". On this section, you'll need to take note of the IP address shown beside: " '''''IP Adr''''' ". It should read back something as: " '''''192.168.0.1''''' ".

Once you have the IP address please open a web browser of your preference and it's URL bar enter the IP address you got by prepending: " '''''http://''''' " and access it. Once accessed, you'll be prompted to authenticate. The default administrator password is: " '''''0000''''' ".

=='''Identity Settings'''==

Once logged in you'll be presented with this screen:

[[File:MAIN_SNOM_D785_v2.png|thumb|none|600px]]

Here, please navigate to: ''Identity 1''. Once on this page, please fill these fields as follows:

===Login Information===

:*'''''Displayname''''': The name you wish to pass when calling out
:*'''''Account''''': 100000 (replace with your SIP main account or subaccount)
:*'''''Password''''': Your SIP account's password
:*'''''Registrar''''': One of VoIP.ms multiple ''[[Choosing Server | SERVERS]]'', you can choose the one closest to your location
:*'''''Outbound Proxy''''': The same server used above for registrar server
:*'''''Authentication Username''''': 100000 (replace with your SIP main account or subaccount)
:*'''''Mailbox''''': *97 (The feature: "BLF Directed Call Pickup" has to be left blank on the "Features" tab for this to work)

[[File:LOGIN_SNOM_D785.png|thumb|none|600px]]

Once done press the: "'''''Apply'''''" button at the bottom. Then, head to the: " '''''SIP''''' " tab. Here, fill these fields as follows:

===SIP Identity Settings===

:*'''''Dial-Plan String''''': ^.$
:*'''''Proposed Expiry''''': 300
:*'''''Subscription Expiry''''': 300
:*'''''Failed Subscription Retry Time''''': 300

[[File:SIP_SNOM_D785.png|thumb|none|600px]]

Once done press the: " '''''Apply''''' " button at the bottom. Then, head to the: " '''''RTP''''' " tab.

===RTP Identity Settings===

Here, leave only the following text on the " '''''Codec''''' " section:

pcmu,gsm,g729,telephone-event

[[File:RTP_SNOM_D785.png|thumb|none|600px]]

Finally, press the: "'''''Apply'''''" button on the bottom and then the: "'''''Save'''''" button at the top. If you're prompted to reboot the phone please do so. When all these steps are taken & fulfilled the device will be ready for use.

[[File:D735_Save.png|thumb|none|600px]]

If you experience any issues or find anything you'd like to contribute with please don't hesitate to contact us.

[[category:SIP phones]]

SNOM D785

2019-08-09T14:53:58Z

B13n:

[[File:D785 device.png|150px|thumb|left]]
<br clear="all" />

The [https://www.snom.com/ip-phones/desk-phones/d7xx-series/d785/ Snom D785] belongs to the latest generation of advanced Snom IP phones. Elegantly designed (Black and white) and featuring a large high-resolution colour display and a convenient second screen for dynamic contact management as well as integrated Bluetooth, this IP phone has all the functions necessary to fulfil even the most demanding requirements.

The Snom D785 is the perfect combination of advanced technology and elegant design and sets new standards with its intuitive user interface. Due to its high-resolution colour display and practical second screen, the D785 marks another milestone in the twenty-year history of the VoIP phone pioneer, Snom.

<br clear="all" />

__TOC__

=='''Accessing The Web Interface'''==

In order to configure the '''SNOM D785''' to be used along our service it is required to access it's web interface settings. For this, the IP address of the device must be acquired.

To perform this click on the "'''''Settings'''''" button of the phone. Once on the settings menu, scroll down to: " '''''Information''''' " , then select: " '''''System info''''' ". On this section, you'll need to take note of the IP address shown beside: " '''''IP Adr''''' ". It should read back something as: " '''''192.168.0.1''''' ".

Once you have the IP address please open a web browser of your preference and it's URL bar enter the IP address you got by prepending: " '''''http://''''' " and access it. Once accessed, you'll be prompted to authenticate. The default administrator password is: " '''''0000''''' ".

=='''Identity Settings'''==

Once logged in you'll be presented with this screen:

[[File:MAIN_SNOM_D785_v2.png|thumb|none|600px]]

Here, please navigate to: ''Identity 1''. Once on this page, please fill these fields as follows:

===Login Information===

:*'''''Displayname''''': The name you wish to pass when calling out
:*'''''Account''''': 100000 (replace with your SIP main account or subaccount)
:*'''''Password''''': Your SIP account's password
:*'''''Registrar''''': One of VoIP.ms multiple ''[[Choosing Server | servers]]'', you can choose the one closest to your location
:*'''''Outbound Proxy''''': The same server used above for registrar server
:*'''''Authentication Username''''': 100000 (replace with your SIP main account or subaccount)
:*'''''Mailbox''''': *97 (The feature: "BLF Directed Call Pickup" has to be left blank on the "Features" tab for this to work)

[[File:LOGIN_SNOM_D785.png|thumb|none|600px]]

Once done press the: "'''''Apply'''''" button at the bottom. Then, head to the: " '''''SIP''''' " tab. Here, fill these fields as follows:

===SIP Identity Settings===

:*'''''Dial-Plan String''''': ^.$
:*'''''Proposed Expiry''''': 300
:*'''''Subscription Expiry''''': 300
:*'''''Failed Subscription Retry Time''''': 300

[[File:SIP_SNOM_D785.png|thumb|none|600px]]

Once done press the: " '''''Apply''''' " button at the bottom. Then, head to the: " '''''RTP''''' " tab.

===RTP Identity Settings===

Here, leave only the following text on the " '''''Codec''''' " section:

pcmu,gsm,g729,telephone-event

[[File:RTP_SNOM_D785.png|thumb|none|600px]]

Finally, press the: "'''''Apply'''''" button on the bottom and then the: "'''''Save'''''" button at the top. If you're prompted to reboot the phone please do so. When all these steps are taken & fulfilled the device will be ready for use.

[[File:D735_Save.png|thumb|none|600px]]

If you experience any issues or find anything you'd like to contribute with please don't hesitate to contact us.

[[category:SIP phones]]

Virtual Fax

2019-07-19T16:14:51Z

B13n:

[[File:Faxhomelogo.png|center]]

The Virtual Fax feature is used to send and receive Faxes (facsimile) with the VoIP.ms service using a DID number specifically dedicated to Fax. You may obtain such a number from your Customer Portal in the Fax Numbers section under the ''Order DID(s)'' of the ''DID Numbers'' menu.
Regular voice DID numbers are not compatible with the Virtual Fax feature.

__TOC__

== Important information about the Virtual Fax Service ==

* '''The Virtual Fax Service is only available for U.S. and Canadian DID Numbers specifically acquired from the Fax Numbers ''Order DID'' section'''
* '''It is also possible to port your VoIP.ms Voice DID Numbers and Numbers from other providers into our Virtual Fax service. For numbers from other providers, you can find this option under the ''DID Portability'' section of the Customer Portal. For VoIP.ms numbers, you can request an internal port by sending an email to our LNP department at ports@voip.ms. The porting fee is $15 per number for both options.'''
* '''The Service can currently only be used to send Faxes to Canadian and U.S. numbers. We also cannot guarantee that international will be properly received.'''
* '''Virtual Fax DID Numbers cannot receive regular voice calls nor SMS, but only faxes.'''

== Costs and Rates ==

Setup Fee: $0.00 (Currently Free)

Monthly Fee: $1.99

Per Minute Fee: $0.0290 (2.9 Cents)

[[Calls Cost|Billing Increment]] : 6 seconds

If you want to calculate how much this service could cost per page faxed, converted into per minute charges, you'll realize that this depends a lot on the destination fax speed and the content faxed (how much content is on the page compared to the blank space). Unfortunately, there are no definite ways to calculate precisely these costs . If you are sending just text, a page can take from 30s to 1 min. If you are faxing multiple pages documents, this will go faster because you don't have to handshake or negotiate with the far side's fax machine for each page. This can result in 1.5 cents to 3 cents on a 1-2 page fax. Since we also increase the charge to every 6 seconds, you are saving even more money since we do not charge you a full min for partial minute usages. You can usually get around 1-2 pages faxed per minute at 2.9 cents and $2 a month which is much less than most other Electronic Fax services currently available from other providers.

== Current Limitations ==

*Each DID Number can only send 100 messages per day. This limit can be raised upon request and verification.

*The files sent per message cannot exceed 25 MB

*The file cannot contain more than 200 pages

*Only one document per fax message can be sent

== Virtual Fax DID Number ==

Virtual Fax works specifically with Fax Numbers only acquired from the VoIP.ms Customer Portal or numbers ported in as Fax enabled. There are '''local US and Canadian numbers''' available for order. You can order a Fax DID Number from your portal >> DID Numbers >> Order DID >> Fax Numbers. You can select the desired region and a random number from the chosen area code will be assigned to you.

[[File:FaxorderDID2.jpg|700px|]]

You can also port in a number you currently own with another provider. This process can be started from the Customer Portal at DID Numbers >> DID Portability >> Porting Fax Numbers

[[File:FaxPortability.png|700px]]

== Send a Fax ==

To start using the service you will need to head to your Customer Portal >> DID Numbers >> Virtual Fax. From the Home Page you can select ‘Send Fax’. There you will see:
*Fax Number or Contact Name: This is where you will put the destination number. You can start typing a name or a number from your Phone book and it will become available.
*From Name: Here you will put the name to send in the Fax header.
*From Number: Select the Fax DID number from which you will send your Fax.
*File: Choose a file to send as a Fax. The file must be in pdf, txt, jpg, gif, png or tiff
-'''IMPORTANT: The maximum file size is 25 MB'''
*Station ID: This will be the station ID you set for the header of the Fax message. It could be a specified post if your location has several stations, such as Reception, Main Office, Accounting PC, etc.
*Send Email: If selected, an email will be sent to the specified address to confirm the Fax has been sent successfully or to advise of a failed attempt.

[[File:SendFax.png|900px]]

== My Faxes ==
In this section of the Virtual Fax menu you will be able to view your Inbound and Outbound Faxes. You may select a date range and choose the folder you would like to view. Click 'Get My Faxes' to view your selection. You can view the Status of each Fax and select from several actions. You can select to View the Fax directly, download the Fax, email the Fax to an address of your choice or alter the location of the Fax by moving it to another folder.

Only the Status gets updated automatically. You will have to refresh the page to get the costs after a fax has been completed.

[[File:MyFaxes.png|900px]]

== My Folders ==

In the 'My Folders' section, you can create folders by typing in the folder name of your choice under 'New Folder' and clicking 'Create'.
You will have an overview of your folders, see the dates they were created, the number of Faxes in each folder and be able to edit the folder or delete it.
Any Faxes contained in a created folder will revert back to either the INBOX or SENT folder if the created folder is deleted.

[[File:MyFolders.png|900px]]

== My Fax Numbers ==
In the 'My Fax Numbers' section, you will see your Fax DID numbers and description, the options that have been enabled for each number, the email address if one has been configured along with the URL if configured in the URL Callback section. You can edit the number from the 'Actions' section or choose to delete it. When editing you will have the option to set an email address to receive a notification when a new Fax is received (you can also select to have the PDF file attached in the email) and set a URL Callback (you can also enable URL Callback Retry).

[[File:MyFaxNumbers.png|900px]]

== Email to Fax==

This feature allows you to send a Fax message using your email account.

How to send a Fax message using your email account:
*Use the email account you provided when enabling the email to Fax service.
*Send the email to fax@voip.ms
*In the subject field type the destination Fax number (example: 5148000000).
*Attach the document you wish to send to the email message. VoIP.ms supports the following formats: pdf, txt, jpg, gif, png, tif.
*Send the email.

'''Important:'''

*Only the file attached will be faxed, the body of the email won't be transmitted'''
*If you have a signature at your email, avoid using pictures (logos, photos or images) on it, as it will be set as another attachment at your email and that could cause issues at the outbound fax your email will generate.

'''Security Code and From Number:'''

If Security Code is enabled, you need to add a dot (.) and the security code after the destination Fax number (example: 5148000000.Az09).

If you have more than one Fax number, you could change the "from number" by adding a dot (.) and the "from number" you'd like to use after the destination Fax number and the security code (example: 5148000000.Az09.2268280000).

If you have not enabled the security code and want to change the from number, you can add a dot (.) and the From Number after the destination Fax number (example: 5148000000.2268280000).

[[File:EmailToFax.png|900px|]]

== Forward Inbound faxes to mail ==

To have your inbound faxes forwarded to a given email address, on your customer portal, refer to:
DID Numbers --> Manage DID's. When here, select and edit the given Virtual Fax number and on the first screen you'll be presented with, enable the tick boxes: "Email address" and "Attach PDF file", as well as filling in the email address field with the desired address for the faxes to be attached to.

Grandstream HandyTone 502 - HT502

2019-07-11T14:41:34Z

B13n:

[[File:Ht502.jpg|300px|thumb|left|Grandstream HandyTone 502 - HT502]]
The '''Grandstream HandyTone 502''' is a two-line analogue telephone adapter with a built-in single port wired 10/100Mbps LAN router and network address translation (NAT). It is reported to support both tone and [[pulse dial]] (a capability which was removed from the later [[Grandstream HandyTone 702 - HT702|HT702]]).

A [http://www.grandstream.com/products/gateways-and-atas/analog-telephone-adaptors/product/handytone-502 product description] and manual is available from the manufacturer. You can access your User Manual here and it includes your device's star codes on page 25: http://www.grandstream.com/sites/default/files/Resources/ht502_user_manual.pdf <br clear="all"/>

==Connecting the HandyTone==

1. Connect a standard touch-tone analog telephone to PHONE port (or PHONE1,
PHONE2 port for HT386/496/502).

2. Connect a PSTN telephone line to LINE port (optional, applies to HT386/486/488/503 only).

3. Insert the Ethernet cable into the Ethernet port (HT286/386) or WAN port (HT486/488/496/502/503) of
HandyTone and connect the other end of the Ethernet cable to an uplink port (a router or a modem, etc.).

4. Connect a PC to the LAN port of HandyTone (optional, applies to HT486/488/496/502/503 only).

5. Insert the power adapter into the HandyTone and connect it to an electrical outlet.

6. Using the HandyTone embedded web server or IVR (Interactive Voice Prompt) menu, you can further
configure the phone using either a static IP or DHCP.

[[File:502.jpg]]

==Accessing to the Web Configuration==

1. From the analog phone, press *** to get into the IVR menu. Enter option 02 to obtain the HandyTone’s IP
address.

2. For HT486/488/496/502/503, please enable the “WAN side HTTP access” option by entering IVR
option 12 and press 9. A reboot or power cycle of the HandyTone is required after this change. You can
also access the HandyTone’s web configuration from a PC connected to the LAN port via 192.168.2.1.

3. Type the HandyTone’s IP address in your PC browser.

4. Log in using password “admin” to configure the HandyTone.

==Settings==

'''Step 1:'''

* Click on '''FXS 1''' to configure your first line.

'''Step 2:'''

Fill the followings fields.

*'''Account Active:''' Yes
* '''Primary SIP Server:''' atlanta.voip.ms (Pick one of VoIP.ms multiple [http://wiki.voip.ms/article/Choosing_Server VoIP Servers])
*'''Outbound Proxy:''' Set the same server you've configured at the '''Primary SIP Server''' field
*'''NAT Traversal:''' No, But Keep-alive
* '''SIP User ID:''' 100000 (Replace with your Main SIP account or Subaccount UserID, e.g. 198765 or 198765_sub)
*'''Authenticate ID:''' 100000 (Replace with your Main SIP account or Subaccount UserID, e.g. 198765 or 198765_sub)
* '''Authenticate Password:''' ********* (account password)

* '''SIP Registration:''' Yes
* '''Register Expiration:''' 5 minutes
*'''Preferred Vocoder:''' Select as primary option the PCMU codec and as secondary option the G729 codec
*'''Allow Incoming SIP Messages from SIP Proxy Only:''' Yes
[[File:HT502-02.png|600px]]

'''Step 3:'''
* (Optional) Select a customised dial plan.

'''Step 4:'''
* Click on '''Basic settings''' to configure your time zone.
* Set ''Time Zone'' to one of the predefined values (such as Eastern Time: GMT-5) or a self-defined time zone (for example: MTZ+6MDT+5,M4.1.0,M11.1.0) for your area.

: ''Don't forget to reboot your device after you've applied the recommended settings.''

== Dial plans ==
The use of a customised dial plan is optional.

A dial plan contains a series of digit sequences, separated by the | character, entirely enclosed within { curly brackets }. Each time a phone button is pressed, the ATA will attempt to match the digit sequence to the dial plan.

===Grandstream's default dial plan===

{ x+ | *x+ | *xx*x+ }

===VoIP.ms===

We recommend the use of the dial plan presented below, however, you can build your own dial plan depending on your needs
{911|[3469]11|*xx.|<=1>[2-9]xxxxxxxxx|1[2-9]xxxxxxxxx|<=1555>[2-9]xxxxxx|011xxxxxxxxxxxx.|011[2-9]x.| 4xxx | ***xx}
Replace the 555 with your area code if you want to be able to dial 7 digit numbers.

===Building your own dial plan===
In theory, a standard [[Dial Plan for Linksys ATAs|VoIP.ms dial plan]] could be adapted to Grandstream as:
: {911|310xxxx|<=1555>[2-9]xxxxxx|1[2-9]xx[2-9]xxxxxx|[2-9]xx[2-9]xxxxxx|*xx|***xxx|*xx.|[3468]11|822|0|00|4xxx|**275*x.|xxxxxxxxxxxx.}
This would attempt the following translations:
: 911 (the North American emergency number) is passed verbatim
: 310xxxx passes any seven-digit 310-xxxx numbers verbatim
: <=1555>[2-9]xxxxxx adds area code 1-555 to seven-digit local calls (which begin with anything other than 0 or 1)
: 1[2-9]xx[2-9]xxxxxx passes any full eleven-digit North American format (1-NXX-NXX-XXXX) telephone number verbatim
: [2-9]xx[2-9]xxxxxx passes any ten-digit North American format (NXX-NXX-XXXX) telephone number verbatim. This is not compatible with the 7-digit rule above.
: *xx passes any 'star' and two digit codes (like *73 to disable call forwarding)
: *xx. is similar but passes any code with 'star' followed by at least two digits
: ***xxx passes three stars followed by any three numeric digits
: [3468]11 passes 311, 411, 611 and 811 verbatim
: 822|0|00 passes 822, 0 or 00 verbatim
: 4xxx passes any four-digit number in the 4000-4999 range (such as 4443, an [[Dialing Codes|echo test]] for [[Troubleshooting Outgoing Calls|troubleshooting]])
: **275*x. passes any number with **275* followed by at least one digit (a [[Dialing Codes|dialling code]] to reach [http://www.sipbroker.com/sipbroker/action/providerWhitePages SIP Broker] numbers)
: xxxxxxxxxxxx. passes any number which consists of a dozen or more consecutive numeric digits

Unfortunately, in the Grandstream dial plans, as soon as one rule is matched (except for x+ or x. which allow an arbitrary number of additional digits) the call is sent out immediately. (By contrast, the Linksys dial plan will wait for a short [typically five second] delay unless 'S0' is specified explicitly). It's therefore not possible to deal with multiple conflicting alternatives by waiting for the user to dial additional digits which could potentially match some other valid pattern.

For instance 444-3xxx (a seven-digit local call) and 4443 (an echo test) might both be desired as valid for some dial plans, but can't both be supported at once. Seven and ten-digit local calls can't both be supported in the same dial plan.

For North American 7-digit dial (adds 1-555- to local calls):
: { 0x+ | *x+ | [2-9]11 | <=1555>[2-9]xxxxxx | 1[2-9]xx[2-9]xxxxxx |***xxx | **275*x+ | *xx*x+ }
For North American 10-digit dial:
: { 0x+ | *x+ | [2-9]11 | [2-9]xx[2-9]xxxxxx | 1[2-9]xx[2-9]xxxxxx |***xxx | **275*x+ | *xx*x+ }
For no translation of domestic numbers:
: { x+ | *x+ | ***xxx | **275*x+ | *xx*x+ }

Note: In the seven digit dial plan, replace 555 by the area code of your choice. The 4443 (Echo Test) and 4747 (DTMF Test) [[Dialing Codes|dialling codes]] will not be supported.

The dial plan structure (described on [http://grandstream.com/products/ht_series/ht502/documents/ht502_usermanual_english.pdf page 44 of the manual] is otherwise very similar to that described for the [[Dial Plan for Linksys ATAs]] with minor discrepancies:

{| class="wikitable"
|-
! Grandstream 502
! Cisco/Linksys ATA's
! Function
|-
| style="text-align:center;" colspan="2"|0 1 2 3 4 5 6 7 8 9 * # a b c d
| You can use any of these characters to represent a pressed phone digit.
|-
| style="text-align:center;" colspan="2"| x
| Any phone digit, [0-9]
|-
| style="text-align:center;" colspan="2"|[sequence]
| You can enter characters between brackets to create a list of acceptable digits. <br>For example, if you enter the range [1-5], the user may only press the digits from 1 to 5. <br>You can also use individual numbers, and certain other characters, in combination. For example [35-8*] allows the user to press 3, 5, 6, 7, 8 or *. [369]11 allows calls to 311, 611 or 911.
|-
| style="text-align:center;"|+ (plus) or . (period)
| style="text-align:center;"|. (period)
| You can use a period to accept zero or more entries of a give digit. <br>For example, '''01.''' allows the user to enter 0, 01, 011 and so on, while '''xx+''' allows any two or more numeric digits to be dialled.
|-
| style="text-align:center;"|<dialed=substituted>
| style="text-align:center;"|<dialed:substituted>
| This is used for sequence substitution, you can use this to indicate that certain numbers dialled are replaced by other characters. The ''dialled'' digits can be zero or more characters. <br>For example, with '''<=1555>xxxxxxx''' if the user dials a 7 digit number, the number 1555 is added to the beginning of the sequence. If the user presses 6782345, the system transmits 15556782345. ''<2=011>'' replaces digit 2 with 011 when dialling and ''< =1>'' adds a leading 1 to all numbers dialled
|-
| style="text-align:center;"|^ (leading carat)
| style="text-align:center;"|! (trailing exclamation point)
| You can use this character to prohibit a dial sequence. <br/>For example '''^1900x+''' will reject any sequence that starts with 1900.
|-
| style="text-align:center;"|{} (curly brackets)
| style="text-align:center;"|() (parentheses)
| These enclose the entire dial plan text
|-
| style="text-align:center;" colspan="2"| | (pipe character)
| These separate each of the individual rules within the dial plan
|}

There are no supported Grandstream 502 equivalents to these codes:
{| class="wikitable"
|-
! Cisco/Linksys ATA's
! Function
|-
| style="text-align:center;"|, (comma)
| No supported equivalent. Used between digits to play an “outside line” dial tone after a user-entered sequence.
|-
| style="text-align:center;"|S0 or L0
| No supported equivalent. Overrides the Short or Long inter-digit timer to 0 seconds
|-
| style="text-align:center;"|P#
| No supported equivalent. Pauses # seconds.
|}

The factory default Grandstream dial plan is: { x+ | *x+ | *xx*x+ } where:
: x matches any numeric digit
: x+ matches one or more digits
: 0 1 2 3 4 5 6 7 8 9 * # a b c d match those specific, individual digits only
Each rule is separated from the others by | and the full dial plan is enclosed in { } curly braces.

To ensure that user-dial strings such as *123 are passed through to activate features provided by VoIP.ms (as service provider) instead of being handled locally by the Grandstream ATA, the * sequence should be defined inside the dial plan; the resulting dial plan rule would contain: { *x+ }

== Known Issues and Resolutions ==

'''Hearing an Echo on the Line:'''
: Please go to your FXS port setting screen, the one you are using with our service, and verify that the option 'Disable Line Echo Canceller' is set to NO.
: You can also adjust the setting Gain, where the Rx (Other Person) is a gain level for signals transmitted by FXS and Tx (You) is a gain level for signals received by FXS.

'''Receiving Weird Calls such as from CallerID 100 or in the middle of the Night not showing in your CDR:'''
: These calls are not going through our Network but rather through the internet directly to your ATA Device.
: Please check in the Web GUI under each FXS port tab that this option is enabled: Allow Incoming SIP Messages from SIP Proxy Only: Set to YES.
: This will make sure you can only receive calls from VoIP.ms.

[[category: Analog Telephone Adapters]]

SNOM D785

2019-06-20T18:16:36Z

B13n:

[[File:D785 device.png|150px|thumb|left]]
<br clear="all" />

The [https://www.snom.com/ip-phones/desk-phones/d7xx-series/d785/ Snom D785] belongs to the latest generation of advanced Snom IP phones. Elegantly designed (Black and white) and featuring a large high-resolution colour display and a convenient second screen for dynamic contact management as well as integrated Bluetooth, this IP phone has all the functions necessary to fulfil even the most demanding requirements.

The Snom D785 is the perfect combination of advanced technology and elegant design and sets new standards with its intuitive user interface. Due to its high-resolution colour display and practical second screen, the D785 marks another milestone in the twenty-year history of the VoIP phone pioneer, Snom.

<br clear="all" />

__TOC__

=='''Accessing The Web Interface'''==

In order to configure the '''SNOM D785''' to be used along our service it is required to access it's web interface settings. For this, the IP address of the device must be acquired.

To perform this click on the "'''''Settings'''''" button of the phone. Once on the settings menu, scroll down to: " '''''Information''''' " , then select: " '''''System info''''' ". On this section, you'll need to take note of the IP address shown beside: " '''''IP Adr''''' ". It should read back something as: " '''''192.168.0.1''''' ".

Once you have the IP address please open a web browser of your preference and it's URL bar enter the IP address you got by prepending: " '''''http://''''' " and access it. Once accessed, you'll be prompted to authenticate. The default administrator password is: " '''''0000''''' ".

=='''Identity Settings'''==

Once logged in you'll be presented with this screen:

[[File:MAIN_SNOM_D785_v2.png|thumb|none|600px]]

Here, please navigate to: ''Identity 1''. Once on this page, please fill these fields as follows:

===Login Information===

:*'''''Displayname''''': The name you wish to pass when calling out
:*'''''Account''''': 100000 (replace with your SIP main account or subaccount)
:*'''''Password''''': Your SIP account's password
:*'''''Registrar''''': One of VoIP.ms multiple [[Choosing Server | servers]], you can choose the one closest to your location
:*'''''Outbound Proxy''''': The same server used above for registrar server
:*'''''Authentication Username''''': 100000 (replace with your SIP main account or subaccount)
:*'''''Mailbox''''': *97 (The feature: "BLF Directed Call Pickup" has to be left blank on the "Features" tab for this to work)

[[File:LOGIN_SNOM_D785.png|thumb|none|600px]]

Once done press the: "'''''Apply'''''" button at the bottom. Then, head to the: " '''''SIP''''' " tab. Here, fill these fields as follows:

===SIP Identity Settings===

:*'''''Dial-Plan String''''': ^.$
:*'''''Proposed Expiry''''': 300
:*'''''Subscription Expiry''''': 300
:*'''''Failed Subscription Retry Time''''': 300

[[File:SIP_SNOM_D785.png|thumb|none|600px]]

Once done press the: " '''''Apply''''' " button at the bottom. Then, head to the: " '''''RTP''''' " tab.

===RTP Identity Settings===

Here, leave only the following text on the " '''''Codec''''' " section:

pcmu,gsm,g729,telephone-event

[[File:RTP_SNOM_D785.png|thumb|none|600px]]

Finally, press the: "'''''Apply'''''" button on the bottom and then the: "'''''Save'''''" button at the top. If you're prompted to reboot the phone please do so. When all these steps are taken & fulfilled the device will be ready for use.

[[File:D735_Save.png|thumb|none|600px]]

If you experience any issues or find anything you'd like to contribute with please don't hesitate to contact us.

[[category:SIP phones]]

SNOM D785

2019-06-04T20:36:40Z

B13n:

=='''Accessing The Web Interface'''==

In order to configure the '''SNOMD785''' to be used along our service it is required to access it's web interface settings. For this, the IP address of the device must be acquired.

To perform this click on the "'''''Settings'''''" button of the phone. Once on the settings menu, scroll down to: "'''''Information'''''" , then select: "'''''System info'''''". On this section, you'll need to take note of the IP address shown beside: "'''''IP Adr'''''". It should read back something as: "'''''192.168.0.1'''''".

Once you have the IP address please open a web browser of your preference and it's URL bar enter the IP address you got by prepending: "'''''http://'''''" and access it. Once accessed, you'll be prompted to authenticate. The default administrator password is: "'''''0000'''''".

=='''Identity Settings'''==

Once logged in you'll be presented with this screen:

[[File:MAIN_SNOM_D785_v2.png]]

Here, please navigate to: '''''Identity 1'''''. Once on this page, please fill these fields as follows:

'''LOGIN'''

-'''''Displayname=The name you wish to pass when calling out'''''

-'''''Account=100000''''' (replace with your SIP main account or subaccount)

-'''''Password=Your SIP account's password'''''

-'''''Registrar=server.voip.ms''''' (any of our servers listed here: )

-'''''Outbound Proxy=The same server used above for registrar server'''''

-'''''Authentication Username=100000'''''(replace with your SIP main account or subaccount)

-'''''Mailbox=*97'''''

[[File:LOGIN_SNOM_D785.png]]

Once done press the: "'''''Apply'''''" button at the bottom. Then, head to the: "'''''SIP'''''" tab. Here, fill these fields as follows:

'''SIP'''

-'''''Dial-Plan String=^.$'''''

-'''''Proposed Expiry=300'''''

-'''''Subscription Expiry=300'''''

-'''''Failed Subscription Retry Time=300'''''

[[File:SIP_SNOM_D785.png]]

Once done press the: "'''''Apply'''''" button at the bottom. Then, head to the: "'''''RTP'''''" tab.

'''RTP'''

Here, leave only the following text on the "'''''Codec'''''" section: "'''''pcmu,gsm,g729,telephone-event'''''".

[[File:RTP_SNOM_D785.png]]

Finally, press the: "'''''Apply'''''" button on the bottom and then the: "'''''Save'''''" button at the top. If you're prompted to reboot the phone please do so. When all these steps are taken & fulfilled the device will be ready for use.

If you experience any issues or find anything you'd like to contribute with please don't hesitate to contact us.

SNOM D785

2019-06-04T20:36:11Z

B13n: /* Configuration details */

---
=='''Accessing The Web Interface'''==

In order to configure the '''SNOMD785''' to be used along our service it is required to access it's web interface settings. For this, the IP address of the device must be acquired.

To perform this click on the "'''''Settings'''''" button of the phone. Once on the settings menu, scroll down to: "'''''Information'''''" , then select: "'''''System info'''''". On this section, you'll need to take note of the IP address shown beside: "'''''IP Adr'''''". It should read back something as: "'''''192.168.0.1'''''".

Once you have the IP address please open a web browser of your preference and it's URL bar enter the IP address you got by prepending: "'''''http://'''''" and access it. Once accessed, you'll be prompted to authenticate. The default administrator password is: "'''''0000'''''".

=='''Identity Settings'''==

Once logged in you'll be presented with this screen:

[[File:MAIN_SNOM_D785_v2.png]]

Here, please navigate to: '''''Identity 1'''''. Once on this page, please fill these fields as follows:

'''LOGIN'''

-'''''Displayname=The name you wish to pass when calling out'''''

-'''''Account=100000''''' (replace with your SIP main account or subaccount)

-'''''Password=Your SIP account's password'''''

-'''''Registrar=server.voip.ms''''' (any of our servers listed here: )

-'''''Outbound Proxy=The same server used above for registrar server'''''

-'''''Authentication Username=100000'''''(replace with your SIP main account or subaccount)

-'''''Mailbox=*97'''''

[[File:LOGIN_SNOM_D785.png]]

Once done press the: "'''''Apply'''''" button at the bottom. Then, head to the: "'''''SIP'''''" tab. Here, fill these fields as follows:

'''SIP'''

-'''''Dial-Plan String=^.$'''''

-'''''Proposed Expiry=300'''''

-'''''Subscription Expiry=300'''''

-'''''Failed Subscription Retry Time=300'''''

[[File:SIP_SNOM_D785.png]]

Once done press the: "'''''Apply'''''" button at the bottom. Then, head to the: "'''''RTP'''''" tab.

'''RTP'''

Here, leave only the following text on the "'''''Codec'''''" section: "'''''pcmu,gsm,g729,telephone-event'''''".

[[File:RTP_SNOM_D785.png]]

Finally, press the: "'''''Apply'''''" button on the bottom and then the: "'''''Save'''''" button at the top. If you're prompted to reboot the phone please do so. When all these steps are taken & fulfilled the device will be ready for use.

If you experience any issues or find anything you'd like to contribute with please don't hesitate to contact us.

User:B13n/Sandbox

2019-06-04T20:32:33Z

B13n: /* Identity Settings */

File:MAIN SNOM D785 v2.png

2019-06-04T20:32:21Z

B13n: Main page SNOM D785 png correction

Main page SNOM D785 png correction

User:B13n/Sandbox

2019-06-04T20:27:41Z

B13n: /* Identity Settings */

---
=='''Accessing The Web Interface'''==

In order to configure the '''SNOMD785''' to be used along our service it is required to access it's web interface settings. For this, the IP address of the device must be acquired.

To perform this click on the "'''''Settings'''''" button of the phone. Once on the settings menu, scroll down to: "'''''Information'''''" , then select: "'''''System info'''''". On this section, you'll need to take note of the IP address shown beside: "'''''IP Adr'''''". It should read back something as: "'''''192.168.0.1'''''".

Once you have the IP address please open a web browser of your preference and it's URL bar enter the IP address you got by prepending: "'''''http://'''''" and access it. Once accessed, you'll be prompted to authenticate. The default administrator password is: "'''''0000'''''".

=='''Identity Settings'''==

Once logged in you'll be presented with this screen:

[[File:MAIN_SNOM_D785_v2.jpg]]

Here, please navigate to: '''''Identity 1'''''. Once on this page, please fill these fields as follows:

'''LOGIN'''

-'''''Displayname=The name you wish to pass when calling out'''''

-'''''Account=100000''''' (replace with your SIP main account or subaccount)

-'''''Password=Your SIP account's password'''''

-'''''Registrar=server.voip.ms''''' (any of our servers listed here: )

-'''''Outbound Proxy=The same server used above for registrar server'''''

-'''''Authentication Username=100000'''''(replace with your SIP main account or subaccount)

-'''''Mailbox=*97'''''

[[File:LOGIN_SNOM_D785.png]]

Once done press the: "'''''Apply'''''" button at the bottom. Then, head to the: "'''''SIP'''''" tab. Here, fill these fields as follows:

'''SIP'''

-'''''Dial-Plan String=^.$'''''

-'''''Proposed Expiry=300'''''

-'''''Subscription Expiry=300'''''

-'''''Failed Subscription Retry Time=300'''''

[[File:SIP_SNOM_D785.png]]

Once done press the: "'''''Apply'''''" button at the bottom. Then, head to the: "'''''RTP'''''" tab.

'''RTP'''

Here, leave only the following text on the "'''''Codec'''''" section: "'''''pcmu,gsm,g729,telephone-event'''''".

[[File:RTP_SNOM_D785.png]]

Finally, press the: "'''''Apply'''''" button on the bottom and then the: "'''''Save'''''" button at the top. If you're prompted to reboot the phone please do so. When all these steps are taken & fulfilled the device will be ready for use.

If you experience any issues or find anything you'd like to contribute with please don't hesitate to contact us.

User:B13n/Sandbox

2019-06-04T20:10:44Z

B13n: /* Identity Settings */

---
=='''Accessing The Web Interface'''==

In order to configure the '''SNOMD785''' to be used along our service it is required to access it's web interface settings. For this, the IP address of the device must be acquired.

To perform this click on the "'''''Settings'''''" button of the phone. Once on the settings menu, scroll down to: "'''''Information'''''" , then select: "'''''System info'''''". On this section, you'll need to take note of the IP address shown beside: "'''''IP Adr'''''". It should read back something as: "'''''192.168.0.1'''''".

Once you have the IP address please open a web browser of your preference and it's URL bar enter the IP address you got by prepending: "'''''http://'''''" and access it. Once accessed, you'll be prompted to authenticate. The default administrator password is: "'''''0000'''''".

=='''Identity Settings'''==

Once logged in you'll be presented with this screen:

[[File:MAIN_SNOM_D785.jpg]]

Here, please navigate to: '''''Identity 1'''''. Once on this page, please fill these fields as follows:

'''LOGIN'''

-'''''Displayname=The name you wish to pass when calling out'''''

-'''''Account=100000''''' (replace with your SIP main account or subaccount)

-'''''Password=Your SIP account's password'''''

-'''''Registrar=server.voip.ms''''' (any of our servers listed here: )

-'''''Outbound Proxy=The same server used above for registrar server'''''

-'''''Authentication Username=100000'''''(replace with your SIP main account or subaccount)

-'''''Mailbox=*97'''''

[[File:LOGIN_SNOM_D785.png]]

Once done press the: "'''''Apply'''''" button at the bottom. Then, head to the: "'''''SIP'''''" tab. Here, fill these fields as follows:

'''SIP'''

-'''''Dial-Plan String=^.$'''''

-'''''Proposed Expiry=300'''''

-'''''Subscription Expiry=300'''''

-'''''Failed Subscription Retry Time=300'''''

[[File:SIP_SNOM_D785.png]]

Once done press the: "'''''Apply'''''" button at the bottom. Then, head to the: "'''''RTP'''''" tab.

'''RTP'''

Here, leave only the following text on the "'''''Codec'''''" section: "'''''pcmu,gsm,g729,telephone-event'''''".

[[File:RTP_SNOM_D785.png]]

Finally, press the: "'''''Apply'''''" button on the bottom and then the: "'''''Save'''''" button at the top. If you're prompted to reboot the phone please do so. When all these steps are taken & fulfilled the device will be ready for use.

If you experience any issues or find anything you'd like to contribute with please don't hesitate to contact us.

File:RTP SNOM D785.png

2019-06-04T20:10:21Z

B13n: RTP Tab SNOM D785

RTP Tab SNOM D785

User:B13n/Sandbox

2019-06-04T20:09:57Z

B13n: /* Identity Settings */

---
=='''Accessing The Web Interface'''==

In order to configure the '''SNOMD785''' to be used along our service it is required to access it's web interface settings. For this, the IP address of the device must be acquired.

To perform this click on the "'''''Settings'''''" button of the phone. Once on the settings menu, scroll down to: "'''''Information'''''" , then select: "'''''System info'''''". On this section, you'll need to take note of the IP address shown beside: "'''''IP Adr'''''". It should read back something as: "'''''192.168.0.1'''''".

Once you have the IP address please open a web browser of your preference and it's URL bar enter the IP address you got by prepending: "'''''http://'''''" and access it. Once accessed, you'll be prompted to authenticate. The default administrator password is: "'''''0000'''''".

=='''Identity Settings'''==

Once logged in you'll be presented with this screen:

[[File:MAIN_SNOM_D785.jpg]]

Here, please navigate to: '''''Identity 1'''''. Once on this page, please fill these fields as follows:

'''LOGIN'''

-'''''Displayname=The name you wish to pass when calling out'''''

-'''''Account=100000''''' (replace with your SIP main account or subaccount)

-'''''Password=Your SIP account's password'''''

-'''''Registrar=server.voip.ms''''' (any of our servers listed here: )

-'''''Outbound Proxy=The same server used above for registrar server'''''

-'''''Authentication Username=100000'''''(replace with your SIP main account or subaccount)

-'''''Mailbox=*97'''''

[[File:LOGIN_SNOM_D785.png]]

Once done press the: "'''''Apply'''''" button at the bottom. Then, head to the: "'''''SIP'''''" tab. Here, fill these fields as follows:

'''SIP'''

-'''''Dial-Plan String=^.$'''''

-'''''Proposed Expiry=300'''''

-'''''Subscription Expiry=300'''''

-'''''Failed Subscription Retry Time=300'''''

[[File:SIP_SNOM_D785.png]]

Once done press the: "'''''Apply'''''" button at the bottom. Then, head to the: "'''''RTP'''''" tab.

'''RTP'''

Here, leave only the following text on the "'''''Codec'''''" section: "'''''pcmu,gsm,g729,telephone-event'''''".

Finally, press the: "'''''Apply'''''" button on the bottom and then the: "'''''Save'''''" button at the top. If you're prompted to reboot the phone please do so. When all these steps are taken & fulfilled the device will be ready for use.

If you experience any issues or find anything you'd like to contribute with please don't hesitate to contact us.

File:SIP SNOM D785.png

2019-06-04T20:09:37Z

B13n: SIP Tab SNOM D785

SIP Tab SNOM D785

User:B13n/Sandbox

2019-06-04T20:08:47Z

B13n: /* Identity Settings */

---
=='''Accessing The Web Interface'''==

In order to configure the '''SNOMD785''' to be used along our service it is required to access it's web interface settings. For this, the IP address of the device must be acquired.

To perform this click on the "'''''Settings'''''" button of the phone. Once on the settings menu, scroll down to: "'''''Information'''''" , then select: "'''''System info'''''". On this section, you'll need to take note of the IP address shown beside: "'''''IP Adr'''''". It should read back something as: "'''''192.168.0.1'''''".

Once you have the IP address please open a web browser of your preference and it's URL bar enter the IP address you got by prepending: "'''''http://'''''" and access it. Once accessed, you'll be prompted to authenticate. The default administrator password is: "'''''0000'''''".

=='''Identity Settings'''==

Once logged in you'll be presented with this screen:

[[File:MAIN_SNOM_D785.jpg]]

Here, please navigate to: '''''Identity 1'''''. Once on this page, please fill these fields as follows:

'''LOGIN'''

-'''''Displayname=The name you wish to pass when calling out'''''

-'''''Account=100000''''' (replace with your SIP main account or subaccount)

-'''''Password=Your SIP account's password'''''

-'''''Registrar=server.voip.ms''''' (any of our servers listed here: )

-'''''Outbound Proxy=The same server used above for registrar server'''''

-'''''Authentication Username=100000'''''(replace with your SIP main account or subaccount)

-'''''Mailbox=*97'''''

[[File:LOGIN_SNOM_D785.png]]

Once done press the: "'''''Apply'''''" button at the bottom. Then, head to the: "'''''SIP'''''" tab. Here, fill these fields as follows:

'''SIP'''

-'''''Dial-Plan String=^.$'''''

-'''''Proposed Expiry=300'''''

-'''''Subscription Expiry=300'''''

-'''''Failed Subscription Retry Time=300'''''

Once done press the: "'''''Apply'''''" button at the bottom. Then, head to the: "'''''RTP'''''" tab.

'''RTP'''

Here, leave only the following text on the "'''''Codec'''''" section: "'''''pcmu,gsm,g729,telephone-event'''''".

Finally, press the: "'''''Apply'''''" button on the bottom and then the: "'''''Save'''''" button at the top. If you're prompted to reboot the phone please do so. When all these steps are taken & fulfilled the device will be ready for use.

If you experience any issues or find anything you'd like to contribute with please don't hesitate to contact us.

File:LOGIN SNOM D785.png

2019-06-04T20:08:14Z

B13n: Login Tab SNOM D785

User:B13n/Sandbox

2019-06-04T20:02:03Z

B13n: /* Identity Settings */

---
=='''Accessing The Web Interface'''==

In order to configure the '''SNOMD785''' to be used along our service it is required to access it's web interface settings. For this, the IP address of the device must be acquired.

To perform this click on the "'''''Settings'''''" button of the phone. Once on the settings menu, scroll down to: "'''''Information'''''" , then select: "'''''System info'''''". On this section, you'll need to take note of the IP address shown beside: "'''''IP Adr'''''". It should read back something as: "'''''192.168.0.1'''''".

Once you have the IP address please open a web browser of your preference and it's URL bar enter the IP address you got by prepending: "'''''http://'''''" and access it. Once accessed, you'll be prompted to authenticate. The default administrator password is: "'''''0000'''''".

=='''Identity Settings'''==

Once logged in you'll be presented with this screen:

[[File:MAIN_SNOM_D785.jpg]]

Here, please navigate to: '''''Identity 1'''''. Once on this page, please fill these fields as follows:

'''LOGIN'''

-'''''Displayname=The name you wish to pass when calling out'''''

-'''''Account=100000''''' (replace with your SIP main account or subaccount)

-'''''Password=Your SIP account's password'''''

-'''''Registrar=server.voip.ms''''' (any of our servers listed here: )

-'''''Outbound Proxy=The same server used above for registrar server'''''

-'''''Authentication Username=100000'''''(replace with your SIP main account or subaccount)

-'''''Mailbox=*97'''''

Once done press the: "'''''Apply'''''" button at the bottom. Then, head to the: "'''''SIP'''''" tab. Here, fill these fields as follows:

'''SIP'''

-'''''Dial-Plan String=^.$'''''

-'''''Proposed Expiry=300'''''

-'''''Subscription Expiry=300'''''

-'''''Failed Subscription Retry Time=300'''''

Once done press the: "'''''Apply'''''" button at the bottom. Then, head to the: "'''''RTP'''''" tab.

'''RTP'''

Here, leave only the following text on the "'''''Codec'''''" section: "'''''pcmu,gsm,g729,telephone-event'''''".

Finally, press the: "'''''Apply'''''" button on the bottom and then the: "'''''Save'''''" button at the top. If you're prompted to reboot the phone please do so. When all these steps are taken & fulfilled the device will be ready for use.

If you experience any issues or find anything you'd like to contribute with please don't hesitate to contact us.

File:MAIN SNOM D785.jpg

2019-06-04T20:01:01Z

B13n: Main page SNOM D785

Main page SNOM D785

User:B13n/Sandbox

2019-06-04T19:51:04Z

B13n: /* Configuration details */

---
=='''Accessing The Web Interface'''==

In order to configure the '''SNOMD785''' to be used along our service it is required to access it's web interface settings. For this, the IP address of the device must be acquired.

To perform this click on the "'''''Settings'''''" button of the phone. Once on the settings menu, scroll down to: "'''''Information'''''" , then select: "'''''System info'''''". On this section, you'll need to take note of the IP address shown beside: "'''''IP Adr'''''". It should read back something as: "'''''192.168.0.1'''''".

Once you have the IP address please open a web browser of your preference and it's URL bar enter the IP address you got by prepending: "'''''http://'''''" and access it. Once accessed, you'll be prompted to authenticate. The default administrator password is: "'''''0000'''''".

=='''Identity Settings'''==

Once logged in you'll be presented with this screen:

Here, please navigate to: '''''Identity 1'''''. Once on this page, please fill these fields as follows:

'''LOGIN'''

-'''''Displayname=The name you wish to pass when calling out'''''

-'''''Account=100000''''' (replace with your SIP main account or subaccount)

-'''''Password=Your SIP account's password'''''

-'''''Registrar=server.voip.ms''''' (any of our servers listed here: )

-'''''Outbound Proxy=The same server used above for registrar server'''''

-'''''Authentication Username=100000'''''(replace with your SIP main account or subaccount)

-'''''Mailbox=*97'''''

Once done press the: "'''''Apply'''''" button at the bottom. Then, head to the: "'''''SIP'''''" tab. Here, fill these fields as follows:

'''SIP'''

-'''''Dial-Plan String=^.$'''''

-'''''Proposed Expiry=300'''''

-'''''Subscription Expiry=300'''''

-'''''Failed Subscription Retry Time=300'''''

Once done press the: "'''''Apply'''''" button at the bottom. Then, head to the: "'''''RTP'''''" tab.

'''RTP'''

Here, leave only the following text on the "'''''Codec'''''" section: "'''''pcmu,gsm,g729,telephone-event'''''".

Finally, press the: "'''''Apply'''''" button on the bottom and then the: "'''''Save'''''" button at the top. If you're prompted to reboot the phone please do so. When all these steps are taken & fulfilled the device will be ready for use.

If you experience any issues or find anything you'd like to contribute with please don't hesitate to contact us.

User:B13n/Sandbox

2019-06-04T19:49:08Z

B13n:

---
=='''Configuration details'''==

In order to configure the '''SNOMD785''' to be used along our service it is required to access it's web interface settings. For this, the IP address of the device must be acquired.

To perform this click on the "'''''Settings'''''" button of the phone. Once on the settings menu, scroll down to: "'''''Information'''''" , then select: "'''''System info'''''". On this section, you'll need to take note of the IP address shown beside: "'''''IP Adr'''''". It should read back something as: "'''''192.168.0.1'''''".

Once you have the IP address please open a web browser of your preference and it's URL bar enter the IP address you got by prepending: "'''''http://'''''" and access it. Once accessed, you'll be prompted to authenticate. The default administrator password is: "'''''0000'''''".

=='''Identity Settings'''==

Once logged in you'll be presented with this screen:

Here, please navigate to: '''''Identity 1'''''. Once on this page, please fill these fields as follows:

'''LOGIN'''

-'''''Displayname=The name you wish to pass when calling out'''''

-'''''Account=100000''''' (replace with your SIP main account or subaccount)

-'''''Password=Your SIP account's password'''''

-'''''Registrar=server.voip.ms''''' (any of our servers listed here: )

-'''''Outbound Proxy=The same server used above for registrar server'''''

-'''''Authentication Username=100000'''''(replace with your SIP main account or subaccount)

-'''''Mailbox=*97'''''

Once done press the: "'''''Apply'''''" button at the bottom. Then, head to the: "'''''SIP'''''" tab. Here, fill these fields as follows:

'''SIP'''

-'''''Dial-Plan String=^.$'''''

-'''''Proposed Expiry=300'''''

-'''''Subscription Expiry=300'''''

-'''''Failed Subscription Retry Time=300'''''

Once done press the: "'''''Apply'''''" button at the bottom. Then, head to the: "'''''RTP'''''" tab.

'''RTP'''

Here, leave only the following text on the "'''''Codec'''''" section: "'''''pcmu,gsm,g729,telephone-event'''''".

Finally, press the: "'''''Apply'''''" button on the bottom and then the: "'''''Save'''''" button at the top. If you're prompted to reboot the phone please do so. When all these steps are taken & fulfilled the device will be ready for use.

If you experience any issues or find anything you'd like to contribute with please don't hesitate to contact us.

User:B13n/Sandbox

2019-06-04T19:48:01Z

B13n: /* Identity Settings */

User:B13n/Sandbox

2019-06-04T19:44:25Z

B13n: /* Configuration details */

---
=='''Configuration details'''==

In order to configure the '''SNOMD785''' to be used along our service it is required to access it's web interface settings. For this, the IP address of the device must be acquired.

To perform this click on the "'''''Settings'''''" button of the phone. Once on the settings menu, scroll down to: "'''''Information'''''" , then select: "'''''System info'''''". On this section, you'll need to take note of the IP address shown beside: "'''''IP Adr'''''". It should read back something as: "'''''192.168.0.1'''''".

Once you have the IP address please open a web browser of your preference and it's URL bar enter the IP address you got by prepending: "'''''http://'''''" and access it. Once accessed, you'll be prompted to authenticate. The default administrator password is: "'''''0000'''''".

=='''Identity Settings'''==

Once logged in you'll be presented with this screen:

Here, please navigate to: '''''Identity 1'''''. Once on this page, please fill these fields as follows:

-'''''Displayname=The name you wish to pass when calling out'''''

-'''''Account=100000''''' (replace with your SIP main account or subaccount)

-'''''Password=Your SIP account's password'''''

-'''''Registrar=server.voip.ms''''' (any of our servers listed here: )

-'''''Outbound Proxy=The same server used above for registrar server'''''

-'''''Authentication Username=100000'''''(replace with your SIP main account or subaccount)

-'''''Mailbox=*97'''''

Once done press the: "'''''Apply'''''" button at the bottom. Then, head to the: "'''''SIP'''''" tab. Here, fill these fields as follows:

-'''''Dial-Plan String=^.$'''''

-'''''Proposed Expiry=300'''''

-'''''Subscription Expiry=300'''''

-'''''Failed Subscription Retry Time=300'''''

Once done press the: "'''''Apply'''''" button at the bottom. Then, head to the: "'''''RTP'''''" tab. Here, leave only the following text on the "'''''Codec'''''" section: "'''''pcmu,gsm,g729,telephone-event'''''".

Finally, press the: "'''''Apply'''''" button on the bottom and then the: "'''''Save'''''" button at the top. If you're prompted to reboot the phone please do so. When all these steps are taken & fulfilled the device will be ready for use.

User:B13n/Sandbox

2019-06-04T19:37:10Z

B13n:

---
=='''Configuration details'''==

In order to configure the '''SNOMD785''' to be used along our service it is required to access it's web interface settings. For this, the IP address of the device must be acquired.

To perform this click on the "'''''Settings'''''" button of the phone. Once on the settings menu, scroll down to: "'''''Information'''''" , then select: "'''''System info'''''". On this section, you'll need to take note of the IP address shown beside: "'''''IP Adr'''''". It should read back something as: "'''''192.168.0.1'''''".

Once you have the IP address please open a web browser of your preference and it's URL bar enter the IP address you got by prepending: "'''''http://'''''" and access it. Once accessed, you'll be prompted to authenticate. The default administrator password is: "'''''0000'''''".

Once logged in you'll be presented with this screen:

Here, please navigate to: '''''Identity 1'''''. Once on this page, please fill these fields as follows:

-'''''Displayname=The name you wish to pass when calling out'''''

-'''''Account=100000''''' (replace with your SIP main account or subaccount)

-'''''Password=Your SIP account's password'''''

-'''''Registrar=server.voip.ms''''' (any of our servers listed here: )

-'''''Outbound Proxy=The same server used above for registrar server'''''

-'''''Authentication Username=100000'''''(replace with your SIP main account or subaccount)

-'''''Mailbox=*97'''''

Once done press the: "'''''Apply'''''" button at the bottom. Then, head to the: "'''''SIP'''''" tab. Here, fill these fields as follows:

-'''''Dial-Plan String=^.$'''''

-'''''Proposed Expiry=300'''''

-'''''Subscription Expiry=300'''''

-'''''Failed Subscription Retry Time=300'''''

Once done press the: "'''''Apply'''''" button at the bottom. Then, head to the: "'''''RTP'''''" tab. Here, leave only the following text on the "'''''Codec'''''" section: "'''''pcmu,gsm,g729,telephone-event'''''".

Finally, press the: "'''''Apply'''''" button on the bottom and then the: "'''''Save'''''" button at the top. If you're prompted to reboot the phone please do so. When all these steps are taken & fulfilled the device will be ready for use.

User:B13n/Sandbox

2019-06-04T19:24:35Z

B13n:

---
=='''Configuration details'''==

In order to configure the '''SNOMD785''' to be used along our service it is required to access it's web interface settings. For this, the IP address of the device must be acquired.

To perform this click on the "'''''Settings'''''" button of the phone. Once on the settings menu, scroll down to: "'''''Information'''''" , then select: "'''''System info'''''". On this section, you'll need to take note of the IP address shown beside: "'''''IP Adr'''''". It should read back something as: "'''''192.168.0.1'''''".

Once you have the IP address please open a web browser of your preference and it's URL bar enter the IP address you got by prepending: "'''''http://'''''" and access it. Once accessed, you'll be prompted to authenticate. The default administrator password is: "'''''0000'''''".

Once logged in you'll be presented with this screen:

Here, please navigate to: '''''Identity 1'''''. Once on this page, please fill these fields as follows:

-'''''Displayname=The name you wish to pass when calling out'''''

-'''''Account=100000''''' (replace with your SIP main account or subaccount)

-'''''Password=Your SIP account's password'''''

-'''''Registrar=server.voip.ms''''' (any of our servers listed here: )

-'''''Outbound Proxy=The same server used above for registrar server'''''

-'''''Authentication Username=100000'''''(replace with your SIP main account or subaccount)

-'''''Mailbox=*97'''''

Once done press the: "'''''Apply'''''" button at the bottom. Then, head to the: "'''''SIP'''''" tab. Here, fill these fields as follows:

-'''''Dial-Plan String=^.$'''''

-'''''Proposed Expiry=300'''''

-'''''Subscription Expiry=300'''''

-'''''Failed Subscription Retry Time=300'''''

Once done press the: "'''''Apply'''''" button at the bottom. Then, head to the: "'''''RTP'''''" tab. Here, leave only the following text on the "'''''Codec'''''" section: "'''''pcmu,gsm,g729,telephone-event'''''"