Recent Changes - Search:

Resources


IP PBX Systems


Telephony Switch


Phones


Access Gateway
Signaling Converter


Lawful Interception Recorder


Others


Discontinued Products


Main Domains


In Social Media


About Us
Contact Details





.

Basic_Programming_Tutorial

********* This document is not complete *********
************* and may contain errors ************
******** PLEASE DO NOT USE THIS DOCUMENT ********
********* UNTIL THIS MESSAGE IS REMOVED *********

1. INTRODUCTION AND INITIAL STEPS

  • Maintenance personnel or Telesis system programmers can interface with the Telesis system to determine the system`s overall status, to program the system, to collect records, etc.
  • Required Software in the PC is a WEB browser for programming and Telesis XTools Software Utility for record collection, reporting, and monitoring.
  • Telesis XTools is a freeware utility and its latest version may be downloaded from http ://wiki.telesis-pbx.com or http ://www.telesis-pbx.com sites.
  • This document aims novice Telesis system programmers to become familiar with system programming.

1.1. PHYSICAL CONNECTION

  • Telesis systems do not get IP addresses automatically from the network.
  • Since you may not change your network structure or parameters for any reason, you may need a direct ethernet connection to the system to adjust its basic ethernet settings according to your requirements.
  • Download and install XTools Utility. Read readme.txt file within the downloaded zip file for easy installation.
  • Interconnect your PC and Telesis system with using a cross-connected ethernet cable.
  • Be sure that only the ethernet interface, which is directly connected to the Telesis system is enabled in your PC. If there are any other interfaces (like wi-fi), disable them.
  • Run Xtools Utility.
  • Run Xymphony Discover function in Xtools Utility.
  • The discovery function should pop up the discovered Telesis system with its IP address.
  • The factory default IP address of a Telesis system is 10.0.0.12
  • If you can not success to discover Telesis system, check again network parameters in your PC, and use Scan function in XTools Utility.
  • If the IP address of the discovered Telesis system is not with the default IP address, it is advised to restart the system with factory defaults.
  • The procedure for restarting Telesis system with factory defaults may differ depending on the system model and its revision. In Telesis WiKi site (http ://wiki.telesis-pbx.com, read the procedure applicable for your system. You may use Search function in wiki to find the content easily.

1.2. HOME PAGE

  • Be aware that the root directory (or homepage) of the domain name (or IP address) of the Telesis system is the WebPhone service page.
  • The root directory (that is http ://10.0.0.12 or http ://10.0.0.12/home.asp by default) results in either
    • an error page for Telesis systems, which are not licensed or activated for the WebPhone service, or
    • webphone page for Telesis systems, which are licensed or activated for the WePhone service.
  • Note that Telesis WebPhone is a SIP softphone or client applet hosted in Telesis systems. The applet can be run from any java enabled web browser. A web browser, a microphone, and a headset are sufficient to make calls. Consequently, this service is for telephony not for system programming.
  • Note that, in PX24N Nano systems, webphone page displays a button for click to call Nano itself (by default its access code is 10). For the first call, and testing, just try to call.

1.3. MAIN PAGE FOR PROGRAMMING

  • Main page for programming is xp.asp page in the root of the domain name (or IP address) of the Telesis system (that is http ://10.0.0.12/xp.asp by default).
  • This page be either accessed with your a web browser or XTools Expert Setup Function (in fact, that function opens a web browser within the XTools Utility.

1.3.1. FIRST ACCESS TO PROGRAMMING PAGES

  • Be sure that Telesis system is accessible over IP.
  • Use a web server on your computer access to the main programming page (that is http ://10.0.0.12/xp.asp by default) or use XTools Expert Setup Function.
  • At the first connection with factory defaults, you are asked to define a strong password as an admin. Do this as mentioned below.

1.3.2. DEFINE A STRONG PASSWORD

  • Strong password selection is essential for the admin.
  • With using Ethernet paragraph WebServer link, admin Login ID and Password should be defined for the admin account to activate all web pages.
  • While defining the account, the password is typed in Password re-enter field same as the one typed in Password field. Strong password selection is essential for the security of Xymphony. It must be at least 8 characters, maximum length is 15. At least one upper case, one lower case and one numeric character should be present. Valid character set is "ABCDEFGHIJKLMNOPQRSTUVWXYZabcdefghijklmnopqrstuvwxyz0123456789+/" Consecutive 3 characters should not be selected as incrementing or decrementing the previous character. i.e sequences of "234" or "dcb" are not accepted.
  • Click on WebServer.
  • Define a Login ID and Password, password should be at least 8 character, click OK button.
  • After editing the fields, pressing OK restarts the web server.
  • If Random button is pressed, a strong password is recommended by Xymphony.
  • Continue with programming after accessing to the system with the strong password.

1.3.3. ADJUSTING BASIC ETHERNET PARAMETERS

  • Basic ethernet properties of a Telesis system can be programmed with using Basic link in Ethernet paragraph .
  • The factory default values of some basic ethernet properties are:
    • IP address: 10.0.0.12
    • Subnet mask: 255.255.255.0
    • Default gateway: 10.0.0.138
  • When OK button is clicked on, modified parameters are stored into volatile memories but they are not activated. In order to activate new parameters, these should to stored into nonvolatile memories and then the system should be restarted again. To do this, first operate Save command in System paragraph, and then operate Reboot command in Control Program paragraph.
  • After setting up new parameters(according to your network configuration), you may disconnect direct ethernet connection between your PC and Telesis system, and connect Telesis system to your local area network.

2. HELP DOCUMENTS

2.1. ONLINE HELP DOCUMENTS

  • All online help documents are prepared to help system installers and users to guide about programming TELESIS systems and usage of some services and features.
  • Online help documents are accessible by clicking on the help icon in programming pages.
  • All links in help pages are for another help page of a related topic. If programming page of that help topic is available, you can click on the programming icon within a help page.
  • Online help documents are embedded into Xymphony and available after establishing a connection to a Telesis system.
  • Online help documents are in English language.

2.2. BRIEF HARDWARE INFORMATION

  • Brief hardware information about your Telesis system can be accessed with using Hardware link in Help paragraph.
  • Hardware pages may look like below.
  • Note that complete and detailed hardware information about your Telesis system is always available in Telesis WiKi pages.

2.3. XYMPHONY RELEASE NOTES

  • Firmware (that is Xymphony) history of your Telesis system can be accessed with using Release Notes link in Status paragraph.
  • Firmware history page may look like below.

SIP PROGRAMMING

SIP UDP SIGNALING PORT

  • By factory default, SIP UDP signaling port is 5060, which is the well known port number stated in RFC documents. Changing this number may cause some routing equipment fail to deliver messages properly.
  • However, if desired, SIP UDP signaling port can be modified to another. To do this, click on SIP link in Homepage Ethernet paragraph. The SIP link opens SIP voip settings page. Edit the Sip UDP Signalling port textbox for the desired port number and then click on OK button. Be aware that when OK button is clicked in SIP voip settings page, modified parameters are stored into volatile memories but they are not activated. In order to activate the new parameters, these should to stored into nonvolatile memories and then the system should be restarted again.
  • If there are public (outside) SIP users, NAT should be programmed such that the UDP port (set in SIP voip settings page) is forwarded to the IP address of the Telesis system.

OTHER SIP BASIC SETTINGS

  • Basic settings for Session Initiation Protocol can be programmed with using Sip link in Homepage Ethernet paragraph. The Sip link opens SIP voip settings page.
  • Default value of Signalling port ToS is hex B8, which is suitable for most networks. Before modifying this parameter, consult your network administrator.
  • Unfortunately, there are numerous SIP devices in the market, which are sending SIP signaling packets with incorrect checksums. When Ignore checksum in signalling checkbox is marked, Telesis system ignores the checksum in received SIP signaling packets. If you notice incorrect checksums in received SIP signaling packets, mark this checkbox. Otherwise, leave it unmarked.
  • When OK button is clicked on, the parameters are stored into volatile memories but they are not activated. In order to activate the modified parameters, these should to stored into nonvolatile memories and then the system should be restarted again. To do this, first operate Save command in Homepage System paragraph and then operate Reboot command in Homepage Control Program paragraph.

SIP USERS BEHIND A NAT

  • Usually, configuring the NAT does not need much experience. However, some NATs may not initiate bindings for some SIP messages or they may not perform binding well. It is a complication, which will appear especially for end to end SIP VoIP communication, if the messages containing the private address are routed to the public domain. When the remote endpoint receives the private address, it will attempt to transmit to this address and the connection will fail since these addresses are un-routable in the public domain. As a result the performance the NAT equipment limits the overall performance of the operation.
  • If the Telesis system is operating behind a NAT equipment with bindings but the NAT equipment fails to translate declared IP addresses in SIP messages sent, then Declare external IP address checkbox should be marked in in SIP voip settings page.
  • In such case, the Telesis system discovers the public address and declares the source IP address as this one when signaling with non local peer entities. To have proper operation, DNS server IP address in Basic Ethernet settings page should also be set.

SIP MEDIA SETTINGS

  • Some parameters for VoIP codecs and media (like transmit and receive frame lengths, QoS, media jitter buffer) are adjustable in Telesis systems. These parameters are common for both SIP and H.323 VoIP calls.
  • The parameters can be programmed with using the Media link in Homepage Ethernet paragraph. The Media link opens Voip media settings page.
  • Telesis systems have integrated media proxies. This integrated media proxy:
    • receives RTP packets from the originating side,
    • decodes (i.e., converts) received RTP packets to PCM linear codes,
    • switches linear codes within the integrated PCM switch,
    • encodes linear codes according to the requirement of the destination, and
    • transmits RTP packets to the destination.
  • Never: Telesis system always does the media transport direct for the calls of similar VoIP entities.
  • Inside-Outside: Telesis system does the media transport direct for the calls of similar VoIP entities residing in the inside (private) IP address span. However, if one VoIP entity is in the inside and the other entity is in outside (public) IP address span, then Telesis system does the media transport through the integrated media proxy.
  • Always: Telesis system always does the media transport through the integrated media proxy for the calls of similar VoIP entities.
  • It is recommended to leave Media proxy type as the default one (Never) unless you really know what you are doing. Be aware that; just like VoIP to TDM calls, media proxied VoIP calls also require IP-to-TDM license for both VoIP parties. Consequently, unnecessarily setting Media proxy type to Inside-Outside or Always will require more number licenses than the actually needed number.
  • For G.711, G723, and G729 codecs, various transmit and receive parameters are adjustable in Voip media settings page.
  • ToS (Type of Service) and Differentiated services is a quality of service (Qos) protocol that prioritizes IP voice (RTP payload) and data traffic to help preserve voice quality even when network traffic is heavy. If Qos value of network devices is written in RTP ToS-Diffservices textbox, the system transmits this differentiated services value inside the RTP Payload messages. Consult your network administrator to learn if this protocol is supported by your network. If so, which value is to be used. For most networks Hex B8 is the proper value.
  • Telesis systems are equipped with an internal jitter buffer to correct transmission jitter in RTP media packets. The length of this Media jitter buffer is adjustable. By default, it is 100 milliseconds. Decreasing this value reduces reception delay but depending the load of the network, reception may be discontinuous. Leave this at the default value unless you really know what you are doing.
  • When OK button is clicked on, the parameters are stored into volatile memories but they are not activated. In order to activate the modified parameters, these should to stored into nonvolatile memories and then the system should be restarted again. To do this, first operate Save command in Homepage System paragraph, and then operate Reboot command in Homepage Control Program paragraph.

ADDING A SIP USER

  • Click Sip in Users paragraph.
  • Click Add button.
  • Define an Account for the SIP user then click OK button. Meanwhile system generates an access code automatically (like 1498) for the SIP user. You may change it if you wish.
  • Click Common button of the SIP user.
  • In Common Properties page, define a Password, select Local from registrar list box, and set the Authentication id and then click OK button
  • Again, in Common Properties page, select Security Authentication then click OK button
  • Again, in Common Properties page, mark Any IP can authenticate then click OK button.
  • If SIP phone registers to system you should see La sign in Status column.
Print - Recent Changes - Search
Page last modified on March 14, 2013, at 03:11 AM EST
Subject to change without any notice. All rights reserved 2010 - Telesis A.S.
Iskitler Cad. No.68 Ankara, TURKEY. Tel: +90 312 3840540 Fax: +90 312 3840549 http://www.telesis-pbx.com