Browse Category

Technical Hints

Registering RTX4002 Repeater with N300/N510 IP Base

Updated 09/02/2018 – Luke Warby

*RTX4022P can not be set up in Daisy Chain with 3rd party devices such as Gigaset and Yealink*

Updated 10/01/2014 – Chris Wright

Below are some instructions that will help in registering a RTX repeater with Gigaset Base station.

DO NOT PLUG IN THE REPEATER UNTIL INSTRUCTED

1. Set the range extender up near the Gigaset Base Station, you can move it to its final
destination later.

2. Turn off Eco Mode through the Gigaset handset, go to Settings – Eco Mode. Untick the boxes if necessary

3. Turn on Repeater Mode through the Gigaset handset, go to Settings – System – Repeater Mode.
(If you are using firmware 42.194 or greater, you will need to disable the Encryption setting at this stage rather than enabling Repeater mode. More info here)

Updated 28/03/2018 – Jordan Carr

*RTX4022: press the button on the back of the repeater for 5 seconds instead of plugging the power in*

4. NOW PLUG THE POWER INTO THE RTX 4002 for 5 seconds and turn it off again; then turn it back on.

Note: The LED on the RTX 4002 slowly flashes showing that it is now in registration mode.
This should be a single flash, if it is a double flash please go back to Step 1 and retry.

5. Turn on Registration on the Gigaset Base Station, by either:
a. In the web GUI, go to Management > Miscellaneous > Start Registration’

b. On the Gigaset Base Station, press and hold the PAGE/FIND button for approximately 3-5 seconds

Note: The LED on the RTX 4002 flashes quickly to show that it is in ‘learn’ mode.

6. On the Handset – Key in X* – where ‘X’ is a number between 2 and 7. (This relates to the repeater number – the first repeater is number 2 as the N300 is the first link (1).)
Then press the green SEND button.

The LED will stop flashing for about 5 seconds; press * again to confirm the pairing. The LED should now show a steady light without flashing.

Note: If the LED goes back to flashing quickly then the new settings have not been saved or accepted by the RTX 4002. Repeat item 5. If the LED goes back to flashing quickly again then repeat item 5 with a different X.

7. Now position the RTX 4002 where required, ensuring that it is still within range of the Gigaset Base Station.

** If you hear a chirping/beeping noise when on call within range of the RTX, you may have enabled the verfication tone. For instructions on turning this off, please view our blog post**

Panasonic factory reset

To do a proper factory reset of a Panasonic SIP phone you need to have the phone in front of you.

There is a reset option in the web interface but this will only reset any settings that had been set in the web interface itself. Any settings that have been provisioned will persist.

On the phone:

  • Press the “setting” button to go into the settings menu

  • Dial: #136 on the keypad

  • A hidden menu will appear, select “Factory Reset”

  • Press up or down to choose “yes” and then Enter

  • Repeat the previous step for the “are you sure” prompt

  • The phone will now reboot itself

Once rebooted, it’ll be fully reset. Just be aware, if the phone has been provisioned it may well call home to the provisioning server and get some settings applied from that. You’ll have to speak to whoever does your provisioning for us (hopefully us!).

cheers,
Paul.

Door entry wiring diagram 2 – fail safe, high power magnetic lock with CityLine/SkyLine/SlimLine

This connection diagram shows how to wire up a high-power (more than 350mA) electronic door lock using an external power supply with any of the CityLine, SkyLine or SlimLine range of door entry devices.

CityLine info.

SkyLine info.

SlimLine info.

Wiring Diagram

Parts Required

These can all be bought from ProVu.

    • Any ProTalk CityLine, Skyline or SlimLine IP door entry kit

 

    • 240Volt AC mains to 12Volt DC power supply (with internal battery back up highly recommended)

 

    • A 12Volt “fail-safe” door lock – large magnetic lock shown in diagram

 

    • A “push to break” exit switch

 

    • “VHLD” – Very Handy Little Delay

 

Notes

    • Mains voltage is dangerous! If you aren’t 100% confident you know what you are doing, hire a qualified electrician (at least for the power supply installation)

 

    • This set up is intended for use when you have large locks that require more than 350mA current or as a way of adding battery back up

 

    • Whilst the door entry unit itself can be powered from PoE, it makes sense to use the same 12V power supply since it is installed and (hopefully) battery backed

 

    • Make sure the power supply is more than capable of supplying enough power for both the lock(s) and the door entry unit

 

Door entry wiring diagram 1 – fail safe, low power, strike plate with CityLine/Skyline

This connection diagram shows how to connect a electronic door strike plate up to any of the CityLine or SkyLine IP door entry units we sell.

CityLine info.

SkyLine info.

Wiring Diagram


 

Parts required

These can all be bought from ProVu

    • Any ProTalk CityLine or SkyLine IP door entry kit

 

    • A 12Volt “fail-safe” electronic door strike (max 350mA)

 

    • A “push to break” exit switch

 

    • “VHLD” – Very Handy Little Delay board

 

Notes

  • Ensure the exit switch is push-to-break, not push-to-make, or this will not work
  • If an emergency break glass is needed, connect this in series with the normal exit switch
  • The Door Entry unit cannot supply more than 350mA from the 12Vout connector, do not attempt to use a door lock which will draw more power or you will damage the door entry unit (and void the warranty!). If you have a more powerful door lock then a separate power supply must be used (which I’ll draw a diagram for soon).
  • 12Vin is not shown connected as you can power the whole device & circuit from either this or Power-over-Ethernet.
  • You can adjust the amount of time the door is unlocked for by setting the “delay” potentiometer on the VHLD board, anti-clockwise increases the delay.

I will be drawing a series of these diagrams to suit various scenarios so keep checking here for more.

snom phones – which caller ID to use on inbound calls

There are several ways a snom phone can get Caller ID Name for an inbound call.

The first is from the Invite message of the inbound call from the sending SIP end-point. If a “Name” part of the Caller ID exists then this will be used by the Snom phone to display the name on the screen.

The phone can also get a name from it’s internal address book or an LDAP server if one is configured. However, it will only use this if there is no “Name” part of the Caller ID in the incoming Invite.

If you want to change this behaviour set this setting in the Snom phone’s web interface:

  • Advanced => Behaviour => Prioritise PBX Number Lookup

To “off”. Then an internal address book or LDAP server will take precedence.

More information here:

Snom Wiki

*****
UPDATE

This setting has no been superseded. From software version 8.7.3.19 use setting contact_source_priority

Information on snom Wiki:

http://wiki.snom.com/Settings/contact_source_priority

Yealink Security Advisory

Yealink have recently issued “Technical Bulletin 01/11” which advises on security vulnerabilities. The bulletin advises users to upgrade phones to the latest firmware versions and also gives advice on the importance of changing default passwords.

We have attached the Technical Bulletin and a link to the location of latest firmware versions, http://www.yealink.co.uk/downloads/

ProVu Communications take the security of the products it sells very seriously and we would strongly advise that you follow the advice given by Yealink. If you need help or advice on any of these matters please do not hesitate to call our technical support team on 01484 840048

Additionally we may be able to help you deploy these changes to your Yealink handsets remotely using our Prosys phone management system. Prosys phone management will allow you to remotely access your CPE to change firmware versions and generate passwords amongst many other things. Again if you would like further information please contact ProVu Communications on 01484 840048.

Cisco Small Business Phones and LDAP directory

Cisco Small Business phones (the SPA-3xx and SPA-5xx ranges) support central address books using LDAP.

The settings are notoriously difficult for people unfamiliar with LDAP to get right. Here is my example using an OpenLDAP server:

Cisco LDAP settings screenshot

So in my LDAP tree I’m using sn for surname and cn for first name.

Set up with Microsoft Active Directory shouldn’t be too much different from this but the exact settings will just depend on your AD structure.

Connecting ProTalk SIP door phone with Digital keypad and Push button

In my Previous blog post, I explained how to connect a digital keypad with ProTalk door unit. That was entertaining was is`nt :). Now lets add a push button to the previous scenario to make things more exciting.

The blog post will go through the process of attaching all three components together. Each module comes with separate connection cables that can be found in packaging. You should have following cables with each module.

a. Audio/Video module:

>> 1 x 8 pin connector (CC8)

b. Digital Keypad:

>> 1 x 5 pin connector (CC5)
>> 1 x 3 pin connector (CC3)

c. Push Button:

>> 1 x 3 pin connector (CC3)

Lets start connecting these components step by step.

1. Connect CC8 cable to 8 pin connector on Audio Video module.

2. Connect one end of CC5 to Output(CN2) and one end of CC3 cable to Input(CN1) connector on the keypad.

3. Connect CC3 cable to the Input(CN1) on the push button.

If everything is connected correctly, it should look something like this.

Now lets move forward to last few step.

4. Connect other end of CC3 cable connected to push button to LT(3 pin) connector on A/V module.

5. Connect second end of CC5 cable from keypad to EXP(5 pin) connector on the A/V module and CC3 cable to the Output(CN2) on the push button

6. Finally, last step is to connect the CC8 cable to the push button. One thing to keep in mind is, each cable from the 8 equate to “key 3-10” on the web interface. i.e.

black = 3rd pushbutton
orange = 4th pushbutton
green = 5th pushbutton
white = 6th pushbutton
red = 7th pushbutton
yellow = 8th pushbutton
brown = 9th pushbutton
blue = 10th pushbutton

Since our scenario just has one push button in place, I need only one out of 8 cables i.e. Black. So last step is to plug the stripped end of the black cable to the green screw terminal block on the push button.

Click picuture 1 or 2 to see final connections.
Picture 2

NOTE: Microphone is part of front frame on Skyline units and not shown in pictures above. Please make sure to connect it to the sip module

Now log on to the web interface of the door unit and configure the unit to get things started.

Snom phones using SIPS/SRTP encryption with Asterisk 1.8

I’ve been looking forward to the time when Asterisk catches up with the rest of the SIP world and starts working with encrypted SIP and encrypted RTP (SIPS & SRTP respectively). Asterisk has supported it since the recent release of version 1.8 so I had to get it working.

Asterisk only supports a fairly fixed set of encryption options so you’ve got to set the phone up just right for it to work. I’d also say that SIPS & SRTP is very much new functionality in Asterisk so I’d treat it as for testing purposes only right now….although it’s looking promising.

Snom phones have supported both SIPS & SRTP for years (in fact I think they were the first IP phones on the market to do so). So if any phone can get it right it should be them, perfect to test with.

I am using the following to test with:

  • Current Debian Asterisk 1.8 packages maintained by Digium on Debian Squeeze (deb http://packages.asterisk.org/deb squeeze main)

  • My actual Asterisk version at the time of writing is “1.8.4.1-1digium1~squeeze”. Some older ones didn’t work.

  • Snom 300 with 8.4.31 firmware. It will not work with much older versions.

I’m not going to go into the setup of Asterisk itself as there is plenty of information on this out on the Internet, not to mention quite a lot of different ways of doing it. I will just mention that I am using a self-signed SSL certificate, this means you either have to leave server verification turned off on the phone (which it is by default on this firmware version) or import your own CA into the phone. Neither of which are ideal for a real world deployment, you’d buy a server certificate from a recognised CA in that case but for testing….

The important bits in Asterisk

OK so I will mention a couple of things in the Asterisk setup… all in sip.conf

  • tlsenable=yes : in general section

  • domain=ast18.provu.co.uk:5061 : this is needed for it to work

  • transport=tls : used in the general section or in each sip peer/friend to turn on tls for SIPS

  • port=5061 : in general or each sip peer/friend. 5061 is the usual port for SIPS

  • encryption=yes : turns on SRTP, if you have set this then the SIP device(s) MUST use it, it’s either on or off, not optional

There are more settings needed than this, please read the Asterisk documentation.

Snom phone setup

Everything is in identity 1, these are obviously examples only! You’ll need to put your own Registrar in etc…

Login tab:

  • Account: sip username

  • Password: sip password/secret

  • Registrar: ast18.provu.co.uk

  • Outbound Proxy: sips:ast18.provu.co.uk:5061

  • Authentication Username: sip username

SIP tab:

  • Support Broken Registrar: on

RTP tab:

  • RTP Encryption: on (should be default…)

  • SRTP Auth-tag: AES-80

  • RTP/SAVP: mandatory

That should be it. As mentioned the Snom phones do not verify the server certificates by default. If you want to turn this on then go to the “Certificates” page in the phone setup and click “Activate”. But bear in mind you must either use a certificate from a known CA or import your own certificate into each phone manually. Certificates must be in DER format for this.

To confirm it’s working, look for the little lock symbol on the phone screen during calls. It should look closed when the call is secure. For further confirmation you can do a pcap trace on the phone, open this up in Wireshark and then not be able to view the SIP packets or decode the audio to anything but white-noise.

Let me know if anyone thinks it’s worth me putting together a how-to with the full Asterisk config too.

Skyline/Cityline Door Unit connection with Digital Keypad

This blog post explains connecting and configuring of a Digital Keypad

Connections are quite simple. Cityline Keypad comes with two different cables.

1 X 3 pin connector
1 X 5 pin connector

Step 1: Connect the 3 and 5 pin connector to INPUT and OUTPUT connections on the cityline keypad board. Click here for diagram

Step 2: Connect 3 pin connector to connection LT (point 19 on this picture) of the Audio/Video module

Step3: Connect 5 pin connection to EXP connection or connection 18(Please refer to digram in step 2).

Step 4: Finally to be able to dial numbers from keypad,
login to the web interface of the door unit and go to Basic Parameters.

Change the following settings:

1. Keyboard to position : 1
2. Under mode of keyboard choose Direct choice number (phone)

Thats it. Now enter the number and press the A button to dial it.

To unlock the door using keypad, configure unlock codes under Relays section of web gui and save changes. Finally press the B (Bell) button and enter to code to unlock door.

If you don’t want a unit with a keypad and only interested in 1 or 2 button door entry products please look at the our ProTalk range.