Updated headset compatibility guide

You may be aware of our headset compatibility guide – we do our best to keep you informed of compatible wired and wireless headset solutions, for the entire range of phones we supply. We do extensive testing to ensure the solutions you choose; will work for your customers and that we understand how to support you, should you require any assistance.

We’ve recently added a new feature to the guide to make it easier to read! On the top right hand side of the page you are now able to filter the compatibility guide by brand. Simply select which phone brand you would like to see solutions for to narrow down the list. This means that you no longer need to scroll through all of phones in our portfolio, to find what you’re looking for.

View our Headset Compatibility Guide

 

Headset compatibility screenshot

Compatible headsets for the new Cisco 7800 and 8800 series phones

We’ve recently done some testing between the new Cisco 7800 and 8800 series phones and the headsets that we supply.

Here is a table of all the headsets and cables that we’ve tested and work with these new Cisco phones:

Headset Cable / Adaptor
Eartec 308/510/710 Range EAR-QD002(C)
Plantronics SupraPlus Range Plantronics U10
Plantronics CS500 Range Plantronics APC-42
(For EHS, use switch settings: A/3/2)
Jabra BIZ Range Jabra GN1200
Jabra Pro 920/925 Jabra Link 14201-43 (For EHS, use switch setting “B” and EHS setting “Jabra IQ”)
Sennheiser SC230 & SC260 Sennheiser CSTD 08

Please note: The Cisco 7811 does not have a headset port and therefore does not work with the headsets listed in the table above.

To find out more go to our Headset Compatibility Guide here: https://www.provu.co.uk/headset-compatibility.html

If you have any other questions or problems please contact our technical support team.

Christmas 2016 Shipping & Opening Times

Standard Mainland UK Deliveries via APC and/or DPD:

Order Date Delivery Date
23rd December* 28th December
28th / 29th December Next working Day
30th December* 3rd January
3rd January 4th January (Normal Service Resumes)

Christmas Deliveries

*Saturday delivery can be arranged for Christmas Eve and New Years Eve upon request, however this service will incur an additional charge.

Delivery Cut Off Times:

Service Date Time
APC 23rd December 12:00 PM
APC 28th – 30th December 2:30 PM
APC 3rd January 4:45 PM (Normal Service Resumes)
DPD 23rd December 12:00 PM
DPD 28th – 30th December 2:30 PM
DPD 3rd January 3:45 PM (Normal Service Resumes)

ProVu Christmas Opening Times:

Dates Opening Times
23rd December OPEN: 09:00 – 13:00
24th – 27th December CLOSED
28th – 30th December OPEN (Skeleton Staffing): 10:00 – 16:00
31st December – 2nd January CLOSED
3rd January Return to normal: 09:00 – 17:30

ITSPA Recommendations for secure deployment of an IP-PBX

 

logo

 

ITSPA has recently launched a new best practice paper ‘Recommendations for secure deployment of an IP-PBX’ (Version 3). This new document outlines configuration measures that should be implemented on an IP-PBX installed in a customer’s premises as well as the support that service providers can give to assist in the identification and avoidance of attacks.

The update forms part of ITSPA’s Best Current Practice (BCP) documents. This document follows an in-depth collaboration with members, including a range of service providers, security experts and vendors and forms part of ITSPA’s stream of work to ensure that the industry follow best practice to tackle telecommunications fraud.

For a list of ITSPA Best Current Practice (BCP) documents visit: http://www.itspa.org.uk/members/best-practice-documents/

Direct IP Call Between 2N Helios IP and Gigaset N510IP

Here is a short guide on configuring direct IP calling between a 2N Helios IP intercom, and a Gigaset N510IP. The same process will work with a Gigaset N300IP.

Both units need to be plugged in, and connected to the same network. You need to connect to the web interface of each device to configure them.

Step 1: Configure the Intercom

Go to Services > Phone and edit the Domain setting. You need to set this to the IP of the intercom itself, in our example this is 192.168.2.64

path3416

 

Then you need to add an entry to the directory, to call the N510

path3381

Here I have used 200 but you can choose any number, you will need to use this number later when configuring the N510. The IP address part must be the IP address of the N510 unit, in our example this is 192.168.2.38

Step 2: Configure the N510

Go to Settings > Telephony > Connections and Edit one of the Connections.

N510-Connection

Here you add the number that you chose earlier, and the IP address of the 2N intercom in the 3 boxes shown – Domain, Proxy Server and Registration Server. You do not need to enter a password as the N510 does not actually register to the 2N intercom.

Settings > Telephony > Advanced VoIP settings.

N510-SIP-Port

Here you set Use random ports for SIP to ‘No’, and set the SIP port to 5060.

Finally, you need to go to Settings > Telephony > Number Assignment and make sure that your handsets are set to accept incoming calls from the account/connection that you just created.

You should now be able to call to the Gigaset by pressing the button on the front of your intercom. If you are still having problems, please contact our technical support team.

End of an era for the Snom 300

Today we have shipped our last ever Snom 300!

We first shipped the Snom 300 in the summer of 2006, which makes it our longest running IP phone. The Snom 300 has been extremely popular, over its lifetime we have supplied over 32,000 models to the channel.

We announced the end of life notice back in February this year but managed to secure a large stock quantity to ensure we could continue to supply the popular model for as long as possible.

The Snom 300 will now be replaced by the new D3 series of phones which includes the D305 and D315. These have a similar design to the Snom 300, but with a BLF indicator and an improved, larger display. The Snom D315 also includes Gigabit pass-through and a USB port which allows connection of the new D3 expansion console.

Our company accountant is still using their Snom 300, which has been going strong for over 10 years! We’d love to hear about your Snom 300 stories, do you have any that are still standing the test of time?

old300-square

Yealink Provisioning: Common file mapping

This is perhaps more of a reminder to me for future reference, however, it may be useful for others too!

When a Yealink phone provisions, it requests a common provisioning file and a MAC specific one. The common one is referred to as such because each model requests a file which is unique to it.

Here are the Yealink models alongside the requested common files:

Model Common file Firmware code
CP860 CP860 y000000000037.cfg 37
T18P T18 y000000000009.cfg 18
T19P T19 y000000000031.cfg 31
T19P_E2 T19_E2 y000000000053.cfg 53
T20P T20 y000000000007.cfg 9
T21P T21 y000000000034.cfg 34
T21P_E2 T21_E2 y000000000052.cfg 52
T22P T22 y000000000005.cfg 7
T23G T23 y000000000044.cfg 44
T26P T26 y000000000004.cfg 6
T27P T27 y000000000045.cfg 45
T28P T28 y000000000000.cfg 2
T29G T29 y000000000046.cfg 46
T32G T32 y000000000032.cfg 32
T38G T38 y000000000038.cfg 38
T40P T40 y000000000054.cfg 54
T41P T41 y000000000036.cfg 36
T42G T42 y000000000029.cfg 29
T46G T46 y000000000028.cfg 28
T48G T48 y000000000035.cfg 35
VP530 VP530 y000000000023.cfg 23
VP530 VP-T49 y000000000051.cfg 51
W52P W52 y000000000025.cfg 25
W56P W56 y000000000025.cfg 25

Phew.. that should just about do it!

2N Launch the Helios IP Base – Now Available to Order

2N have launched the new Helios IP Base, in order to offer a cost-effective video intercom.

The Helios IP Base is incredibly easy to install and is configurable as a 1 or 2 button model straight out of the box. For added access control capabilities you can also add an RFID reader.

Key points:

  • Full integration with the new My2N service
  • Non-optional HD camera
  • Pictograms
  • IP65 and IK07 ratings
  • No licenced features
  • Surface mount only

The Helios IP Base is now available to order through ProSys, or you can call or email us to discuss more about it or place your order.

Snom Phone Security

We remind all snom phone customers about the security advice at http://wiki.snom.com/FAQ/How_do_I_secure_my_phone

In particular the advice to set an admin mode password on the phone. The web interface of the phone can be accessed using the admin mode password. The default of `0000` is not secure.

A http password alone is not enough to protect the web interface of the phone.

If an attacker can access the web interface of your phone, they can dial a call, which might result in fraudulent calls being made.

How to put RTX 8630 base in to multi-cell mode

1) Find the IP address of the base unit and enter that in to a web browser to configure the device.

2) Once you have logged in (Default username and password are both admin) go to “Time” on the left hand column and enter a timeserver in the field. Once you have done this click save and reboot. (a reboot is required to work correctly)

3) Now go to “Servers” (This is where we configure the PBX details and tell the extensions where to register). Enter the relevant information in to the fields and then click save.

4) Next go to “Extensions”, click “add extension” and fill in the relevant information for the extension such as authentication name and password. Don’t forget to choose the server we created otherwise the extension will not register.

5) Next go to “Multi cell” and change “Multi cell system” to “Enabled”, then create a “system chain ID” all the bases that are going to be paired need to have the same ID number. The Synchronization time can be increased/decreased to change how often the bases sync together. Leave “Multi cell debug” set to “None” for general use (only change when you need to debug issues) then click save and reboot.

Once the base has rebooted on the “Home/Status” page it should come online as Multi cell Unchained(Unchained) Allowed to Join as Primary

6) Connect the second base and follow step 1, 2, 5. (Repeat for every base being connected)

7) Once the second base has rebooted, on the “Home/Status” page  it should come online as Multi cell Unchained(Unchained) Allowed to Join as Secondary. Wait a few minuets and let the bases communicate with each other.

8) On both bases it should now look different under “Multi Cell”. The base with the extension should be listed as the “primary” and the other base/s should be “locked” under “DECT property”.

Please note: if your base has been displaying (UnchainedAllowed to Join as Secondary) for a while make sure you have created at least 1 extension on the primary base.