1 / 36

Teles configuration

Teles configuration. VoIPBOX 4 BRI ports (2NT & 2TE OR 0TE & 4 NT) 8 VoIP media channels VoIPBOX PRI (1U) 1 to 6 PRI lines Up to 180 VoIP media channels. Product variants . Mobile gateways (TELES.iGATE) Mobile interfaces 4/8/16/32 - 600 (GSM, CDMA, 3G/UMTS) PRI / ISDN interfaces

jeroen
Download Presentation

Teles configuration

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. Teles configuration • VoIPBOX • 4 BRI ports (2NT & 2TE OR 0TE & 4 NT) • 8 VoIP media channels • VoIPBOX PRI (1U) • 1 to 6 PRI lines • Up to 180 VoIP media channels

  2. Product variants • Mobile gateways (TELES.iGATE) • Mobile interfaces • 4/8/16/32 - 600 (GSM, CDMA, 3G/UMTS) • PRI / ISDN interfaces • 1/2 - 6 x E1 • VoIP channels • 8/16/32 - 180 x VoIP channels • IP • 2 x Ethernet 10/100 Base-T

  3. Product variants • TELES.VoIPBOX GSM • Mobile interfaces • 4 x GSM or CDMA • Analog interfaces • 4 x FXS • VoIP channels • 8 VoIP channels • IP • 2 x Ethernet 10/100 Base-T • PPP support via GPRS*, CDMA2000 * Roadmap

  4. General features • Number Portability • Callback / SMS Callback • SNTP client • IP router over xDSL (PPPoE) and ISDN • vLAN routing • Bandwidth control (VoIP priority / dynamic codec fallback) • Firewall functionality • NAT, PAT • Http User Interface • DNS Forwarder • Ipupdate (e.g. DynDNS)

  5. VoIP features • Signaling: SIP (RFC 3261), H.323 (v4) – working in parallel • Voice Codecs: G.729, G.723.1, G.711, G.726, G.728, GSM, iLBC • DATA: clear channel (RFC 4040), gnx64, ccd (RFC3108) • DTMF Tone: outband: RFC 2833, SIP Info (RFC 2976) / H.323 Info or inband • Fax: T.38 or inband • Multiple Gatekeeper support H225 (v4) or/and Multiple Registrar support • Radius AAA; Authentication and CDR (RFC2835) • STUN client (RFC3489) (usable for SIP and H.323) • ENUM client (RFC3764, RFC3824) • Silence suppression (VAD / CNG) • Echo cancellation G.168-2000 • RTP multiplex bandwidth reduction • Ring tone generation • Configurable TOS (Type of Service) / DiffServ (Differentiated Services)

  6. iGATE and VoIPBOX GSM Features • LCR engine: Use the best rate out of mobile, PSTN, and VoIP • Selective routing by destination or time • Generation of AOC (Advice of Charge) • Multilevel alternative routing (voice/data/fax) • Digit collection • Black list, White list • Alert/Busy/Announcement tone detection – generates proper signaling • Online traffic statistics and CDR • Direct line (two-stage-dialing) & Callback server • E-Mail to SMS conversion • SNMP • 2 Ethernet interfaces

  7. iGATE • Reduce costs for fixed-to-mobile calls • Different SIM contracts per channel (1 to [n] SIMs) • Integrated SIM server support • Integrated VoIP gateway • Powerful least cost routing • Callback-server functionality • Fixed network backup via mobile • TELES.NMS network-management software

  8. iGATE • Corporate-user benefits • Gain access to PSTN and Internet where you have limited or no wire connection • Simple and fast set up (no change at customer’s site) • Cost-effective voice & data • Enhanced voice services and additional extensions • Mobile-operator benefits • Use existing GSM, CDMA, or 3G infrastructures to connect corporate users • Enhance product portfolio: Fixed lines & broadband Internet access • Greater customer base (SMEs) and additional air time! • Customer retention

  9. Configuration

  10. Remote access overview Access to the system and configuration • Initial configuration with “Quickstart” • LAN access (TCP/IP) • Remote access software “GATE Manager” via • TCP/IP • ISDN Data call • CDMA/UMTS (connection initiated by Access Gateway) • Remote access via HTTP User Interface • LAN / WAN access (TCP/IP) • Remote access via FTP / Telnet • LAN / WAN access (TCP/IP) • NMSSelf provisioning NMS (optional)

  11. Configuration | Initial Startup with TELES.Quickstart • Install Quickstart on your computer or run it from CD • Configure network settings for the system: • IP address • Sub net mask • default gateway • NTP server address and timezone(sets the system time!!) • Click “Next” and/or “Finish” • Access to the system nowvia TELES.GATE Manager • For VoIPBOX BRI there is a wizard that configure: • line interfaces • routing entries

  12. Configuration | GATE Manager • For remote maintenance of single network elements, you can start the GATE Manager application directly from your desktop.

  13. Configuration | Web interface • Default settings are: • IP: 192.168.1.2 • Mask: 255.255.255.0 • Access the system via HTTP- Three levels of access:Read-only accessRights to change IP settingsAll rights

  14. Configuration | FTP interface • Access the system via FTP • Change directory to /boot • Download ip.cfg file andchange it according toyour needs

  15. Configuration | Self provisioning NMS • Zero touch installation for the end customer • Automatic customized creation of the individual configuration files • Input of customer data from the order processing data base to the NMS • First contact configuration of VoIP settings and line interfaces operational customer activated box shipped necessary input for generating configuration box configuration

  16. Configuration | Configuration files (Overview) The 3 configuration files are: • Ip.cfg • Basic configuration of the Ethernet interface(s) • Pabx.cfg • System-specific and port-specific settings • Route.cfg • Routing entries

  17. Configuration | Ethernet Ports Config (ip.cfg) • Basic settings for the Ethernet interfaces (IP address / mask / DGW)Same as on the QuikStart • Different scenarios for the second interface • HUB mode • DSL router • vLAN router • Firewall / NAT firewall • DHCP server • IP router over ISDN Dialup • Bandwidth Control (VoIP priority) Example (default): [System] DefaultGw=192.168.1.1 [emac0] IpAddress=192.168.1.2/24

  18. Configuration | System Config (pabx.cfg) System-specific settings and the port configuration: • Bypass relay (Life line) • Log files • Night configuration (time-dependent routing and SIM switching) • Controllers (defines the parameters that apply to the ports) • Subscribers (features for each port) • Global settings: • Number portability settings • SNMP configuration (runs as optional function module) • VoIP basics • DNS Server settings • NTP Server settings • Remote access settings • SIM Server settings • STUN client

  19. Configuration | System Config (pabx.cfg) Default ... Controller00=9 TES2M DSS1 CRC4 Controller01=10 NTS2M DSS1 CRC4 This configures port 00 as TE, ports 01 as NT, CRC4 is on Controller02=40 VoIP ... Subscriber00=TRANSPARENT ROUTER ALARM Subscriber01=TRANSPARENT ROUTER ALARM Subscriber02=TRANSPARENT ROUTER CHMAX[16] ALARM ... CHMAX[16] Defines the number of channels per G.729 module â

  20. Configuration | VoIP Settings (pabx.cfg, optional) • Global VoIP Settings (Telephony Routing / VoIP Carrier) VoipGlobalMaxChan=30 Maximum VoIP channels for the system H225Port=1720 H.323 signalling port SipPort=5060 SIP signalling port VoipRtpPort=29000 Starting UDP port for RTP (RTCP uses the next port) VoipRtpPortSpacing=2 Space between 2 RTP streams (2 is minimum)

  21. Configuration | Example (HTTP User Interface) • HTTP User Interface (Port Settings)

  22. Configuration | Routing Functions (route.cfg) • Routing commands:- MapAll With these entry we rout calls between the ports.- Restrict This entry applies only for a single controller - Redirect This entry will reroute the call in case of connection failure The order of the mapping is: 1. From top to bottom 2. More specific to more global. Example: MapAll00=90111100 MapAll0170=262010170 MapAll0172=262020172 MapAll00=90111100 MapAll0=9022220

  23. Configuration | Routing Functions (route.cfg) • Controller specific routing entries Restrict<port><num>=<pl> MapAll<pl>=<port><dest> This entry applies only for a single controller or in addition to complete or partial OAD, the DAD is searched in the second step and follows the known rules. Example: Restrict40=pl Restrict10=lp MapAllpl=10 MapAlllp=40DF:

  24. Configuration | Routing Functions (route.cfg) • Alternative RoutingRedirect3<nr>=<pl>MapAll<pl>=<port><dest> This entry will send a call with the number <nr> to another port (e.g. PRI) in case of connection setup failures. Note: This configuration could cause longer post-dial delays! Example: MapAll0172=#262020172 Redirect326202=pl MapAllpl=9

  25. Configuration | Routing Functions (route.cfg) • Routing entry to a VoIP peerMapAll<nr>=<port><voip profile>:<dest> This entry contains the name of a VoIP profile, that include all parametersto establish a connection to the peer. Example: MapAll00=40DF:00

  26. Configuration | Routing Functions (route.cfg) • Digit collection DTMFWaitDial=<sec>MapAll<nr>=|<port><dest><<<count> This entry collects up to 15 digits (including ‘262020172’). If a “sending complete” is received, a timeout occurs (in this case 5 seconds) or the number of digits is reached (here 15 digits) the call will be placed at the defined port / trunk group. Example: DTMFWaitDial=5 MapAll0172=|262020172<<15 • Calling party number suppression - CLIR (block outgoing CLI) MapAll<nr>=#<port><dest> A hash (#) at the beginning of the destination number causes the call to be sent with the flag “calling party number suppression”.Default

  27. Configuration | Routing Functions (route.cfg) • Definition of VoIP profiles • Necessary settings for communication with the VoIP peer [Voip:<name>]Name of the routing profile VoipDirection:<mode>The permitted call direction (In, Out, IO) VoipPeerAddress:<addr>The peer’s Name or IP address VoipIpMask:<mask>The peer’s network range (for incoming calls) VoipSignalling:<int>The signaling protocol used (H.323, SIP) VoipCompression:<list>The compression to be used, in order of preference (G.729, G.729 a G.729b G.729ab G.726-16, G.726.24, G.726-32, G.728, G.711a, G.711u, GSM, G.723.16.3 G.723.1.5.3, iLBC20, iLBC30,T.38 Fax) VoipMaxChan:<num>Max. channels used for profileVoipTxM:<num>The multiplication factor (1–12) for the frame size calculation of the RTP packet (default: 10ms).

  28. Configuration | Routing Functions (route.cfg) • Definition of VoIP profiles management parameters VoipUser:<user> User name (SIPonly) VoipPwd:<pwd> Password (SIPonly) VoipRegistrar:<name> Registrar profile used for the profile VoipGk:<list> Name(s) of the assigned Gatekeeper profile(s) VoipProxy:<name or addr> SIP Serverused VoipRadiusAuthenticate:<name> Name of the assigned RADIUS server VoipRadiusAccounting:<name> Name of the assigned RADIUS server (RADIUS is currently in development and will be implemented soon)

  29. Configuration | Routing Functions (route.cfg) • Definition of VoIP profiles with the HTTP user interface

  30. Configuration | Routing Functions (route.cfg) • Gatekeeper profile(s) [Gatekeeper:<name>] Name of the Gatekeeper profile GkAdd:<addr> The Gatekeeper's IP address GkId:<name> The Gatekeeper's ID GkPwd:<name> Password to log onto the Gk RasId:<name> The ID used for gatekeeper registration RasPrefix:list Prefixesused GkTtl:<num> Time to live for registration validity (sec.) (recommendation) GkMaxChan:<num> Max. channels used for this Gatekeeper

  31. Configuration | Routing Functions (route.cfg) • Registrar profile(s) [Registrar:<name>] Name of the Registrar profile RegId:<name or addr> Name used in the reg. request header RegUser:<name> Username RegPwd:<password> Password RegProxy:<name or addr> Server used RegOwnId:<name or addr> Used in the from field RegContact:<name or addr> Used in the contact field

  32. Configuration | Routing Functions (route.cfg) • RADIUS profile [Radius:<name>] Name of the RADIUS profile Host:<name or addr> Name or IP of the RADIUS server User:<name Username Pwd:<pwd> Password Secret:<secret> Secret OwnId:<name or addr> Used in the NAS identifier or NAS IP address ServiceType:<num> As RFC 2865 chapter 5.6 FramedProtocol:<num> As RFC 2865 chapter 5.7 RadiusRequestTimeout:<sec>Repeat timeout if the server does not respond RadiusRequestRetries:<count> Number of packet retries at one time

  33. Configuration | Routing Functions (route.cfg) • Setting national/international flag (TON = type of number) ÚIt might be necessary in some cases to transmit the calling and/or called party number with the flag instead of the leading “0(s)”: OAD Restrict<port>0=n 15 Restrict<port>00=i 15 DAD MapAll00<num>=<port>i<num> MapAll0<num>=<port>n<num> • TON unknown (u) or subscriber (s) can also be set, “s” might be necessary for some ISDN PBXses • Rejection of data calls and special numbers MapAll<num>=&<cau> DATAMapAll<num>=&<cau> VOICE All calls (DATA: data calls; VOICE: voice calls) starting with <num> will be rejected with the cause value <cau>.

  34. Licenses • iGATE CDR option: Allows for CDR storage on the system. Enables Online Statistics (ASR, ACD, number of calls …) • iGATE DDI and intelligent call back: Enables two-stage-dialing and call. back • iGATE SMS gateway package: enables e-mail to SMS conversion and vice versa. • iGATE ported number screening: Enables online query to iMNP or external provider (nQuire / End2End) • iGATE SS7 Extension: License for SS7 (Q.767); each SS7 related PRI (regardless whether link or trunk) requires a license

  35. Questions? http://www.teles-communication-systems.com Thank you for your attention!

More Related