TELES Basic technical training

Gateway Exercises

Eyal Shmueli TELES 2008

Page 1 of 16

The following exercises will go through the installation and configuration of a TELES VoIPBOX GSM 4 FX and VoIP BOX BRI.

The equipment in hand: 1. VoIP BOX GSM 4 FX. 2. VoIP BOX BRI 3. BRI phones 4. Analog phones 5. SIP server.

1 Installation and IP address Configuration

Install TELES Gate Manager and TELES Quickstart on your PC. Connect the VoIPBOX to Eth port 1, and PC to the LAN. Insert SIM card(s) and connect analog phones or PBX to FXS ports. Plug in and power on device. Wait 2-3 minutes for boot to complete. Run the TELES QuickStart application. QuickStart will search the network for TELES devices. Any systems found will be displayed with their TAG serial number.

Right click on any system to define the systems IP address information. Click next and follow the instruction on screen the system will write this information to the configuration files and restart. Your system is now ready for remote access. And basic routing operation. NOTE: The Quickstart application is best suited for accessing and doing basic configuration on TELES devices where the IP address is unknown. QuickStart will find the Teles device on the LAN and then take you through a wizard
Page 2 of 16

TELES 2008

for basic configuration. If the IP address is known (default is 192.168.1.2) then the Gateway can be accessed using the Web GUI by visiting the IP addresses in your browser or Gate Manger. QuickStart wizard only available on the VoIP BOX family GW.

TELES 2008

Page 3 of 16

2 Options for Remote Access Configuration

Gate Manager
After the Gate Manager application has been installed on the PC it can be used to connect to any TELES system. Gate Manager can be used to access configuration files, view port status, connected calls, statistics and more. - Right click left side of the screen (white area) and choose new group -> enter the new group name. - Left click the new group and then right click the right side of the screen (Grey area) and choose new system -> enter a system name, under remote number enter the GW IP address. Note before entering the IP address you need to enter IP:

HTTP Interface
The web GUI is a user-friendly alternative to text files for gateway configuration. Basic configuration can be done from the web GUI, but more advanced parameters may require direct modification of the text-based configuration files. Enter the VoIPBOXs IP address in the browser address bar. o Username: teles-carrier o Password: tcs-carrier

TELES 2008

Page 4 of 16

3 Configure Gateway Port Information

After logging in to the web interface go to System Settings Port Settings o Choose Phones Directly Connected and enter phone extension numbers o All other parameters may be left default o Corresponding entries in the pabx.cfg file:
Controller00=10 Controller01=11 Controller02=12 Controller03=13 ANA ANA ANA ANA

Subscriber00=TRANSPARENT ROUTER ANA[0001,16,800,250,1500,80,0,1,2,5000,1050 0,5000,0];FXSEXTNO=212 Subscriber01=TRANSPARENT ROUTER ANA[0001,16,800,250,1500,80,0,1,2,5000,1050 0,5000,0];FXSEXTNO=213

TELES 2008

Page 5 of 16

Subscriber02=TRANSPARENT ROUTER ANA[0001,16,800,250,1500,80,0,1,2,5000,1050 0,5000,0];FXSEXTNO=214 Subscriber03=TRANSPARENT ROUTER ANA[0001,16,800,250,1500,80,0,1,2,5000,1050 0,5000,0];FXSEXTNO=215

Configure necessary GSM port information (Frequency band, PIN) o Corresponding entries in the pabx.cfg file:
Controller04=20 Controller05=21 Controller06=22 Controller07=23 GSM GSM GSM GSM

Subscriber04=TRANSPARENT ROUTER GSM[0000,00000,+000000,1,1,1,SIMS,IMSI,BAND (5)] ALARM NEXT Subscriber05=TRANSPARENT ROUTER GSM[0000,00000,+000000,1,1,1,SIMS,IMSI,BAND (5)] ALARM Subscriber06=TRANSPARENT ROUTER GSM[0000,00000,+000000,1,1,1,SIMS,IMSI,BAND (5)] ALARM Subscriber07=TRANSPARENT ROUTER GSM[0000,00000,+000000,1,1,1,SIMS,IMSI,BAND (5)] ALARM * Do you use CHADDR?

4 Configure SIP Trunk Profile

Go to VoIP Settings Main Settings o Verify settings in this section

Corresponding entries in the pabx.cfg file:

VoipGlobalMaxChan=4 H225Port=1720 SipPort=5060 VoipRtpPort=29000 VoipRtpPortSpacing=2 VoipStrictRfc3261=yes

TELES 2008

Page 6 of 16

 Note: The following default system parameters will

also be found in the pabx.cfg:
FtpPort=21 TelnetdPort=23 Ftpd=on Tftpd=off Telnetd=on MoipPort=4445

The following system parameters are recommended

additions to the pabx.cfg
NameServer= ; (Primary DNS, necessary later for Bandtel SIP Trunk config) NameServer= ; (Secondary DNS, necessary later for Bandtel SIP Trunk config) Timezone= ; (defined in Quickstart) NtpServer= ; (defined in Quickstart) SimCtrlUnitAddress= ; (for vGate SIM Server use only) Moip2Port=4446 ; (for vGate SIM Server use only) Dialtone=US

Go to VoIP Settings SIP Profiles o Add a new Registrar Profile for SIP registration

Click details and set Registration Ping =30 and Registration Expiry=120 Click Submit Corresponding entries in the route.cfg file:
[Registrar:BTEL] RegId=proxyx.bandtel.com RegUser=2086500002 RegPwd=telesusa RegExpires=120 RegPing=30

Add a new VoIP Profile with BandTel account information and click Submit

Click details Choose codecs G.729 and G.711u, with Frame size 2 for each Change VoIPMediaWaitForConnect to tone Change VoipDtmfTransport to RFC2833
Page 7 of 16

TELES 2008

VoipRFCPayloadType to 101 Add Public IP to From Field in Signaling Parameters Click Submit Corresponding entries in the route.cfg file:
[Voip:BT] VoipDirection=IO VoipPeerAddress=proxyx.bandtel.com VoipIpMask=0x00000000 VoipSignalling=1 VoipRegistrar=BTEL VoipOadSource=0 VoipDadSource=1 VoipPrack=no VoipOverlap=no VoipUser=2086500002 VoipPwd=telesusa VoipMaxChan=8 ;VoipTxM=2 2 VoipSilenceSuppression=no VoipIpLogging=no VoipUseStun=no VoipBandwidthRestriction=no VoipCompression=g729 g711u VoipMediaWaitForConnect=tone VoipFaxTransport=1 VoipFaxBypassPayloadType=102 VoipFaxMaxRate=3 VoipFaxECM=no VoipV21Transport=0 VoipV22Transport=0 VoipV23Transport=0 VoipV32Transport=0 VoipV34Transport=0 VoipIBSDetectDir=0 VoipDtmfTransport=3 VoipRFC2833PayloadType=101 VoipOwnIPAddress=

Activate Configuration

5 routes configuration
Routing per prefix On the left side of the = sign is the incoming/dialed prefix on the right side of = is the port/LAIN number & the prefix of the number to dial. routing to GSM port: using port number MapAll123=20123 using LAIN number MapAll123=10005123 routing to fix line port: MapAll123=9123 routing to VoIP:
Page 8 of 16

TELES 2008

MapAll123=40DF:123 (DF: is the VoIP profile name) Digit collection: MapAll123=|20123<<12 15 is the number or digits to collect, the number is calculate from the number of digits to dial + the number of digits of the port number. For example if a mobile number have 10 digits and the port number is 2 (two digits) the number for the digit collection will be 12 Hiding the CLI: MapAll123=#20123 Adding the # sign will hide the CLI of the caller.

Routing per port

All incoming traffic from VoIP (40), PSTN (9) & GSM (20) are routed to PBX (10) On the left side of the = sign is the port number where the traffic is coming from on the right side of = is place holder (IN) Restrict40=IN Restrict9=IN Restrict20=IN On the left side of the = sign is the place holder (IN) on the right side of = is the port that received the call MapAllIN=10

Redirect of a call We can redirect a call in one of the following cases:

2 call forwarding no answer. 3 call forwarding when busy 5 call forwarding when busy and no answer MapAll123=|204<<15 Redirects GSM to PRI if all GSM cards are busy Redirect304=a MapAlla=94

TELES 2008

Page 9 of 16

Exercises
1. Outbound from FXS to GSM.
Adding digit collection. Number manipulation. Inbound from GSM to FXS. 2. connect VB BRI with VB GSM Outbound from BRI to GSM. Inbound from GSM to BRI. 3. Inter connect all BRI GWs in the room. 4. Centralized break out. 5. Register a SIP phone on VoIP BOX GSM FX and make inbound & out bound calls. 6. SIP trunk Register the GW on a SIP server*.

1. Outbound from FXS to GSM

Add new route: set mobile prefix and route the call to GSM over port 20. MapAll0172=200172 Is it working try to add digit collection MapALll0172=|200172<<15 Now try to add number manipulation (replacing mobile prefix, international prefix) MapAll123=|200172<<15 Corresponding rules on the WEB GUI:

Submit -> Activate configuration.

TELES 2008 Page 10 of 16

Inbound from GSM to FXS Add new route: On section 3 we define the extension number of each analog phone (for example port 1 ext is 211, port 2 ext is 212). Restrict20=pl MapAllpl=10211 Restrict21=pm MapAllpm=11212

Corresponding rules on the WEB GUI:

Submit -> Activate configuration.

2. Connect VoIP BOX BRI to VoIP BOX GSM FX

Open a VoIP profile on each GW.
[Voip:ToBRI] VoipDirection=IO VoipPeerAddress=XXX.XXX.XXX.XXX VoipIpMask=0xffffffff VoipSignalling=1 VoipMaxChan=8 VoipTxM=2 2 VoipSilenceSuppression=no VoipCompression=g729 g711u VoipMediaWaitForConnect=tone VoipDtmfTransport=3 VoipRFC2833PayloadType=101
TELES 2008 Page 11 of 16

Add a corresponding MapAll MapAll123=40ToBRI:123 Corresponding rules on the WEB GUI:

Submit -> Activate configuration. Complete: Outbound BRI->GSM: MapAll0172=40ToBRi:0172 Inbound GSM->BRI: MapAll200=10200 (200 is the BRI phone on port 10)

3. Inter connect all GWs in the room. 4. Centralized break out.

5. Register a SIP phone

Open a VoIP profile suitable for registration on the GW. [Voip=AAA] VoipDirection=IO VoipOwnUser=500 VoipOwnPwd=500 VoipExpires=30 VoipAuth=www VoipCompression=g711a VoipSilenceSuppression=No VoipSignalling=1 VoipAutoRtpAddr=Yes VoipDtmfTransport=3 VoipRFC2833PayloadType=101 VoipTxm=2 Add a corresponding route to the profile and complete inbound & outbound calls.

6. SIP trunk/SIP extension Register the GW on a SIP server

From the point of view of the IP-PBX, analog phones plugged into the TELES VoIPBOX will appear the same as SIP phones. The VoIPBOX will be configured to SIP register to the IP-PBX just like IP phones. Routing on the VoIPBOX will then send the calls to the proper analog FXS port.

TELES 2008

Add SIP extensions to IP-PBX for TELES analog extensions

Page 12 of 16

Create a Registrar profile for the IP-PBX

o Click details and set Registration Expiry=300

o o Click Submit Corresponding entries in the route.cfg file:
[Registrar:IPBX] RegId=192.168.1.2 RegUser=1003 RegPwd=12345 RegProxy=192.168.1.2 RegExpires=300

Create a VoIP profile for the IP-PBX o Add a new VoIP Profile with the IP-PBX account information, for the corresponding IP-PBX registrar and click Submit

Click details Choose codecs G.729 and G.711u, with Frame size 2 for each Change VoIPMediaWaitForConnect to tone Change VoipDtmfTransport to RFC2833 VoipRFCPayloadType to 101 Click Submit Corresponding entries in the route.cfg file:
[Voip:IPX] VoipDirection=IO VoipPeerAddress=192.168.1.2 VoipIpMask=0xffffffff VoipSignalling=1 VoipRegistrar=IPBX VoipOadSource=0 VoipDadSource=0 VoipPrack=no VoipOverlap=no VoipUser=1003 VoipPwd=12345 VoipMaxChan=8 VoipTxM=2 2 VoipSilenceSuppression=no VoipIpLogging=no VoipUseStun=no VoipBandwidthRestriction=no

TELES 2008

Page 13 of 16

VoipCompression=g729 g711u t38 VoipMediaWaitForConnect=tone VoipFaxTransport=1 VoipFaxBypassPayloadType=102 VoipFaxMaxRate=5 VoipFaxECM=yes VoipV21Transport=0 VoipV22Transport=0 VoipV23Transport=0 VoipV32Transport=0 VoipV34Transport=0 VoipIBSDetectDir=0 VoipDtmfTransport=3 VoipRFC2833PayloadType=101

Create routing FX IP-PBX Go to System Settings Telephony Routing Advanced Mode o Create a new route for FXS ports to send IP-PBX extensions to IP-PBX VoIP Profile. Set prefix 10 to route to VoIP Profile IPBX with no translation.

Any call coming from any interface beginning with prefix 10 will be routed to controller 40IPBX: Click Submit Corresponding entry in the route.cfg file:
MapAll10=|40IPX:10<<24 all

Create a new route for inbound FXS calls from the IP-PBX extensions to IP-PBX VoIP Profile: set prefix 100x (whichever extension you were defined to route to FXS trunk 10 with no translation.

Any call coming from any interface beginning with prefix 100x will be routed to controller 10. Click Submit Corresponding entry in the route.cfg file: MapAll1003=|101003<<24 all

TELES 2008

Page 14 of 16

6 Common Troubleshooting Issues

One-way audio A one-way audio issue is typically a network/firewall issue, not a gateway issue. When implementing VoIP on a network, IP ports necessary for SIP signaling and RTP packets must be open to the gateway. Please see the TELES firewall document for a list of ports that are required to be open to the gateway. A second and less common reason for one-way audio is a loose connection within the TELES Gateway. Outbound to GSM fails o Digit collection, or Enbloc dialing, is necessary when sending calls to the GSM network. When digit collection is enabled, the gateway waits for the specified amount of digits (or until the DTMFWait period ends) before sending the complete number. If digit collection is not enabled, the gateway will send one digit at a time and the call will fail. o Routing issue Often a syntax error in the MapAll command, or use of the CHADDR command, can be a reason for failed calls. Software update To upgrade software for a TELES gateway, simple download the latest version for your device here o http://195.4.12.80/files/ Username free Password access From the Gate Manager Directory page, right click and choose send. Select all files provided in the downloaded .ZIP file. Allow up to 1 hour for all files to transfer. Restart gateway after file transfer completes. SIM cards dont register o The most likely possibility is that the Gateway is not configured to register the SIM on the carriers frequency. TO choose the correct frequency, add the BAND(x) parameter to the Subscriber line of the GSM controller in the pabx.cfg file. For example:
Subscriber01=TRANSPARENT ROUTER GSM[0000,00000,+00000,1,1,1,SIM4,IMS I,BAND(5)] CHADDR ALARM

Where x is: 1 = Mono-band mode 850MHz 2 = Mono-band mode 900MHz 3 = Mono-band mode 1800MHz 4 = Mono-band mode 1900MHz 5 = Dual-band mode 850/1900MHz 6 = Dual-band mode 900/1800MHz 7 = Dual-band mode 900/1900MHz
TELES 2008 Page 15 of 16

After changing the band settings, a restart of the gateway is required for the setting to take effect. o Another reason for SIM registration failure is poor antenna connection or poor GSM signal. Make sure that all antenna connections to the gateway are secure and that the gateway is in a location with ample GSM reception. It is also possible that there is a problem with the SIM. Perhaps the SIM is invalid, expired, out of credit etc. Om this case, contact the GSM carriers customer service, or replace the SIM.

7 Teles Trouble Ticket System

Upon purchasing TELES service agreement, you will be given login credentials to the Teles trouble ticket system at https://smon.teles.com/smon/servlet?cmd=loginUI

TELES 2008

Page 16 of 16