Browse Author

Muhammad Bajwa

Automate your web store with ProVu’s API

We have a number of APIs available for our resellers to utilise. These can help you to build your website and/or integrate with your CRM. Integrating your systems with ours can help to significantly simplify the process of getting important, up to date product information from us, as well as allowing your customers/staff to place their orders directly with us via your own online interface. Take a look at some of the benefits of using ProVu APIs.

Our APIs have been developed in-house and are constantly being updated and expanded to meet the requirements our resellers. The APIs are simple to use and can be integrated with almost all systems out there.

In this blog, we are going to look more closely at the following APIs: Product Information, Product Categories and Ordering as these tend to be the common starting points for integration.

Product Information API
There is a lot of information you can pull about the products we supply, this data can help in the building of your webstore.

Part code ProVu’s product name – this is a unique name given to each item, which is required to place orders. We can even store your own part code if you require or you can simply map these across.
Brand / Class For example Snom and Yealink.
Product Name A short concise product name.
Product Description This is a longer product description, which you can use to quickly build your product information web pages.
Product Range Some manufacturers have different ranges of products, where possible we store this information for you to use. For example, for Yealink we have T2, T4, T5 and CP. These can help to sub-categorise items within a brand/class on you website.
Retail Price Recommended retail price, this is guidance as to what you may want to charge your customers.
Your Price Your discounted trade price, this could be used with the retail price to calculate your sales out pricing to make sure you are making enough margin.
Available Stock Real-time quantity of stock available.
Item Weight Weight stored in kg can be used to help calculate shipping charges.
MPN Manufacturer’s part number/SKU.
EAN This field provides information about EAN/UPC/GTIN which is generally required for web stores using Google shops, shopify etc. You can differentiate between EAN and UPC number quite easily – if the number is 12 digits long it’s a UPC and if it’s 13 digits long it will be an EAN.

We also have a developers guide of how use our product images and datasheets to display on your own site.

Product Categories API
We provide a number product categories for example IP Desk Phone and IP Conference Phones with a list of applicable items, this can be used as a quick way to build your product menus and navigation within your web store if you wish.

Ordering API
An order can be placed by simply passing a unique order reference, list of ordered items and required quantities to us.

There is a number of other things you can tell us about your order using our ordering API:

  • Drop ship details including address and contact details
  • Drop ship branding (see more information on our Branded Shipping services)
  • Carrier service
  • Provisioning settings

 

It doesn’t stop here, we have more APIs available for our resellers including Order details, Invoices, Device status and Device management API – Take a look to find out more.

Adding IP Phone configuration details to orders

Our ProSys provisioning service enables resellers to add device-specific configuration settings while placing orders, offering a true plug-and-play service for their end-users.

As part of our continued drive to improve our online reseller portal, ProSys, we have recently made improvements to the user interface to enhance the user experience – now making it easier than ever to add device configuration details in ProSys.

How to add IP Phone configuration details in ProSys

1) The first step is to add the product to your basket. There are a couple of ways to add hardware to your basket:

You can go to the ‘Price List and stock information’ page, find the product you want to add and click on the button to add it to your basket. This will take you to the order page.

Or you can go straight to the ordering page using the button on the ProSys home page.

In the order form start typing the name of the product in the ‘Choose Product’ text box,  for example ‘Snom D715’. As soon as you start typing, the search results will start displaying a list of products with the nearest match. Simply click on the correct product you want to order to add it to the basket.

3) When you have your items in the basket, click on the button to take you to the configuration settings page.

4) On the configuration page, you will see fields like SIPUser, SIPPass and option to add up to 2 accounts to each phone. The majority of installations will only require Account A fields to be completed, but you can add a 2nd SIP account to the device if needed.

Before adding any details, please make sure you familiarise yourself with the terms on the configuration page. Find below a table which explains each setting and what should be added.

Label Setting meaning
SIPUser Extension number
SIPPass Extension password
SIPProxy Registration/Proxy server URL/IP
outboundProxy Outbound proxy (if any)
SIPPort Phone local SIP listening port
SIPDisplay Display name to appear on the phone screen
SIPIdle Idle screen name
setting_server URL/IP address to redirect the phone to another configuration server

For the majority of installations, you can safely ignore SIPPort and setting_server fields, if in doubt please get in touch.

We can also work with you to create custom configuration templates which can contain common settings such as country tones, dial plan, time server and language etc, these details can be applied to all your devices. Please speak to our sales team if you would like more information.

Tell us what you think
We’d love your feedback! Feedback helps us to make our systems even better for you and we would be very grateful for any comments, problems and suggestions you have on how we could improve ProSys in the future to best suit your needs. Login and send us your feedback or give us a call.

If you do not have a login or have forgotten your password you are able to request a new one here.

Recommended Iphone/Ipad app for Protalk/Fermax Door entry system

Lots of people have been asking us to recommend an app that works with the Protalk/Fermax IP range of door entry systems. Though there are hundreds of them on the Apple store, not all work perfectly with Protalk’s IP door entry system.

Problem :

There are 2 main issues.

1. Multitasking

Multitasking means running an app in the background while the user can do other things. It is important to install/buy an app that supports multitasking if you wish to receive calls when the ipad/iphone is in sleep mode.

2. SIP over TCP support

Apple only ever allows a SIP application to work in the background (multitask) when it supports SIP over TCP. Its just the way they have built IOS(Apple’s operating system). When buying an app to work with a hosted solution or a PBX provider, make sure they support SIP over TCP.

Solution:

The solution is to use a PBX/Hosted provider which supports SIP over TCP or alternatively buy a SARK200 PBX which, along with offering other benefits, works for both video and audio over the TCP protocol. For for information about SARK 200 please click here.

Recommended Applications :

Audio /Video Application:

There are two applications that we have successfully tested with the Protalk video entry system.

Acrobits Softphone
UDVguard

Audio only applications :

For audio only door entry system you can use :

Linphone
Acrobits
Bria SIP phone

Please note that ProVu do not develop these applications. If the application crashes or stops working due to an update we cannot be held responsible. You will have to liaise with the company who develop these apps.

SNAP – Sangoma Vega Provisioning Tool for ITSP and Installers

Sangoma has launched a new web tool for ITSPs that allows for quick and easy provisioning of Vega gateways. The tool allows ITSPs to generate configuration files for any Vega gateway without having to manually configure each setting on the web GUI. SNAP walks through a series of screens and spits out a final configuration file which can be uploaded to the Vega.

To benefit from the tool, the ITSP will have to provide a test account and general install scenario such as whether the box will be on DHCP or static IP address, what codec types to use, etc. Sangoma will then test those scenarios with provided test account and make the final template available for users to download. There is no limit on the number of templates. Multiple templates can be created for the same product according to the scenario.

Have a look at the link below to get a general idea of how it works.

http://vegaconfig.com

Snom phones support for Office365 (Lync Online)

With growing interest in MS Lync, more people are moving to Lync online(Office 365) to benefit from the Microsoft feature rich platform. Some people think it’s a good investment and some think its not. Well I shall leave it to people to decide.

Coming back to the original subject, we are being asked if Snom Lync firmware supports Lync Online or not. The short answer at the moment is No. We understand all the customers requesting Lync Online (Office 365) support in Snom UC edition. The main challenge for Snom devices/development is a new additional login mechanism. To login to O365, Snom need to implement a new OrgID authentication method in their Lync firmware. By the way: in on-premise or Hosted-Edition deployments of Lync Server there is no such additional login using OrgID Authentication. Support for OrgID is on Snom’s roadmap, but an ETA is not available. We hope for the beginning of next year.

Personally, I expect that when we have O365 supported Snom firmware, clients will start requesting Lync On-Premise feature-set, that Snom as a device vendor wont be able to deliver(this may change). In other words OrgID support will be a resolution causing new “challenges”.

Please note: clients requesting phone support in O365 should carefully have a look on the O365 Plans (P1,P2,..,E1,E3,.. etc.) as only E4 support phone/pbx features/PSTN break out’s. E4 plan costs £17.75 per user per month. For the small organisation it’s reasonable but when you start adding more people to the system the cost increases to a level where it would be better to have an on-premises Lync device. Sangoma has recently introduced a Lync appliance that allows O365 integration along with a built-in VoIP gateway.

Find out more information on the Sangoma NetBorder Lync Express Gateway.

Vega 400/200/100 firmware recovery

If you have bricked your Vega box during the firmware upgrade process or something similar then it can be recovered.

You will need the following items for recovery.

  • Console cable (RJ45 to Serial converter). Vega 400/200/100 comes with a console cable.
  • Computer running Windows/Linux or Mac.
  • Terminal client such as Hyper Terminal, Minicom or Putty.
  • USB to Serial converter (optional: only required if computer does not have a serial port)

Recovery Procedure:

  • Turn off Vega
  • Connect RJ45 end of cable to console port and connect the serial connector to the serial port on computer.
  • Connect to Terminal client of your choice and set following configuration
  • Speed: 9600
    Data bits: 8
    Parity: None
    Stop bits: 1
    Flow control: None

  • Turn on Vega box and press Enter button a couple of times until the message “Press ‘Y’ to enter Boot Menu ” appears on terminal window.
  • Press ‘Y’

Note: Check the connections if nothing appear on terminal screen.

    Vega400 BootLoader: Version 3.00
    FPGA Test Pass (FPGA Version 3)
    RAMTest Pass – 64Mbytes verified
    Programmed MAC Address 00505816244A
    Press ‘Y’ to enter Boot Menu

    VegaStream Boot Menu Version 3.00
    ———- —- —- ————

    1) Download Boot Image (SRec)
    2) Download Firmware Image (SRec) (115K2 Baud recommended)
    3) Config Clear
    6) Switch Boot Partition
    D) Duplicate FLASH
    F) Set Flow Control (currently Hardware)
    Z) Set speed high (115200 Baud)
    E) Exit BOOT and Run Firmware

  • Finally press 6 to choose option 6 i.e. switch boot partition press 6 and wait couple of seconds. This setting will change the partition to older firmware version press E to exit and reboot to old firmware.

After the reboot the Vega should come back with older firmware and settings.

RTSP streaming from Protalk/Fermax door entry to VideoLan

You can now stream video directly from the Protalk door phone to your favourite rtsp streaming media server or VideoLan software.

If you are unsure what rtsp means then have a look at this wiki page.

This new feature will allow CCTV/Security installers to integrate video from the Protalk in existing video monitoring/recording software.

Protalk builtin rtsp server support H264 or H263 video format and listen on port 554.

VideoLan Configuration:

To see video stream on VideoLan software.

  • Open program then go to Open Media > Open Capture Device > Network and put “rtsp://ip.address.of.doorphone:554” finally press the Play button.

All being well you will see video from the door phone. If you want to force the rtsp server to use H263 or H264 then add the following in your url field.

‘rtsp://ip_address/video.263’ to force H263
‘rtsp://ip_address/video.264’ to force H264

If you face problem with any of above please get in touch.

This blog post applies to CityLine,SkyLine and SlimLine products.

 

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**

UDVguard- Free Android App For Protalk Door Entry System

We are pleased to announce first Android app for the Protalk door entry system.

NOTE: This app also works with Cityline and Skyline products.

Some of the main features of the app are:

Monitoring of multiple door stations:
You can monitor multiple door phones under one interface.

Controlling of door phone:
User can unlock the door from the interface i.e by pressing the designated button on the screen. Also a call can be initiated from the app to the door phone.

Multitasking:
This app can sit in the background while you do other things.

SIP Support:
It support both sip server mode and peer to peer mode.

The UDVguard application is available free of charge from Google Market place.

 

Installation and Configuration:

* Turn on Wifi

* Open Market place and search for UDVGuard. Install and run the program.

* Select Menu >> Settings > DoorPhone Management. Add the IP address of the door unit to monitor. By default, the program offers parameters 192.168.1.250 and port 80. Change the IP address to match IP of the door phone.

* If you want to software to pop up on incoming calls check “Pop Up” box .

* Default audio mode is set to Peer-to-peer. Select it according to your requirement. If using SIP mode , remember to add sip user info in relevant fields.

If everything is setup up properly you should be able to receive a call on your device if someone presses the button on the door.

WARNING: This software runs in background. Please quit the software when not in use to save battery.

Tested Devices

Tablets:
Acer Iconia Tab A500
Manta MID01

Mobile phones:
HTC Wild Fire A3333
HTC Desire
Samsung Galaxy GT-i9000
Samsung Galaxy mini GT-S5570

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.

  • 1
  • 2