Browse Author

Chris Wild

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!

Sangoma Vega SSH

It is sometimes necessary to perform more advanced debugging on Sangoma Vega’s.

The process is documented here:

Sangoma wiki

I faced a strange problem when trying to SSH onto the Vega from my Debian desktop… the connection sat there and just timed out. I could telnet to the port and was prompted with SSH-2.0-Mocana SSH but nothing was happening with SSH.

I did some digging and found that there was an incompatibility with the algorithms in use in the default configuration.

You can get around this by specifying the following SSH options:

ssh -o HostKeyAlgorithms=ssh-rsa,ssh-dss -o KexAlgorithms=diffie-hellman-group1-sha1 -o Ciphers=aes128-cbc,3des-cbc -o MACs=hmac-md5,hmac-sha1 root@hostname -p2022

Hopefully, this will serve as a reminder to me in future. If someone else finds this useful then all the better!

ProSys firmware provisioning

It has always been possible to manage firmware upgrades using our online phone management portal, ProSys. Support staff can do this very quickly by selecting from a drop-down box of available firmware on the portal.

What happens if you want a newer firmware, or just one which isn’t listed in the drop-down (yet!)?

Well, fortunately, it is possible to provide a custom setting in most cases to allow you to select the firmware you wish to provision to a device.

Proceed with caution…

You can use the “Quick entry” to add configuration settings to an individual device.
This allows you to add (key, value) pairs to the provisioning settings, giving you the power to provision firmware directly.

key value
Gigaset SYMB_ITEM_BS_IP_Data1.aucS_SPECIAL_DATA_SRV http://p.gigaset.me.uk/profiles/n510_238/42/fw238.bin
Panasonic FIRM_FILE_PATH http://pana.provu.co.uk/fw/TGP5xx-DECT-22.88_HW1.fw
snom firmware http://snom.provu.co.uk/sw/snom300-8.7.5.44-SIP-f.bin
Yealink firmware.url http://yealink.provu.co.uk/fw/T41/36.80.23.1.rom

Warning: If you are not sure you are doing this correctly, then stop! Speak to our technical team (support@provu.co.uk), we are happy to help.

As always, feedback is welcome, so please do get in touch.

Sangoma Vega gateway using RFC2833 DTMF

In some of the newer Sangoma Vega firmware, it seems like there was a default setting for the DTMF signalling which had changed from previous firmware builds.

Enter the following commands in the Vega console:

set .media.pkt_profile.1.voice.out-of-band-dtmf=on
apply
save

Recent ProSys Changes

There have been a few changes made to ProSys recently, our online ordering and phone management system.

– We have removed some old alias partcodes from the pricelist. For instance `snom320-withPSU` also as `PVSnom320` (its old partcode)

Customers who read out XML or CSV price fields are unaffected.

– We have removed the old order form from ProSys. The new one is much better.

– If you use an individual ProSys user login then the order will appear against this in our systems. Before, order confirmations and such always went to the default user on the account.

– Yealink v70 Phone Management web interface now available for use

The new interface is available if the phone last provisioned on at least v70 firmware. Otherwise, the older interface will be presented.

Any questions, then get in touch.

Customer NTP issues

What is the `ntpdate -q` alternative in Windows?

I was trying to remotely diagnose an issue with NTP on a customer VoIP device. Everything looked good on the phone but I didn’t have an easy way of checking on this.

Turns out there is a program called w32tm which helped out perfectly:

w32tm /stripchart /computer:ntp.provu.co.uk

I could ping the ntp server fine but after seeing connection timeouts on the above command, it looked like there was a firewall rule on the customer network which was causing the problems.

Yealink Remote Control features

In an automated environment, it can be useful to control things without having to physically interact with them.

I refer, of course, to having to exert my energy on reaching to dial a number on my phone. You might well save yourself these exertions on a daily basis, so you can thank me later.

Here’s an example of dialling a couple of pleasant fellows:

http://user:pass@10.10.11.100/cgi-bin/ConfigMa
nApp.com?number=118118

If you try this on a more recent firmware, you may find that it doesn’t appear to do anything. Confusing at first but it seems there was a firmware change made for security purposes (can’t complain at that but it would be nice if the phone gave a 403 response when it does fail though!)

You now need to tell the phone what IP addresses to trust. If you web browse onto the Phone>Features page, you can find a text box labeled along the lines of “Trusted Action URI Server List”. You need to enter the IP addresses that the phone expects to receive requests from, as a comma-seperated list eg. 10.10.11.200,10.10.11.201

The first time the phone receives a remote request from one of these addresses, the phone does prompt you on screen to allow or reject the request (sorry.. you need to press the buttons this time!). I haven’t seen any subsequent prompts to confirm my consent.

If you want, you can also trigger key presses remotely:

/cgi-bin/ConfigManApp.com?key=OK
/cgi-bin/ConfigManApp.com?key=1
/cgi-bin/ConfigManApp.com?key=2
/cgi-bin/ConfigManApp.com?key=3
/cgi-bin/ConfigManApp.com?key=CANCEL

Isn’t that just great? You can build this into your CRMs or whatever else you can think of.

If you don’t have a Yealink phone to hand, you can browse the range: http://www.provu.co.uk/yealink.html

Now go and have some fun!

SARK SIP-to-SIP peering

You can use the built-in SailToSail or IAX2 trunks, but both of these will use the IAX protocol. If you are wanting to achieve this sibling trunking via SIP, you will need to use the “GeneralSIP” template when creating a trunk.

The steps below are the same for both systems, so follow them through once and then repeat the same process on the other system.

– Login to the SARK web interface
– End points > Trunks > Create new ([*] button on right) > GeneralSIP
– give the trunk a dummy number (I just used 0000 in my test)

– Configure the trunk to point to the URI/IP of the target system (sibling)
– Make up a username and password
– Press “Save”

– Go back to the trunks screen and now “edit” the new trunk
– Click on the “User” tab that appears on the next page
– Set the “Asterisk User” box to be the same as your chosen username above
– the asterisk config for this trunk can then be populated into the textbox below:
“””
secret=password123
context=extensions
“””
Where the secret is the same as the chosen password before.
Now commit your changes and do the same on the other system. With any luck, these should now be peering correctly. You may wish to check on the asterisk console `asterisk -rvvvv` and then `sip show peers`

Best of luck!

Local area code on a snom desk phone

There are many ways you can build a dial plan on a snom phone.

The full range of features are documented on the snom wiki Dial Plan regex

As a quick example, here is how I can dial a local number in the area code 01484:



|^([2-9][0-9]{5})$|sip:014841@d

For many people, this may well be the only dial plan rule that they wish to use.

Get reading the documentation and see what you can do!

Yealink Handset Training Day

Last week, ProVu ran a Yealink handset training course down at the University College London (UCL). Roy from Yealink UK was also present to oversee the course and answer the commercial stuff.

The course is designed to cover the range of Yealink products and give a better technical understanding of the products. Attendees should be able to configure the Yealink phones and perform simple diagnostics to trace problems.

A wide range of topics was covered: ranging from the very basics of setting up a Yealink phone to configuring OpenVPN and discussing Yealink security features, amongst other things.

Here is a picture of me demonstrating the Yealink video phone making a video call with a Protalk Door Entry unit:

There was a Yealink goody-bag for people to take away at the end of the day which included a Yealink cup for you to SIP from.

  • 1
  • 2