Telco Bridge System Architecture

839 views
652 views

Published on

Telco Bridge System Architecture technology

Published in: Technology, Business
0 Comments
0 Likes
Statistics
Notes
  • Be the first to comment

  • Be the first to like this

No Downloads
Views
Total views
839
On SlideShare
0
From Embeds
0
Number of Embeds
2
Actions
Shares
0
Downloads
18
Comments
0
Likes
0
Embeds 0
No embeds

No notes for slide

Telco Bridge System Architecture

  1. 1. System Architecture
  2. 2. System Configuration TMS1600 SS7 SS7 TMP6400-64 ISDN PRI TMP6400 ••• VOIP VOIP TMP6400-64 #1 #2 #16 GigaEth LanSwitch OAM
  3. 3. TMP6400-64 TmediaTM TMP6400 Series Base Unit • Compact 2U form factor • 4 X 100/1000Base-T ports • 2 x TmediaTM Switch ports • AC or DC power (redundant option) • SIP, SS7, ISDN Optional IVR – 1 slot • 128, 256, 384, 512, 1024, 1536, 2,048 channels • Play, record, conference, tones Optional TDM – 1 slot • 4, 8, 12, 16, 32, 64 T1/E1 • 1 to 3 DS3 + 2 T1/E1 • 1 OC3/STM-1 + 2 T1/E1 Optional VoIP – 4 slots • 128, 256, 384, 512 universal channels • Up to 2,048 channels per unit
  4. 4. TMP6400-64 TMP6400 Base Unit Number of slots Part Number 120/240 VAC TMP-6401-AC ✔ TMP-6401-DC TMP-6402-AC TMP-6402-DC -48 VDC PS redundancy VoIP IVR TDM 4 1 1 4 1 1 ✔ 4 1 1 ✔ 4 1 1 ✔ ✔ ✔ Dual Redundant LAN Ports • 100/1000Base-T for control • 100/100Base-T for VoIP Management Ports • 10/100/1000Base-T control port • RS232 serial console Power Supply Redundancy • Using TmediaTM RPP TmediaTM Switch Ports • Dual redundant 2 x RJ45F • Non-blocking up to 32,768 ch. • Development-free scalability
  5. 5. TMP6400-64 Optional VoIP Modules Universal Codecs Wireline Codecs Wireless Codecs G.711 G.723.1 G.726 G.729ab G.728 G.729e g iLBC T.38 AMR GSM-FR/ GSM-EFR EVRC/ QCELP TM-VOIP-1 404 128 216 154 66 84 84 100 84 84 60 TM-VOIP-2 808 256 432 308 132 168 168 200 168 168 120 TM-VOIP-3 1212 384 648 462 198 252 252 300 252 252 180 TM-VOIP-4 1616 512 864 616 264 336 336 400 336 336 240 Max. capacity 6464 2048 3456 2464 1056 1344 1344 1600 1344 1344 960 Part Number • • 4 x field-upgradeable slots 128 to 2048 universal codecs per TMP6400 • G.168-128 ms echo cancellation on all channels simultaneously • • In-band DTMF, RFC2833 and SIP INFO method Adaptive jitter buffers
  6. 6. TMP6400-64 Optional TDM Modules • • • • 1 x field-upgradeable slot 4 to 64 x T1/E1/J1 1, 2, or 3 DS3 1 OC3/STM-1 with APS Part Number T1/E1/J1 DS3 TM-TDM-4 4 TM-TDM-8-UPG 8 TM-TDM-16UPG 16 TM-TDM-32 32 TM-TDM-48 48 TM-TDM-64 64 TM-DS3-1 2* 1 TM-DS3-2-UPG 2* 2 TM-DS3-3-UPG 2* 3 TM-STM-1 2* OC3/STM-1 1 (w/APS) * for BITS synchronization and signaling
  7. 7. TMP6400-64 Optional IVR Modules • 1 x field-upgradeable slot • Play and record • DTMF detection, generation and suppression • Conferencing – 132 active participants per conference – Unlimited listeners Part Number Number of Channels TM-IVR-128 128 TM-IVR-256-UPG 256 TM-IVR-384-UPG 384 TM-IVR-512-UPG 512 TM-IVR-1024 1024 TM-IVR-1536 1536 TM-IVR-2048 2048 • Supports TB-StreamServer application – Up to 20,000 simultaneous audio streams per server
  8. 8. TMP6400-64 Optional Signaling Stacks • Signaling stacks run onboard • Multiple signaling protocols and variants simultaneously supported • Protocols and variants are dynamically added, deleted and changed • ToolpackTM API development tool provides access to IEs and SDPs Signaling Options SIP • RFC 3261 User Agent SS7 HA (20+ variants, contact us or details) • MTP2, MTP3, ISUP, SCCP, TCAP • Up to 64 SS7 links, up to 30,000 CICs • High-speed link supported ISDN (14+ variants) CAS (multiple variants) • R1, MFC-R2, wink start, FXS loop/ground start, FXO, Taiwan R1
  9. 9. TmediaTM Switch TMS1600 Series
  10. 10. TMS1600 TMS1600 System Features • Carrier Grade Architecture • SelfDiscovering for hardware additions & removals • Non-blocking 32768 channels switching • Development free, Plug & Play
  11. 11. TMS1600 TMS1600 System Features Interconnect up to 16 TmediaTM TMP6400 platforms to create a powerful and cost-effective telecom system > Any-to-any timeslot switching between 1,024 T1/E1/J1s, 48 DS3s or 16 OC3/STM-1s LAN Ports  Dual redundant 100/1000Base-T for control Management Ports  1000Base-T control port  RS-232 serial console (RJ45F) > Perfectly non-blocking up to 32,768 channels Tmedia Switch Ports > Carrier-grade redundant dual star architecture (for TMS redundancy)  Each interface supports 2,048 channels  16 High-speed interfaces (RJ45F)  Non-blocking switching between all channels  Interconnects up to 16 TMP6400 devices
  12. 12. Next …. Tmedia Web Portal Web Based OAM
  13. 13. Tmedia Web Portal  The Tmedia Web Portal is a Web-Based OAM&P tool that enables the user to easily configure a Tmedia system and to monitor its performance  The Web Portal, can be accessed from any computer using a standard web browser and is hosted by the Toolpack application server.  Using the OAM&P, the user defines - the physical hardware and its interfaces, - the signaling interfaces, - logical Network Access Points (NAP) with signaling types, such as: SIP, SS7, and ISDN
  14. 14. Procedure to configure system 1. 2. 3. 4. 5. 6. 7. 8. 9. 10. 11. 12. 13. Log In Start up the TMP6400 Toolpack app / verifying it is running. Add Tmedia units Configure a TMS Network Add line interfaces Create line services Configure system clocking Configure the ISDN signaling Configure SIP signaling Configure SS7 signaling Configure profiles Configure NAPs Configure Routing Module
  15. 15. Logon  To log on: 1.The HTTP port is set to 12358 by default during the installation process; HTTP://<server IP address>:12358 The log on screen is displayed 2. Enter your user name and password Click Login
  16. 16. Logoff  When you are finished working in the Web Portal, it is recommended that you log out from your session.  If you do not log out, the session between the Web Browser on your PC and the Web Portal remains active. To log out from the Web Portal: Select Logout from the navigation panel
  17. 17. Start up application / verifying running  To Verify that Application is running Select Instances from the navigation panel.  Click the Status tab, from the Application Instances window, to view the application path.
  18. 18. Start up application / verifying running  Verify that the target state is set to Run, the current state displays Ready, and the current HA state displays Active. 
  19. 19. Add Tmedia Unit - verifying  Select Hardware from Navigation panel.  Verify the hardware list to assure that the hardware is not already installed.
  20. 20. Add Tmedia Unit - adding new hw  Select Hardware from Navigation panel.  Click Create New Hardware from the information panel, to add a new TMP6400.  Enter the serial number of the TMP6400.  Enter a name for the hardware device. • Select TBGateway from the Adapter Type field. • Select Enabled from the Target State field. • Click Create to store your settings.
  21. 21. TMS1600  Tmedia TMS1600 : a key scalability component to build large-scale carrier grade VoIP and TDM solutions. TMS1600 Switch provides the means by which a combination of TMP6400 units can be interconnected to create a 32,768 perfectly non-blockingsystem.
  22. 22. Add TMS1600 …  Select Hardware from the navigation panel.  Click Create New Hardware from the information panel, to add a new TMS1600.  Enter the serial number of TMS1600.  Enter a name for the hardware device. • Select TMS from the Adapter Type field. • Select Enabled from the Target State field. • Click Create to store your settings.
  23. 23. Configure TMS1600 …  Select TMS Network from the navigation panel.  Click Configure New TMS Network to access the TMS Network cfg window.  Select the name of the primary switch from the Primary Adapter field. This switch will operate as the active or main switch. • Select the name of the secondary switch from the Secondary Adapter field. This switch will function as the backup switch. • Click Create to save the configuration.
  24. 24. Line Interfaces
  25. 25. Line Interfaces & line Service For each T1/E1/J1 line that the Tmedia unit will use, a line interface with a related line service is configured in a one-to-one relationship. The configuring of the line interface activates the hardware and the line service is configured to transport traffic and signaling payload. A conceptual image is shown below
  26. 26. Add Line Interfaces  Select Line Interfaces from the navigation panel. Click Create New Line Interface from the Information panel
  27. 27. Add Line Interfaces  To create a T1/E1/J1 line interface: • Enter a name for the line interface, and set the Line Type • The local indexes for trunks are zero-based values. This means that local index 0 is trunk 1 and local index 1 is trunk 2. Enter a local index number, assigning a different value to each T1/E1/J1 line interface. • Enter a local index number, assigning a different index to each T1/E1/J1 line interface. • Set the Line Length, Encoding and Signal Level • Click Create
  28. 28. Create line services  Select Line Interfaces from the navigation panel. Click New Child Line Service from the Line Interface Information panel
  29. 29. Create line services  Enter a name for the line service and click Create  Repeat this procedure for each T1/E1/J1 line that you will use.
  30. 30. Clocking
  31. 31. Clocking  Select Clocking from the navigation panel.  Click Create New System Clock Reference.  Select a hardware adapter • Select a Clock Reference Type and Source • Click Create
  32. 32. ISDN Signaling Stack ISDN signaling stacks are signaling resources that are assigned to a specific line of the Tmedia unit.  Based on the Q.931 switch variant that will be used by the system, a selection of ISDN variants are available.  For each line service requiring ISDN signaling, an ISDN signaling stack is created with its own distinct signaling variant.
  33. 33. Configuring ISDN Signaling  Select ISDN from the navigation panel.  Click Create New ISDN Stack.  Enter a name for the ISDN stack • Select the line service requiring ISDN signaling • Select the variant • Click Create, to save the changes  Notes : To use an ISDN signaling stack, it must be assigned to a Network Access Point (NAP),
  34. 34. SIP Stack
  35. 35. Configuring SIP  Select SIP from the navigation panel.  Click Create New SIP from the information panel  Enter a name for the SIP configuration • Enter a name for the SIP Configuration stack • Select the Tmedia unit that will host SIP signaling • Click Create, to save the changes 
  36. 36. create SIP new transport server  Click Create New Transport Server from the SIP Configuration window.  Enter a name for the transport server • Select a port type and number. (egUDP, port 53 for SIP traffic to the DNS server. • Click Create to save changes.
  37. 37. create SIP new transport server
  38. 38. SIP – configure DNS • Click DNS Params in the SIP configuration window. • Enter the IP address of the DNS • Select the transport server • Click Save to store your settings
  39. 39. Create SAP • The Service Access Point is used to bind the SIP stack with a transport server. Depending on the system configuration, multiple SAPS can be configured. To create a SAP: 1.Click Create New SAP from the SIP configuration window. 2.Enter a name for the SAP • Click Create to save the settings 3. Use the << key to select one or more transport servers for the newly created service access point
  40. 40. SS7
  41. 41. SS7 – MTP L2 The configuration of an MTP2 layer consists of the following: • Creating an MTP2 configuration • Creating an MTP2 Link
  42. 42. Create MTP-2 cfg Select MTP2 from the navigation panel.  Enter a name for the MTP2 configuration, and click Save to store the configuration settings.
  43. 43. Create MTP-2 link  The MTP2 link is used to link the MTP2 physical layer with a line service carrying SS7 signaling.  Parameters below are configured in the MTP2 link: • Mode of connection: Normal or HSL • Line service • Timeslot used • Protocol Type • Destination Point Code (DPC) • Timeslot rate
  44. 44. Create a new MTP-2 link  Click Create New Mtp2 Link, to access MTP2 link configuration window.  Enter a name for the MTP2 link • Select the connection mode. Normal requires that you choose the timeslot used. HSL uses all timeslots. • Select the line service carrying the SS7 payload, set the protocol type, DPC, and the timeslot rate Click Create to save the settings
  45. 45. MTP-3
  46. 46. Create MTP-3 cfg  Select MTP3 from the navigation panel.  Provide a name for the MTP3 configuration • Click Create to save the settings
  47. 47. Create MTP-3 network  Click Create New MTP3 Network Enter a name for the network and select the SS7 DPC length. • Click Create to store the settings
  48. 48. Create MTP-3 Point Code  Click Create New MTP3 Point Code  Provide a name for the point code. Click Create to save the point code.
  49. 49. Create MTP-3 LinkSet  Click Create New MTP3 LinkSet  Provide a name for the linkset. • Select an origin point code and an adjacent point code • Click Create to save the linkset
  50. 50. Create MTP-3 Route  Click Create New MTP3 Route  Provide a name that indicates this is your self route. • Select OPC for an origin point code. (DPC is for a route leading away from you). • Select a point code and click Create to create the MTP3 Route
  51. 51. Create MTP-3 Route   Provide a name that indicates this is your self route. • Select OPC for an origin point code. (DPC is for a route leading away from you). • Select a point code and click Create to create the MTP3 Route
  52. 52. Create MTP-3 Route  Using the << key to associate a linkset with the route.
  53. 53. ISUP
  54. 54. Create SS7 Stack – ISUP • Create ISUP Configuration • Create ISUP Network – Use MTP3 network here • Create ISUP userpart – Select appropriate options in the web portal • Create ISUP interface – Contains Circuits from OPC to DPC – Create circuit groups by selecting the check box (or shortcut “Select All”)
  55. 55. Create SIP • Create SIP configurations • Create SIP profile – Fill in the SDP – This would be used for SIP compatibility negotiation • Create SIP Transport Server – Select the IP interface for SIP traffic • Create SIP Service Access Point – Select the IP interface for SIP traffic
  56. 56. Create NAP • • Create Network Access Point (NAP) for each group Each Network Access Point (NAP) needs a unique name in CAPITAL – NAP for ISUP • Select the circuit group and click “<<“ • All selected circuit belongs to the same NAP • May select the circuit usage – NAP for ISDN • Select the ISDN stack and click “<<“ – NAP for SIP • Select the SIP SAP and click “<<“ • Select the IP interface for RTP traffic • Input the destination IP and port. • Fill in extra information if required.
  57. 57. Troubleshooting tools tb640debug Provide a snapshot on all configurations in the system. /lib/tb/toolpack/pkg/2.4.0/bin/release/pcc-linux/tb640debug tbsigtrace Provide signaling trace on SS7, ISDN and SIP Capture in pcap format. Viewable in Wireshark or Ethereal tblogtrace Capture logs from TMG3200 telecom module /lib/tb/toolpack/setup/12358/2.4/apps/tblogtrace Toolpack module’s log Contain all logs of daily activities /lib/tb/toolpack/setup/12358/2.4/apps/ Use “du –sh” to check each folder size Use “df” to check the disk space

×