Connecting new phones
To be able to use your new phones, please follow the instructions below.
General provisioning
- Get the phone id's that have been attributed to the new phones from Escaux technical support:
----------------------------------------------------------------------------------------
Phone ID's are (for example SDP20083) ...
----------------------------------------------------------------------------------------
- If those new phones have not yet been defined, you may define them by yourself :
- Before changing anything on the SMP (smp.escaux.com), it may be useful to take a configuration snapshot:
Navigate to: Advanced > Configuration Management > Create Configuration Snapshot
- Add the phones at
Navigate to: Resources > IP Phones
Do not forget to click on the Phone Profile (for ex. GrandstreamGXP2000.ver.2.1) to configure:
- MAC address
- VLAN (if applicable)
- Speeddials (if applicable)
- Timezone
- ...
- Please attribute each phone to an extension
Navigate to: Directory > Internal Directory
- Click on "Apply Changes" to activate the changes.
Navigate to: Apply Changes
- Connect phones to the LAN and power them (if Power over Ethernet is not used).
- If VLANs are used, see important remarks below
- The first time the IP phones are connected, they should be plugged in a port on the switch that is configured in Voice VLAN only mode. They'll get their initial configuration, with their VLAN ID. Important remarks :
- The VLAN Id should not be defined on the phone in any of the 2 situations below:
- the switch and the phone are both from Cisco -> they use CDP
- the phone will be connected to a port configured in Voice VLAN only mode (i.e. no PC will be connected behind the phone)
- Polycom phones : VLAN Id needs to be defined manually at the first boot (More info here. This means they need to be directly connected to a switch port configured in "trunk" mode (Voice VLAN + Data VLAN).
- Once VLAN ID is configured, phones need to be plugged in a switch port configured in "trunk" mode (Voice VLAN + Data VLAN).
Special provisioning for Polycom phones
By default, Polycom phones will try to fetch their configuration using FTP which is not supported. This can be changed manually (read on) or
through a DHCP option.
At first boot, you will see the Welcome screen and "x seconds before reboot". During this notification:
- Press "SETUP" Enter the password : 456 and press on "Ok"
- To change FTP to TFTP manually (if applicable) :
- Use the navigation arrows to select "Server Menu"
- Select "Server type".
- Use the navigation arrows ( LEFT and RIGHT ) to select "Trivial FTP" Press on "Ok"
- Press "Exit"
- Define VLAN ID (if applicable) :
- Use the navigation arrows to select "Ethernet Menu"
- Edit "VLAN Id" + "OK"
- Press "Exit"
- Disable CDP :
- Use the navigation arrows to select "Ethernet Menu"
- Select "CDP".
- Use the navigation arrows ( LEFT and RIGHT ) to select "Disabled" Press on "Ok"
- Press "Exit"
- Press "Exit" and "Start"
Register and subscribe Polycom Kirk and Spectralink 40xx phones
- On the SMP admin web page
- Create a SDX Generic SIP phone
- MAC Address: IPEI of the phone (strip the last digit off if necessary)
- DTMF mode: rfc2833
- Password: 1234
- Assign an extension and do an Apply Changes
- Connect to the SOP through SSH and make a tunnel so that you can connect to the W6000 Polycom antenna in your web browser
- In your web browser, connect to the antenna
- Login: admin
- Password: ip6000
- Users > Add
- IPEI : 0 _ _ _ _ _ (MAC Address / IPEI - Same as the of the Resource in SMP admin)
- Access Code : 1234
- Standby Text : (Whatever customer want - same as in SMP admin web page)
- Username / Extension : SDX _ _ _ _ _ (Resource ID)
- Displayname : (Whatever customer want - same as in SMP admin web page)
- On the DECT phone
- Menu > Inscription > Create
- Enter the password (1234) and validate
Special provisioning for Grandstream GXP2000 phones
In order to use the french interface of GXP2000 phones, you have to use the Grandstream phone support version 1.3 and SDG resource version 2.2.
Since GXP2000 read their configuration before upgrading their firmware but old firmwares can't read lang tag and, you have to:
-
- Upgrade firmware with resources in EN
5042.273870 10.99.2.31 -> 10.99.0.10 TFTP Read Request, File: cfg000b8215ca3a, Transfer type: octet
5042.657728 10.99.2.31 -> 10.99.0.10 TFTP Read Request, File: boot55d.bin, Transfer type: octet
5042.877582 10.99.2.31 -> 10.99.0.10 TFTP Read Request, File: gxp2000d.bin, Transfer type: octet
5097.481372 10.99.2.31 -> 10.99.0.10 TFTP Read Request, File: ring1.bin, Transfer type: octet
5100.707919 10.99.2.31 -> 10.99.0.10 TFTP Read Request, File: ring2.bin, Transfer type: octet
5102.598807 10.99.2.31 -> 10.99.0.10 TFTP Read Request, File: ring3.bin, Transfer type: octet
5105.244853 10.99.2.31 -> 10.99.0.10 TFTP Read Request, File: gxp.lpf, Transfer type: octet
* Change resources to FR, Apply Changes
5415.403020 10.99.2.31 -> 10.99.0.10 TFTP Read Request, File: cfg000b8215ca3a, Transfer type: octet
5415.786784 10.99.2.31 -> 10.99.0.10 TFTP Read Request, File: boot55e.bin, Transfer type: octet
5416.006710 10.99.2.31 -> 10.99.0.10 TFTP Read Request, File: gxp2000e.bin, Transfer type: octet
5416.966208 10.99.2.31 -> 10.99.0.10 TFTP Read Request, File: ring1.bin, Transfer type: octet
5417.260104 10.99.2.31 -> 10.99.0.10 TFTP Read Request, File: ring2.bin, Transfer type: octet
5417.541289 10.99.2.31 -> 10.99.0.10 TFTP Read Request, File: ring3.bin, Transfer type: octet
5417.745965 10.99.2.31 -> 10.99.0.10 TFTP Read Request, File: gxp.lpf, Transfer type: octet
- Factory reset (Only if really needed)
Special provisioning for Snom
Here's the procedure to connect any Snom IP phone:
- a Snom phone should automatically use TFTP autoprovisioning
- At first start, it reboots 3 times:
- first: reboot after reset
- second: reboot after ereasing application
- third: reboot after installing application
- The Snom phone should have the kind of display:
Date First_name Last_name Time
PhoneBk Reg CallLog
- if name = NR (Not Registered) after 2minutes, whereas the smp has been configured (ip phones & extension has been defined + "Apply Changes"), you perhaps have to reset the phone:
- press "Settings" button (at any time) > "Reset" (first contextual button)
- Default admin passord is "0000"
- For a Snom M3, you should
- do a firmware upgrade :
- set the transfer protocol to TFTP:
- Point your browser to the IP address of the basestation
- login as admin/admin
- Go to advanced
- Change "transfer protocol' from "http" to "tftp"
- press "save changes" and "reboot"
Snom and VLAN configuration
- Begin with configuring the resource in the SMP and fill in the voice vlan id (e.g. 5).
- Make sure the switchport on which you will connect the SNOM is properly configured with default VLAN DATA and allowing VLAN Voice (e.g. native vlan 2 (untagged) and allow vlan 5 (tagged)).
- Make sure routing between VLAN voice and VLAN data is configured
- Make sure the DHCP server in the data vlan is configured correctly. Refer to the CustomerDhcpServerConfiguration document on how to correctly configure the DHCP server.
- Connect the SNOM phone to the port and let it boot. It will download its configuration from the SOP and remain in the data vlan.
- Reboot the SNOM phone manually. It will immediately be in the Voice vlan (info from config file) and will do its DHCP requests in the voice vlan.
Special Provisioning for Topic Phones
- DHCP option 66 is needed
- Topic phone support module should be installed
- Topic resource is needed when connecting new phones
- CDP & LLDP are not supported
Connecting Cisco SPA2102 converters
Installation procedure
- Add resources on the SMP: 1 resource per line (might already be populated)
- On the ATA two cables have to be plugged:
- phone/fax RJ11 cable in 'PHONE1' (&PHONE2) port.
- RJ45 cable in 'INTERNET' port (the BLUE one).
- same RJ45 cable in your switch.
- The 'Ethernet' connexion should never be used.
- Plug the power cable in the ATA
Wait for about 60 seconds (until the two first LED stay lit - second one could blink).
- Unplug/replug the power cable in the ATA
Wait until at least the tree first LED stay lit
The majority of devices supported by Escaux are auto-provisioned in a single reboot cycle. The Cisco ATA devices are a bit different:
- The first boot allows the device to get its profile file (i.e. spa2102.cfg), with a link to the necessary configuration files.
- The second boot allows the device to get its actual configuration file (i.e. spa2102-000e081c9bf0.cfg) which contains the necessary configuration data.
FAQ
Problem |
Solution |
No dial tone third LED never switched on |
Phone unplugged and/or device seems to be unregistered. Did you apply SMP changes? |
Power LED blinking |
Check IP address (can be done by phone, check the "installation & compliance guide") |
Calling another phone works, but receiving calls doesn't work |
Did you correctly define callflows & did you apply SMP changes? |
Factory reset
- Pick up the phone connected to line 1, enter the following sequence: ****73738# then confirm by pressing 1
Check IP address
- Pick up the phone connected to line 1, enter the following sequence: ****110
Connecting Grandstream BudgeTone analog converters
In annex you will find the print screens of the Grandstream BudgeTone 101's web interfaces with the parameters that need to be filled in.
Web interface password: admin
Authenticate password: 20050305
Attention points : "Send DTMF : via SIP info " !
FXS impedance: "CRT21 (...)"
- Screen1:
- screen2:
- screen3:
- screen0: