1 / 63

H.320 IOS Gateway

Learn about H.320 suite specifications, signaling flow, Bit Allocation, codec details, and dial-peer configuration on Cisco IOS gateways. Find troubleshooting tips and interoperability features.

cfacer
Download Presentation

H.320 IOS Gateway

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. H.320 IOS Gateway

  2. Agenda • H.320 Protocol Overview • H.320 IOS gateway feature • H.320 gateway configuration • H.320 troubleshooting

  3. H.320 Protocol Overview

  4. H.320 Description • The H.320 suite addresses videoconferencing over circuit switched services like ISDN. • Specifies requirements for processing audio and video information. • Provides common formats for compatible audio/video inputs and outputs, and protocols that allow a multimedia terminal to utilize the communications links and synchronization of audio and video signals. • The H.320 suite consists of several ITU specifications, including H.320/H.221/H.242/H.230/H.241.

  5. H.320 Generic Diagram H320 System diagram

  6. H.320 System control signal flow • The path for the terminal-to-network control is through ISDN D-channel (Q931). • One H320 call may consist of multiple ISDN calls: one primary call and zero/one/multiple secondary calls. • Regular ISDN call setup/teardown procedure. • Bearer-cap set to unrestricted digital. • The path for terminal-to-terminal control is through BAS channel defined in ITU H.221

  7. H.221 Overview • Defines frame structure for audiovisual tele-services in single or multiple B or H0 channels or a single H11 or H12 channel • Subdivides an overall transmission channel of 64 to 1920Kbps into lower rates suitable for audio, video and data purpose. • Provides synchronizing and ordering transmissions over multiple B channels.

  8. Bit Allocation Example for 2B (2x64) Call

  9. Ipanema H.320 GW • Recognize the H.320 call based on dialpeer config. • Bundle multiple ISDN calls into one logical H.320 call and present single call to H323 or SCCP side. • Support in-session control via the conversion of BAS/H245 and BAS/SCCP.

  10. Protocol Interworking Between H.320 and H.323

  11. H.221/H.245 Mapping Examples

  12. H.221/SCCP Mapping Examples

  13. H.320 Feature in IOS Gateways

  14. A Integrated Voice and Video GW in ISR CallManager Cluster WAN • Video gateway capabilities built into ISR ISDN voice interfaces • Allows for extension of currently deployed systems • Provides simplified architecture for next generation combined voice and video networks • Functionality • Px64 implementation for up to 1024Kbps calls • Interoperable with major 3rd party components up to 128K • Video Codecs: H261, H263, H.263+, H.264 • Protocols: H323 PSTN H.320 H.320 H.320 Voice/Video IP Voice/Video

  15. H.320 General Feature Description • Provides for calls between H.323/SCCP to H.320. • Each H.320 call can be from 1B (64k) up to 16B (1024K), using bandwidth configuration. • 1024K max in back to back gateway configuration • 128k max in H.320 video terminal to gateway configuration (H.320 terminals only support 128k in H.221 mode) in 12.4(11)T release. The 12.4(20)T release allows ISO 13871 channel bonding to allow higher bandwidths. • Support for the feature is on the c5510 TI DSPs. Each DSP can support 16B worth of H.320 calls, and can be mixed with other call types (voice/fax/modem). • Supported voice codecs: • G.711 (64, 56, and 48kbps) • G.722 (64, 56, and 48kbps) • G.728 • G.729 • Supported Video codecs: • H.261, H.263, H.263+, H.264

  16. H.320 General Feature Description • H.320 specification • Translate H.221 frames into RTP audio / video packets • Translate RTP audio / video packets into H.221 frames • H.221 Encapsulation on H.320 side • Dynamic adding and removing of B-channels during call setup • Automatic frame and multiframe alignment and channel synchronization • BAS signaling processing with squelching • Dynamic secondary call number exchange using ITU H.242 • RTP encapsulation on H.323/SCCP • RFC 3550 (G.711, G.722 (64, 56, and 48kbps), G.728, G.729) • RFC 2032 (H.261 Video) • RFC 2190 (H.263 Video) • RCF 2429 (H.263+ Video) • ITU-T H.241 Annex-A (H.264 Video)

  17. Dial-peer configuration for audio/video codec: • Default codec for H.320 calls – The default audio/video codec on the dial-peer for H.320 calls is codec transparent. This gives the endpoints to control the desired audio/video codec selection based on the bandwidth of the call. Endpoints would prefer H.264 codec for calls at 128Kbps and H.263 for higher bandwidths. • What is codec transparent – Gateway would pass the list of codecs coming from H.320 remote endpoint across to the H.323 remote endpoint and vice-versa. But only the codecs that are supported by the gateway are passed. • Audio/Video codec filtering – To give the user control over desired audio/video codec selection and for inter-operability the audio/video codecs can be configured on the dial-peer. This will only forward the codecs that are configured on the dial-peer if advertised by the remote endpoints.

  18. Numbering Descriptions: Static vs. Dynamic • Normally, an H.320 terminal would have one or more numbers assigned, just like a normal POTS line. In this feature, the IOS gateway is becoming a virtual H.320 terminal on one side of the H.320 call. This facilitates the need to have numbers ‘assigned’ to the IOS gateway. • The IOS gateway gets around this by allowing the user to configure number pools for H.320 calls. These pools can work in 2 modes, static or dynamic. • Static numbering is used when both sides of the H.320 call know what all of the secondary leg numbers will be. Numbers may be repeated, but both sides know the numbers. No numbers are passed between the terminals. • Dynamic numbering is used when only the called H.320 terminal (or IOS gateway) knows the secondary leg numbers (the primary call leg number is known). Once the H.320 primary call leg is established, the called H.320 terminal will pass the secondary leg numbers to the calling H.320 terminal, using ITU H.221/H.242 standards or ISO-13871 bonding. Currently the IOS gateway will support only the ITU H.221/H.242 method.

  19. H.320 Feature Limitations • Only TI c5510 DSP supported. No other DSP type is supported. • The DSP must have enough available timeslots for the H.320 call (the call cannot span DSPs). • Feature supports G.729 audio, but no G.729 support for SCCPH.320 directly. (If the same router is the CME, and the H.320 gateway, the phone should be configured for G.711) • G.722 is supported for H.320, but not for general TDM calls. • No G.722 32k and 24k audio. • No RFC3984 support for H.264. • TDM interface must be ISDN (BRI or PRI). No other TDM interface types are supported (i.e. E1 MFCR2). • The member interfaces of trunk-group or NFAS group must reside on c5510-based NMs and/or 28/38 onboard slot. • No DTMF support (that is, no inband to out of band conversion). • No Overlap dialing. • No Supplementary services.

  20. H.320 IOS Supported Platforms and Modules • Platforms • 2600XM • 2691 • 3700 • 2800 • 3800 • Hardware Modules • NM-HD • NM-HD-2V • NM-HD-2VE • NM-HDV2 • VWIC-xMFT-x • VIC2-2BRI • VIC-(EVM-BRI) • VWIC2-xMFT-x

  21. Gateway Configuration

  22. H320 Video Network Setup: Tested Components • CME/SRST 4.0 • CCM version 4.1 & 4.2 • CVTA version 1.0(2) • CUVA version 2.0(1) • Skinny Endpoints • Cisco IP-Phones: (phone supported are 7940, 7941, 7960, 7961,and 7970) • 7940/7960 with firmware: P00306000500 and P00307020300 • 7941/7961 with firmware: TERM41.7-0-1-43DEV • 7970 with firmware: TERM70.6-0-2-0s and TERM70.7-0-1-0s • Tandberg version: E3.0 and E4.1 • H323 & H320 Endpoints • Tandberg version: E3.0 and E4.1 • Polycom version: Release 7.5.2

  23. Call Flows • Call Flows for H.320 (to/from PSTN): • H.320 to/from SCCP Audio/Video Endpoints • H.320 to/from H.323 Audio/Video Endpoints • CCM(H.323 trunk) to/from H320 Endpoints • Call Flows in SRST Mode • Local SCCP Audio/Video H320 SCCP Audio/Video • Local SCCP Audio/Video  H.320 Audio/Video

  24. Controller t1 1/0 pri-group timeslots 1-24 interface Serial1/0:23 no ip address isdn switch-type primary-ni isdn integrate calltype all TDM Configuration

  25. secondary number configuration: Static • Outgoing H320 calls: • voice class called number outbound 100 • index 1 6502221100 - 6502221111 • dial-peer voice 3000 pots • voice-class called-number outbound 100 • Incoming H.320 calls: • voice class called number inbound 100 • index 1 65022211.. • dial-peer voice 4000 pots • voice-class called-number inbound 100

  26. secondary number configuration: Dynamic • Incoming H.320 calls: • voice class called number pool 100 • index 1 6502221111 - 6502221116 • voice-port 1/0:23 • voice-class called-number-pool 100

  27. Outgoing H.320 calls dial-peer voice 124 pots information-type video destination-pattern 6505552222 bandwidth maximum 384 voice-class called-number outbound 100 port 4/1:23 Incoming H.320 calls: dial-peer voice 123 pots information-type video incoming called-number 6505552222 bandwidth maximum 384 minimum 384 voice-class called-number inbound 100 direct-inward-dial Pots Dial-peer configuration (Static)

  28. Outgoing H.320 calls: dial-peer voice 124 pots information-type video destination-pattern 6505552222 bandwidth maximum 384 port 4/1:23 Incoming H.320 calls: dial-peer voice 123 pots information-type video incoming called-number 6505552222 bandwidth maximum 384 minimum 384 direct-inward-dial Voice-port 1/0:23 voice-class called-number-pool 100 Pots Dial-peer configuration (Dynamic)

  29. H323 configuration • voice service voip • h323 • call start slow

  30. Voip Dial-peer configuration • voice class codec 100 • codec preference 1 [G.711, G.722 (64, 56, and 48kbps), G.728, G.729] • video codec [h261/h263/h263+/h264] • dial-peer voice 7001 voip • video codec [h261/h263/h263+/h264] • codec [G.711, G.722 (64, 56, and 48kbps), G.728, G.729] • rtp payload-type cisco-codec-video-h263+ [96-127] • rtp payload-type cisco-codec-video-h264 [96-127]

  31. Dial-peer configuration for audio/video codec: Config Example -default dial-peer voice 919 voip destination-pattern 919.... g711ulaw, g722-64, g722-48 h261, h263+, h264 g711ulaw, g722-64, g722-48 h261, h263+, h264 H.323-EP Codecs: g711ulaw, g722-64, g722-48, h261 h263+, h264 H.320-EP Codecs: g711ulaw, g722-64, g728, h261, h263 H.323 Call Leg H.320 Call Leg g711ulaw, g722-64, g728 h261, h263 g711ulaw, g722-64, g728 h261, h263 H.320 Gateway

  32. Dial-peer configuration for audio/video codec: Config Example – codec filter dial-peer voice 919 voip destination-pattern 919…. codec g711ulaw video codec h263 g711ulaw, g722-64, g722-48 h261, h263+, h264 g711ulaw, h263 H.323-EP Codecs: g711ulaw, g722-64, g722-48, h261 h263+, h264 H.320-EP Codecs: g711ulaw, g722-64, g728, h261, h263 H.323 Call Leg H.320 Call Leg g711ulaw, h263 g711ulaw, g722-64, g728 h261, h263 H.320 Gateway

  33. H320 Dynamic (H.242) Secondary Dial PlanConfiguration TGW OGW 6505552222 interface Serial4/1:23 isdn integrate calltype all dial-peer voice 124 pots information-type video destination-pattern 6505552222 bandwidth maximum 384 port 4/1:23 voice class called number pool 100 index 1 6502221111 index 2 6502221212 index 3 6503332222–6503334444 interface Serial3/1:23 isdn integratecalltype all voice-port 3/1:23 voice-class called number pool 100 dial-peer voice 123 pots information-type video incoming called-number 6505552222 bandwidth maximum 384

  34. Primary call setup: 6505552222 (Q.931 setup) Secondary number exchange: 6502221111, 1212, 2222, 2223 (H.221/H.242 messages) Sec call setup: 6502221111 (Q.931 setup) Sec call setup: 6502221212 (Q.931 setup) Sec call setup: 6502222222 (Q.931 setup) Sec call setup: 6502222223 (Q.931 setup) H320 Dynamic (H.242) Secondary Dial PlanCall Setup Flow OGW TGW 6505552222

  35. H320 Static Secondary Dial PlanConfiguration TGW OGW 6505551111 6505552222 voice class called number outbound 100 index 1 6502221111 index 2 6502221112 index 2 6502221113 index 3 6502221114 index 4 6502221115 index 5 6502221116 interface Serial3/1:23 isdn integrate calltype all dial-peer voice 124 pots information-type video destination-pattern 6505552222 bandwidth maximum 384 voice-class called-number outbound 100 port 4/1:23 voice class called number inbound 101 index 1 650222111. interface Serial4/1:23 isdn integrate calltype all dial-peer voice 123 pots information-type video incoming called-number 6505552222 bandwidth maximum 384 minimum 384 voice-class called-number inbound 101

  36. Primary call setup: 6505552222 Sec call setup: 6502221111 Sec call setup: 6502221112 Sec call setup: 6502221113 Sec call setup: 6502221114 H320 Static Secondary Dial PlanCall Setup Flow OGW TGW 6505552222

  37. Troubleshooting

  38. Show Commands • Show ephone registered • Show call active video [compact/brief] • Show call history video • Show voice dsp • Show isdn status • Show voice call summary • Show voice class called-number inbound <tag> • Show voice class called-number outbound <tag> • Show voice class called-number-pool <tag> (Dynamic)

  39. General Debugs for H.320 calls • Debug voip ccapi default • Debug cch323 video • Debug voip vtsp all • Debug voip dsm all • Debug voip dsmp all • Debug voip h221 all • Debug voip h221 raw (not activated by all option) • Debug voip h221 raw decode (not activated by all option) • Debug H225 asn1/event/q931 • Debug H225 q931 • Debug H245 asn1/event • Debug ephone video ( debug ephone detail ) • Debug dsp-resource-manager flex all • Debug isdn q931

  40. New H.221 Debugs • Debug voice/voip h221 • This is the new debug class for the H.221 library code. All debugs in the class fully support call filter match-lists. • ALL - Activates error (all), inout, and function only. • DEFAULT – Activates error (no informational), inout, and function. • ERROR – Activates call error and software error debugs (no informational). • ERROR CALL – Activates major call related error debugs. • ERROR CALL INFORMATIONAL – Activates major and minor call related error debugs. • ERROR SOFTWARE – Activates major software related error debugs. • ERROR SOFTWARE INFORMATIONAL – Activates major and minor software related error debugs.

  41. New H.221 Debugs continued • Debug voice/voip h221 • FUNCTION – Activates debugs at the entry and exit points of a code procedure. No internal data is displayed, only the procedure names. • INOUT - Activates in-out debugs. • INDIVIDUAL – Activates a single debug using an index number. The list of index numbers are located in the backup slides. • RAW – Displays the raw H221 BAS messages buffers coming to and from the DSP. It will also display any buffer fragments (pieces of messages requiring the next 25 byte buffer from the DSP), and complete MBE (multi-byte extension) buffers. All messages are displayed in hex. • RAW DECODE – Displays the raw H221 BAS messages to and from the DSP in decoded format. Not every H221 BAS is decoded, only the ones that the router will use. If the router does not use the BAS code, the display will be blank. Please note that the raw decode option does not activate the raw option also. This debug output is very verbose.

  42. Troubleshooting guide

  43. Troubleshooting: Primary Call Setup • Normally, if the primary call is having problems being established, the problem is usually dial-peer/configuration related. • Things to check • Make sure that pots dial-peer has information-type video. • Make sure that pots dial-peer that is being used is actually the correct one. • Make sure “isdn integrate calltype all” is defined from the supported ISDN interface • Make sure that for incoming H.320 calls, the bearer capability is correct (should be 64K unrestricted digital, 56k digital is not supported)

  44. Troubleshooting: Primary Call Setup • Debugs • Debug isdn q931 • Debug h225 event/q931 (if IP leg H.323) • Debug voip tsp dialpeer • Debug voip dialpeer inout • Debug voip ccapi inout

  45. Troubleshooting: Secondary Call(s) Setup • The problem of the secondary calls not be established can be more complicated than the primary not being established. • Two major methods of establishing secondary legs exist. • ITU-H.221/H.242 only (pX64 mode, supported) • ISO-13871/ITU-H.244 bonding (p*64 mode, supported in 12.4(20)T code) • For troubleshooting, we will take a look at 3 different cases. • When back to back IOS gateways are connected together via an H.320 link. • When the IOS gateway is connected directly to an H.320 device (directly or via a PBX/switch configuration) • The bandwidth reported via H.221 doesn’t match the range configured on the gateway.

  46. Troubleshooting: Secondary Call(s) Setup; back to back IOS gateway • The IOS gateways can have a secondary number configuration of static numbers, or dynamic numbers. • For the static numbers configuration, both gateways need to know the numbers that will dialed on the secondary legs. No number exchange is passed. • In the dynamic numbers case, the called gateway will send the calling gateway the secondary leg numbers to dial, using the H.221/H.242 protocol. This is done after the primary leg is up, and H.221 frame sync has been achieved.

  47. Troubleshooting: Secondary Call(s) Setup; back to back, static number configuration • For static number calls to work, both routers must have knowledge of all the numbers to dial. The feature was done in a manner that each H.320 doesn’t necessarily need a complete set of numbers. If the calling router doesn’t have enough numbers configured, it will repeat the last number in the configuration enough times to complete all of the calls. • The important thing to remember is that both routers will know about all of the numbers that will be dialed.

  48. Troubleshooting: Secondary Call(s) Setup; back to back, static number configuration • Things to check: • Make sure the calling number is the same for each call leg. • On the originating router, make sure that the outgoing pots dial-peer has the correct voice class called number outbound index, and that index has the correct numbers. • On the terminating router, make sure that the incoming pots dial-peer has the correct voice class called number inbound index, and that index has the correct numbers. • Debugs • Debug isdn q931 • Debug voip tsp dialpeer

  49. Troubleshooting: Secondary Call(s) Setup; back to back, dynamic number configuration • For dynamic numbers, the numbers will be passed from the terminating router, back to the originating router. In this case, no configuration is needed on the originating router. • Things to check: • That there is a properly configured voice class called number pool index. • The voice-port of the incoming ISDN interface should have the correct voice-class called-number pool. • The numbers in the pool should be numbers that will actually route though the PSTN network between the routers. Remember that translation rules may apply to these numbers also. • Debugs: • Debug voip tsp dialpeer • Debug isdn q931 • Debug voip h221 individual 32 (displays secondary number exchange on the H221 BAS stream)

  50. Troubleshooting: Secondary Call(s) Setup; gateway to H.320 terminal • H.320 terminals typically support either pX64 and p*64 mode. • For most terminals, they will only support up to 2 b-channels in pX64 mode (ITU-H.221 only), and 6 b-channels in p*64 mode (ISO-13871 bonding/ITU-H.221). • This is regardless of how the terminal can be configured (for example, some Polycom H.320 terminals have a 7X64 and 14X64 setting, but will not actually perform this mode). • Also, H.320 terminals typically don’t support the H.242 method of dynamic exchange of numbers for secondary call legs.

More Related