DocWiki - User contributions [en]

Video on ISR 2800 3800 H.320 GW with ISO 13871 bonding Configuration Example

2011-02-08T12:08:09Z

Msamarts: /* Related show Commands */

==Introduction==

This is the basic config for any ISR router 2800 / 3800 series with PRI connection to PSTN / PBX and H.323 protocol on IP side.

==Design==

The example toplogy:

Tandberg VT - E1 PRI - PSTN - E1 PRI - ISR router - H.323 GK - Tandberg VT

==Configuration==

1. First we need to register GW and the video endpoint to the GK, we can run GK feature on the same router if we have IOS with GK feature for example - C2800NM-IPVOICE_IVS-M.
The most simple setup will be if we register endpoing with full E164 number and GW with the tech prefix, chousen in a way it will allow dialing to PSTN without any number transformation.
Assume PSTN will requre 00 for international call, in this case we can use the following config on GK:

!
gatekeeper
zone local video-98 mappets.com 10.52.218.98
no use-proxy video-98 default inbound-to terminal
no use-proxy video-98 default outbound-from terminal
no shutdown
!

There is no need to configure zone prefixes as GW will register with the tech prefix.
And VT will register with the full E164 number, so GK will always be able to resolve the them to IP.
For VT we need to allow direct calls to / from H.323 GW, so we disabling proxy requirement.

The matching GW config will be:

!
voice service voip
h323
emptycapability
h225 h245-address on-connect
call start slow
h245 tunnel disable
h245 timeout olc 30
!

Formally you will need only slow start and OLC timeout tuning. Because it may take some time for all ISDN secondary calls to get connected and for the BAS and codec negotiation to start, we need allow voip side to wait for some time. The 30 second timeout is reasonable setting, if we are talking about some VT like Tandberg or Polycom, they will have that settings by default. But if you have CallManager on IP side, you need to tune that timeouts via Service parameters:

H245 TCS Timeout 30

Media Exchange Interface Capability Timer 30

Media Exchange Timer 30

You may also consider to un-check the check-box on the GW config page:

"Wait for Far End H.245 Terminal Capability Set"

It usually good practice explicitly specify which interface will be used for H.323 signaling and if you register the GW to GK you will need to configure:

!
interface FastEthernet0/0
ip address 10.52.218.91 255.255.255.0
h323-gateway voip interface
h323-gateway voip id video-98 ipaddr 10.52.218.98 1719
h323-gateway voip h323-id ios-91-to-98
h323-gateway voip tech-prefix 00
h323-gateway voip bind srcaddr 10.52.218.91
!
gateway
!

Next we can proceed with the H.320 video GW configuration.

1. Specify the card type you will have:

card type e1 1 1

2. As video calls are actually the DATA calls by the nature of video content, we need to ensure the clocking is configured corectcly:

network-clock-participate slot 1
network-clock-participate wic 1
!
! Choose the one which required by your hardware setup.
!
network-clock-select 1 E1 1/0

3. You will need to specify the ISDN switch type before you can proceed with PRI group config on the controller:

isdn switch-type primary-net5

4. The controller config is the same as for any PRI connection:

controller E1 1/0
pri-group timeslots 1-31
description >>>>> Test of NEW BT PRI ports - out 338898 *** <<<<<
!

5. Now we need to configure D-channel to accept / send Data calls:

!
interface Serial1/0:15
description >>>>> Test of NEW BT PRI ports - out 338898 *** <<<<<
no ip address
encapsulation hdlc
isdn switch-type primary-net5
isdn map address .* plan unknown type unknown
isdn negotiate-bchan resend-setup
isdn bchan-number-order ascending
isdn sending-complete
isdn integrate calltype all
no cdp enable
!

6. Now we can proceed with the preparation for the dial-peer config, first let define the codecs we will use on IP side.
Please keep in mind that GW will actually do the filtering of the codes it will announce to the endpoints on both sides.

!
voice class codec 1000
codec preference 1 g711ulaw
codec preference 2 g711alaw
codec preference 3 g728
codec preference 4 g722-64
codec preference 5 g722-56
codec preference 6 g722-48
video codec h261
video codec h263
video codec h263+
video codec h264
!

7. This part is required to accept the incoming video calls, we need to have to provide the secondary numbers to the calling party, so they can call us on that numbers to add more bandwidth to the video call, that numbers will be sent out during ISO 13871 bonding stage. According to ISO 13871 only 7 digits will be sent. So there is no need or sense to configure more then 7 digits in the pool config. But you can configure less then 7 digits. The secondary called number will be crated from the primary called number by replacing the last digits with the numbers from the pool. So in case when only last 1 or 2 digits are different, you pool may have only 1 or 2 digit numbers in it.

!
voice class called number pool 3151
index 1 315140 - 315149

8. Now we need to apply that pool to the voice port to activate it:

!
voice-port 1/0:15
voice-class called-number-pool 3151
!

9. Now we are ready to proceed with the dial-peer configuration we need 4 of them, two incoming and two outgoing.
It is possible to use one POTS dial-peer as incoming and outgoing at the same time, but we will provide config for two of them for the sake of clarity:

!
dial-peer voice 99 pots
description default incoming video dial-peer
information-type video
incoming called-number 313300
bandwidth maximum 384
direct-inward-dial
!

!
dial-peer voice 9001 pots
description default outgoing video dial-peer
destination-pattern 00
information-type video
bandwidth maximum 384
port 1/0:15
forward-digits all
!

10. here is the example of the VOIP dial-peer, now we configured it as both - incoming and outgoing:

!
dial-peer voice 770 voip
description default incoming/outgoing voip dial-peer for all calls from GK w
destination-pattern 701...
voice-class codec 1000
session target ras
incoming called-number 00.
dtmf-relay h245-alphanumeric
!

==Related show Commands==
This section provides information you can use to confirm your configuration is working properly.

Certain show commands are supported by the [https://www.cisco.com/cgi-bin/Support/OutputInterpreter/home.pl Output Interpreter Tool (registered customers only)], which allows you to view an analysis of show command output.

show network-clocks
show isdn status
show dial-peer voice summary
show voice call status
show voice dsp

There also some useful commands to add and they can be used on All routers in production as well:

service nagle
service tcp-keepalives-in
service tcp-keepalives-out
service timestamps debug datetime msec
service timestamps log datetime msec

!
logging message-counter syslog
logging queue-limit 100000
logging buffered 5000000
logging rate-limit 10000
no logging console

And some very useful aliases :)

!
alias exec c conf t
alias exec r sh run
alias exec i sh ip ro
alias exec ib sh ip int brie
alias exec gs show run | s gatekeeper
alias exec ge sho gatekeeper end
alias exec sg sho gatekeeper
alias exec rs sh run | s
alias exec ri sh run | i
alias exec rb sh run | b
alias exec dp sh run | be dial-p
!

In case you will need to contact TAC, you can get the debugs following this template:

#1. Add to the config or make sure you have it already:

!
service sequence-numbers
service timestamps debug datetime msec
service timestamps log datetime msec
!
logging buffered 5000000
logging rate-limit 10000
logging queue-limit 100000
no logging console
!

#2. Then start logging to a file from your telnet application and get:

!
U all
Term no mon
Term len 0
!
Sh ver
Sh run
!

#3. Then enable debugs (you can copy / paste all of them to the telnet session window )

!
Deb voip ccapi inout
Deb isdn q931
Deb h225 q931
Deb h225 asn1
Deb h245 asn1
Deb cch323 h245
deb voip tsp dialpeer
deb voip h221 raw decode

Sh deb
Term no mon

Clear log before placing call:

Clear logg

Then place the call and get content of the buffer as:

Show logg

Please send the log in simple TXT format attached to the e-mail in simple TXT format with extension".TXT".
Please include attach@cisco.com in CC to get logs and e-mail attached to case notes.

Enjoy :)

==Show running-config==

<pre>Add show running config of your device</pre>

==Related Information==
[http://www.cisco.com/web/psa/products/index.html Technical Support & Documentation - Cisco Systems]




[[Category:VoIP Configuration Examples]]
[[Category:Video Configuration Examples]]

Video on ISR 2800 3800 H.320 GW with ISO 13871 bonding Configuration Example

2011-02-08T12:06:20Z

Msamarts: /* Related show Commands */

==Introduction==

This is the basic config for any ISR router 2800 / 3800 series with PRI connection to PSTN / PBX and H.323 protocol on IP side.

==Design==

The example toplogy:

Tandberg VT - E1 PRI - PSTN - E1 PRI - ISR router - H.323 GK - Tandberg VT

==Configuration==

1. First we need to register GW and the video endpoint to the GK, we can run GK feature on the same router if we have IOS with GK feature for example - C2800NM-IPVOICE_IVS-M.
The most simple setup will be if we register endpoing with full E164 number and GW with the tech prefix, chousen in a way it will allow dialing to PSTN without any number transformation.
Assume PSTN will requre 00 for international call, in this case we can use the following config on GK:

!
gatekeeper
zone local video-98 mappets.com 10.52.218.98
no use-proxy video-98 default inbound-to terminal
no use-proxy video-98 default outbound-from terminal
no shutdown
!

There is no need to configure zone prefixes as GW will register with the tech prefix.
And VT will register with the full E164 number, so GK will always be able to resolve the them to IP.
For VT we need to allow direct calls to / from H.323 GW, so we disabling proxy requirement.

The matching GW config will be:

!
voice service voip
h323
emptycapability
h225 h245-address on-connect
call start slow
h245 tunnel disable
h245 timeout olc 30
!

Formally you will need only slow start and OLC timeout tuning. Because it may take some time for all ISDN secondary calls to get connected and for the BAS and codec negotiation to start, we need allow voip side to wait for some time. The 30 second timeout is reasonable setting, if we are talking about some VT like Tandberg or Polycom, they will have that settings by default. But if you have CallManager on IP side, you need to tune that timeouts via Service parameters:

H245 TCS Timeout 30

Media Exchange Interface Capability Timer 30

Media Exchange Timer 30

You may also consider to un-check the check-box on the GW config page:

"Wait for Far End H.245 Terminal Capability Set"

It usually good practice explicitly specify which interface will be used for H.323 signaling and if you register the GW to GK you will need to configure:

!
interface FastEthernet0/0
ip address 10.52.218.91 255.255.255.0
h323-gateway voip interface
h323-gateway voip id video-98 ipaddr 10.52.218.98 1719
h323-gateway voip h323-id ios-91-to-98
h323-gateway voip tech-prefix 00
h323-gateway voip bind srcaddr 10.52.218.91
!
gateway
!

Next we can proceed with the H.320 video GW configuration.

1. Specify the card type you will have:

card type e1 1 1

2. As video calls are actually the DATA calls by the nature of video content, we need to ensure the clocking is configured corectcly:

network-clock-participate slot 1
network-clock-participate wic 1
!
! Choose the one which required by your hardware setup.
!
network-clock-select 1 E1 1/0

3. You will need to specify the ISDN switch type before you can proceed with PRI group config on the controller:

isdn switch-type primary-net5

4. The controller config is the same as for any PRI connection:

controller E1 1/0
pri-group timeslots 1-31
description >>>>> Test of NEW BT PRI ports - out 338898 *** <<<<<
!

5. Now we need to configure D-channel to accept / send Data calls:

!
interface Serial1/0:15
description >>>>> Test of NEW BT PRI ports - out 338898 *** <<<<<
no ip address
encapsulation hdlc
isdn switch-type primary-net5
isdn map address .* plan unknown type unknown
isdn negotiate-bchan resend-setup
isdn bchan-number-order ascending
isdn sending-complete
isdn integrate calltype all
no cdp enable
!

6. Now we can proceed with the preparation for the dial-peer config, first let define the codecs we will use on IP side.
Please keep in mind that GW will actually do the filtering of the codes it will announce to the endpoints on both sides.

!
voice class codec 1000
codec preference 1 g711ulaw
codec preference 2 g711alaw
codec preference 3 g728
codec preference 4 g722-64
codec preference 5 g722-56
codec preference 6 g722-48
video codec h261
video codec h263
video codec h263+
video codec h264
!

7. This part is required to accept the incoming video calls, we need to have to provide the secondary numbers to the calling party, so they can call us on that numbers to add more bandwidth to the video call, that numbers will be sent out during ISO 13871 bonding stage. According to ISO 13871 only 7 digits will be sent. So there is no need or sense to configure more then 7 digits in the pool config. But you can configure less then 7 digits. The secondary called number will be crated from the primary called number by replacing the last digits with the numbers from the pool. So in case when only last 1 or 2 digits are different, you pool may have only 1 or 2 digit numbers in it.

!
voice class called number pool 3151
index 1 315140 - 315149

8. Now we need to apply that pool to the voice port to activate it:

!
voice-port 1/0:15
voice-class called-number-pool 3151
!

9. Now we are ready to proceed with the dial-peer configuration we need 4 of them, two incoming and two outgoing.
It is possible to use one POTS dial-peer as incoming and outgoing at the same time, but we will provide config for two of them for the sake of clarity:

!
dial-peer voice 99 pots
description default incoming video dial-peer
information-type video
incoming called-number 313300
bandwidth maximum 384
direct-inward-dial
!

!
dial-peer voice 9001 pots
description default outgoing video dial-peer
destination-pattern 00
information-type video
bandwidth maximum 384
port 1/0:15
forward-digits all
!

10. here is the example of the VOIP dial-peer, now we configured it as both - incoming and outgoing:

!
dial-peer voice 770 voip
description default incoming/outgoing voip dial-peer for all calls from GK w
destination-pattern 701...
voice-class codec 1000
session target ras
incoming called-number 00.
dtmf-relay h245-alphanumeric
!

==Related show Commands==
This section provides information you can use to confirm your configuration is working properly.

Certain show commands are supported by the [https://www.cisco.com/cgi-bin/Support/OutputInterpreter/home.pl Output Interpreter Tool (registered customers only)], which allows you to view an analysis of show command output.

show network-clocks
show isdn status
show dial-peer voice summary
show voice call status
show voice dsp

There also some useful commands to add and they can be used on All routers in production as well:

service nagle
service tcp-keepalives-in
service tcp-keepalives-out
service timestamps debug datetime msec
service timestamps log datetime msec

!
logging message-counter syslog
logging queue-limit 100000
logging buffered 5000000
logging rate-limit 10000
no logging console

And some very useful aliases :)

!
alias exec c conf t
alias exec r sh run
alias exec i sh ip ro
alias exec ib sh ip int brie
alias exec gs show run | s gatekeeper
alias exec ge sho gatekeeper end
alias exec sg sho gatekeeper
alias exec rs sh run | s
alias exec ri sh run | i
alias exec rb sh run | b
alias exec dp sh run | be dial-p
!

In case you will need to contact TAC, you can get the debugs following this template:

#1. Add to the config or make sure you have it already:

service sequence-numbers
service timestamps debug datetime msec
service timestamps log datetime msec
!
logging buffered 5000000
logging rate-limit 10000
logging queue-limit 100000
no logging console

#2. Then start logging to a file from your telnet application and get:

U all
Term no mon
Term len 0
!
Sh ver
Sh run

#3. Then enable debugs (you can copy / paste all of them to the telnet session window )

Deb voip ccapi inout
Deb isdn q931
Deb h225 q931
Deb h225 asn1
Deb h245 asn1
Deb cch323 h245
deb voip tsp dialpeer
deb voip h221 raw decode

Sh deb
Term no mon

Clear log before placing call:

Clear logg

Then place the call and get content of the buffer as:

Show logg

Please send the log in simple TXT format attached to the e-mail in simple TXT format with extension".TXT".
Please include attach@cisco.com in CC to get logs and e-mail attached to case notes.

Enjoy :)

==Show running-config==

<pre>Add show running config of your device</pre>

==Related Information==
[http://www.cisco.com/web/psa/products/index.html Technical Support & Documentation - Cisco Systems]




[[Category:VoIP Configuration Examples]]
[[Category:Video Configuration Examples]]

Video on ISR 2800 3800 H.320 GW with ISO 13871 bonding Configuration Example

2011-02-08T12:01:02Z

Msamarts: /* Configuration */

==Introduction==

This is the basic config for any ISR router 2800 / 3800 series with PRI connection to PSTN / PBX and H.323 protocol on IP side.

==Design==

The example toplogy:

Tandberg VT - E1 PRI - PSTN - E1 PRI - ISR router - H.323 GK - Tandberg VT

==Configuration==

1. First we need to register GW and the video endpoint to the GK, we can run GK feature on the same router if we have IOS with GK feature for example - C2800NM-IPVOICE_IVS-M.
The most simple setup will be if we register endpoing with full E164 number and GW with the tech prefix, chousen in a way it will allow dialing to PSTN without any number transformation.
Assume PSTN will requre 00 for international call, in this case we can use the following config on GK:

!
gatekeeper
zone local video-98 mappets.com 10.52.218.98
no use-proxy video-98 default inbound-to terminal
no use-proxy video-98 default outbound-from terminal
no shutdown
!

There is no need to configure zone prefixes as GW will register with the tech prefix.
And VT will register with the full E164 number, so GK will always be able to resolve the them to IP.
For VT we need to allow direct calls to / from H.323 GW, so we disabling proxy requirement.

The matching GW config will be:

!
voice service voip
h323
emptycapability
h225 h245-address on-connect
call start slow
h245 tunnel disable
h245 timeout olc 30
!

Formally you will need only slow start and OLC timeout tuning. Because it may take some time for all ISDN secondary calls to get connected and for the BAS and codec negotiation to start, we need allow voip side to wait for some time. The 30 second timeout is reasonable setting, if we are talking about some VT like Tandberg or Polycom, they will have that settings by default. But if you have CallManager on IP side, you need to tune that timeouts via Service parameters:

H245 TCS Timeout 30

Media Exchange Interface Capability Timer 30

Media Exchange Timer 30

You may also consider to un-check the check-box on the GW config page:

"Wait for Far End H.245 Terminal Capability Set"

It usually good practice explicitly specify which interface will be used for H.323 signaling and if you register the GW to GK you will need to configure:

!
interface FastEthernet0/0
ip address 10.52.218.91 255.255.255.0
h323-gateway voip interface
h323-gateway voip id video-98 ipaddr 10.52.218.98 1719
h323-gateway voip h323-id ios-91-to-98
h323-gateway voip tech-prefix 00
h323-gateway voip bind srcaddr 10.52.218.91
!
gateway
!

Next we can proceed with the H.320 video GW configuration.

1. Specify the card type you will have:

card type e1 1 1

2. As video calls are actually the DATA calls by the nature of video content, we need to ensure the clocking is configured corectcly:

network-clock-participate slot 1
network-clock-participate wic 1
!
! Choose the one which required by your hardware setup.
!
network-clock-select 1 E1 1/0

3. You will need to specify the ISDN switch type before you can proceed with PRI group config on the controller:

isdn switch-type primary-net5

4. The controller config is the same as for any PRI connection:

controller E1 1/0
pri-group timeslots 1-31
description >>>>> Test of NEW BT PRI ports - out 338898 *** <<<<<
!

5. Now we need to configure D-channel to accept / send Data calls:

!
interface Serial1/0:15
description >>>>> Test of NEW BT PRI ports - out 338898 *** <<<<<
no ip address
encapsulation hdlc
isdn switch-type primary-net5
isdn map address .* plan unknown type unknown
isdn negotiate-bchan resend-setup
isdn bchan-number-order ascending
isdn sending-complete
isdn integrate calltype all
no cdp enable
!

6. Now we can proceed with the preparation for the dial-peer config, first let define the codecs we will use on IP side.
Please keep in mind that GW will actually do the filtering of the codes it will announce to the endpoints on both sides.

!
voice class codec 1000
codec preference 1 g711ulaw
codec preference 2 g711alaw
codec preference 3 g728
codec preference 4 g722-64
codec preference 5 g722-56
codec preference 6 g722-48
video codec h261
video codec h263
video codec h263+
video codec h264
!

7. This part is required to accept the incoming video calls, we need to have to provide the secondary numbers to the calling party, so they can call us on that numbers to add more bandwidth to the video call, that numbers will be sent out during ISO 13871 bonding stage. According to ISO 13871 only 7 digits will be sent. So there is no need or sense to configure more then 7 digits in the pool config. But you can configure less then 7 digits. The secondary called number will be crated from the primary called number by replacing the last digits with the numbers from the pool. So in case when only last 1 or 2 digits are different, you pool may have only 1 or 2 digit numbers in it.

!
voice class called number pool 3151
index 1 315140 - 315149

8. Now we need to apply that pool to the voice port to activate it:

!
voice-port 1/0:15
voice-class called-number-pool 3151
!

9. Now we are ready to proceed with the dial-peer configuration we need 4 of them, two incoming and two outgoing.
It is possible to use one POTS dial-peer as incoming and outgoing at the same time, but we will provide config for two of them for the sake of clarity:

!
dial-peer voice 99 pots
description default incoming video dial-peer
information-type video
incoming called-number 313300
bandwidth maximum 384
direct-inward-dial
!

!
dial-peer voice 9001 pots
description default outgoing video dial-peer
destination-pattern 00
information-type video
bandwidth maximum 384
port 1/0:15
forward-digits all
!

10. here is the example of the VOIP dial-peer, now we configured it as both - incoming and outgoing:

!
dial-peer voice 770 voip
description default incoming/outgoing voip dial-peer for all calls from GK w
destination-pattern 701...
voice-class codec 1000
session target ras
incoming called-number 00.
dtmf-relay h245-alphanumeric
!

==Related show Commands==
This section provides information you can use to confirm your configuration is working properly.

Certain show commands are supported by the [https://www.cisco.com/cgi-bin/Support/OutputInterpreter/home.pl Output Interpreter Tool (registered customers only)], which allows you to view an analysis of show command output.

show network-clocks
show isdn status
show dial-peer voice summary
show voice call status
show voice dsp

There also some useful commands to add and they can be used on All routers in production as well:

service nagle
service tcp-keepalives-in
service tcp-keepalives-out
service timestamps debug datetime msec
service timestamps log datetime msec

!
logging message-counter syslog
logging queue-limit 100000
logging buffered 5000000
logging rate-limit 10000
no logging console

And some very useful aliases :)

!
alias exec c conf t
alias exec r sh run
alias exec i sh ip ro
alias exec ib sh ip int brie
alias exec gs show run | s gatekeeper
alias exec ge sho gatekeeper end
alias exec sg sho gatekeeper
alias exec rs sh run | s
alias exec ri sh run | i
alias exec rb sh run | b
alias exec dp sh run | be dial-p
!

Enjoy :)

==Show running-config==

<pre>Add show running config of your device</pre>

==Related Information==
[http://www.cisco.com/web/psa/products/index.html Technical Support & Documentation - Cisco Systems]




[[Category:VoIP Configuration Examples]]
[[Category:Video Configuration Examples]]

Video on ISR 2800 3800 H.320 GW with ISO 13871 bonding Configuration Example

2011-02-08T12:00:05Z

Msamarts: /* Configuration */

==Introduction==

This is the basic config for any ISR router 2800 / 3800 series with PRI connection to PSTN / PBX and H.323 protocol on IP side.

==Design==

The example toplogy:

Tandberg VT - E1 PRI - PSTN - E1 PRI - ISR router - H.323 GK - Tandberg VT

==Configuration==

1. First we need to register GW and the video endpoint to the GK, we can run GK feature on the same router if we have IOS with GK feature for example - C2800NM-IPVOICE_IVS-M.
The most simple setup will be if we register endpoing with full E164 number and GW with the tech prefix, chousen in a way it will allow dialing to PSTN without any number transformation.
Assume PSTN will requre 00 for international call, in this case we can use the following config on GK:

!
gatekeeper
zone local video-98 mappets.com 10.52.218.98
no use-proxy video-98 default inbound-to terminal
no use-proxy video-98 default outbound-from terminal
no shutdown
!

There is no need to configure zone prefixes as GW will register with the tech prefix.
And VT will register with the full E164 number, so GK will always be able to resolve the them to IP.
For VT we need to allow direct calls to / from H.323 GW, so we disabling proxy requirement.

The matching GW config will be:

!

voice service voip
h323
emptycapability
h225 h245-address on-connect
call start slow
h245 tunnel disable
h245 timeout olc 30
!

Formally you will need only slow start and OLC timeout tuning. Because it may take some time for all ISDN secondary calls to get connected and for the BAS and codec negotiation to start, we need allow voip side to wait for some time. The 30 second timeout is reasonable setting, if we are talking about some VT like Tandberg or Polycom, they will have that settings by default. But if you have CallManager on IP side, you need to tune that timeouts via Service parameters:

H245 TCS Timeout 30

Media Exchange Interface Capability Timer 30

Media Exchange Timer 30

You may also consider to un-check the check-box on the GW config page:

"Wait for Far End H.245 Terminal Capability Set"

It usually good practice explicitly specify which interface will be used for H.323 signaling and if you register the GW to GK you will need to configure:

!
interface FastEthernet0/0
ip address 10.52.218.91 255.255.255.0
h323-gateway voip interface
h323-gateway voip id video-98 ipaddr 10.52.218.98 1719
h323-gateway voip h323-id ios-91-to-98
h323-gateway voip tech-prefix 00
h323-gateway voip bind srcaddr 10.52.218.91
!
gateway
!

Next we can proceed with the H.320 video GW configuration.

1. Specify the card type you will have:

card type e1 1 1

2. As video calls are actually the DATA calls by the nature of video content, we need to ensure the clocking is configured corectcly:

network-clock-participate slot 1
network-clock-participate wic 1
!
! Choose the one which required by your hardware setup.
!
network-clock-select 1 E1 1/0

3. You will need to specify the ISDN switch type before you can proceed with PRI group config on the controller:

isdn switch-type primary-net5

4. The controller config is the same as for any PRI connection:

controller E1 1/0
pri-group timeslots 1-31
description >>>>> Test of NEW BT PRI ports - out 338898 *** <<<<<
!

5. Now we need to configure D-channel to accept / send Data calls:

!
interface Serial1/0:15
description >>>>> Test of NEW BT PRI ports - out 338898 *** <<<<<
no ip address
encapsulation hdlc
isdn switch-type primary-net5
isdn map address .* plan unknown type unknown
isdn negotiate-bchan resend-setup
isdn bchan-number-order ascending
isdn sending-complete
isdn integrate calltype all
no cdp enable
!

6. Now we can proceed with the preparation for the dial-peer config, first let define the codecs we will use on IP side.
Please keep in mind that GW will actually do the filtering of the codes it will announce to the endpoints on both sides.

!
voice class codec 1000
codec preference 1 g711ulaw
codec preference 2 g711alaw
codec preference 3 g728
codec preference 4 g722-64
codec preference 5 g722-56
codec preference 6 g722-48
video codec h261
video codec h263
video codec h263+
video codec h264
!

7. This part is required to accept the incoming video calls, we need to have to provide the secondary numbers to the calling party, so they can call us on that numbers to add more bandwidth to the video call, that numbers will be sent out during ISO 13871 bonding stage. According to ISO 13871 only 7 digits will be sent. So there is no need or sense to configure more then 7 digits in the pool config. But you can configure less then 7 digits. The secondary called number will be crated from the primary called number by replacing the last digits with the numbers from the pool. So in case when only last 1 or 2 digits are different, you pool may have only 1 or 2 digit numbers in it.

!
voice class called number pool 3151
index 1 315140 - 315149

8. Now we need to apply that pool to the voice port to activate it:

!
voice-port 1/0:15
voice-class called-number-pool 3151
!

9. Now we are ready to proceed with the dial-peer configuration we need 4 of them, two incoming and two outgoing.
It is possible to use one POTS dial-peer as incoming and outgoing at the same time, but we will provide config for two of them for the sake of clarity:

!
dial-peer voice 99 pots
description default incoming video dial-peer
information-type video
incoming called-number 313300
bandwidth maximum 384
direct-inward-dial
!

!
dial-peer voice 9001 pots
description default outgoing video dial-peer
destination-pattern 00
information-type video
bandwidth maximum 384
port 1/0:15
forward-digits all
!

10. here is the example of the VOIP dial-peer, now we configured it as both - incoming and outgoing:

!
dial-peer voice 770 voip
description default incoming/outgoing voip dial-peer for all calls from GK w
destination-pattern 701...
voice-class codec 1000
session target ras
incoming called-number 00.
dtmf-relay h245-alphanumeric
!

==Related show Commands==
This section provides information you can use to confirm your configuration is working properly.

Certain show commands are supported by the [https://www.cisco.com/cgi-bin/Support/OutputInterpreter/home.pl Output Interpreter Tool (registered customers only)], which allows you to view an analysis of show command output.

show network-clocks
show isdn status
show dial-peer voice summary
show voice call status
show voice dsp

There also some useful commands to add and they can be used on All routers in production as well:

service nagle
service tcp-keepalives-in
service tcp-keepalives-out
service timestamps debug datetime msec
service timestamps log datetime msec

!
logging message-counter syslog
logging queue-limit 100000
logging buffered 5000000
logging rate-limit 10000
no logging console

And some very useful aliases :)

!
alias exec c conf t
alias exec r sh run
alias exec i sh ip ro
alias exec ib sh ip int brie
alias exec gs show run | s gatekeeper
alias exec ge sho gatekeeper end
alias exec sg sho gatekeeper
alias exec rs sh run | s
alias exec ri sh run | i
alias exec rb sh run | b
alias exec dp sh run | be dial-p
!

Enjoy :)

==Show running-config==

<pre>Add show running config of your device</pre>

==Related Information==
[http://www.cisco.com/web/psa/products/index.html Technical Support & Documentation - Cisco Systems]




[[Category:VoIP Configuration Examples]]
[[Category:Video Configuration Examples]]

Video on ISR 2800 3800 H.320 GW with ISO 13871 bonding Configuration Example

2011-02-08T11:58:39Z

Msamarts: /* Configuration */

==Introduction==

This is the basic config for any ISR router 2800 / 3800 series with PRI connection to PSTN / PBX and H.323 protocol on IP side.

==Design==

The example toplogy:

Tandberg VT - E1 PRI - PSTN - E1 PRI - ISR router - H.323 GK - Tandberg VT

==Configuration==

1. First we need to register GW and the video endpoint to the GK, we can run GK feature on the same router if we have IOS with GK feature for example - C2800NM-IPVOICE_IVS-M.
The most simple setup will be if we register endpoing with full E164 number and GW with the tech prefix, chousen in a way it will allow dialing to PSTN without any number transformation.
Assume PSTN will requre 00 for international call, in this case we can use the following config on GK:

!
gatekeeper
zone local video-98 mappets.com 10.52.218.98
no use-proxy video-98 default inbound-to terminal
no use-proxy video-98 default outbound-from terminal
no shutdown
!

There is no need to configure zone prefixes as GW will register with the tech prefix.
And VT will register with the full E164 number, so GK will always be able to resolve the them to IP.
For VT we need to allow direct calls to / from H.323 GW, so we disabling proxy requirement.

The matching GW config will be:

!
voice service voip
h323
emptycapability
h225 h245-address on-connect
call start slow
h245 tunnel disable
h245 timeout olc 30
!

Formally you will need only slow start and OLC timeout tuning. Because it may take some time for all ISDN secondary calls to get connected and for the BAS and codec negotiation to start, we need allow voip side to wait for some time. The 30 second timeout is reasonable setting, if we are talking about some VT like Tandberg or Polycom, they will have that settings by default. But if you have CallManager on IP side, you need to tune that timeouts via Service parameters:

H245 TCS Timeout 30

Media Exchange Interface Capability Timer 30

Media Exchange Timer 30

You may also consider to un-check the check-box on the GW config page:

"Wait for Far End H.245 Terminal Capability Set"

It usually good practice explicitly specify which interface will be used for H.323 signaling and if you register the GW to GK you will need to configure:

!
interface FastEthernet0/0
ip address 10.52.218.91 255.255.255.0
h323-gateway voip interface
h323-gateway voip id video-98 ipaddr 10.52.218.98 1719
h323-gateway voip h323-id ios-91-to-98
h323-gateway voip tech-prefix 00
h323-gateway voip bind srcaddr 10.52.218.91
!
gateway
!

Next we can proceed with the H.320 video GW configuration.

1. Specify the card type you will have:

card type e1 1 1

2. As video calls are actually the DATA calls by the nature of video content, we need to ensure the clocking is configured corectcly:

network-clock-participate slot 1
network-clock-participate wic 1
!
! Choose the one which required by your hardware setup.
!
network-clock-select 1 E1 1/0

3. You will need to specify the ISDN switch type before you can proceed with PRI group config on the controller:

isdn switch-type primary-net5

4. The controller config is the same as for any PRI connection:

controller E1 1/0
pri-group timeslots 1-31
description >>>>> Test of NEW BT PRI ports - out 338898 *** <<<<<
!

5. Now we need to configure D-channel to accept / send Data calls:

!
interface Serial1/0:15
description >>>>> Test of NEW BT PRI ports - out 338898 *** <<<<<
no ip address
encapsulation hdlc
isdn switch-type primary-net5
isdn map address .* plan unknown type unknown
isdn negotiate-bchan resend-setup
isdn bchan-number-order ascending
isdn sending-complete
isdn integrate calltype all
no cdp enable
!

6. Now we can proceed with the preparation for the dial-peer config, first let define the codecs we will use on IP side.
Please keep in mind that GW will actually do the filtering of the codes it will announce to the endpoints on both sides.

!
voice class codec 1000
codec preference 1 g711ulaw
codec preference 2 g711alaw
codec preference 3 g728
codec preference 4 g722-64
codec preference 5 g722-56
codec preference 6 g722-48
video codec h261
video codec h263
video codec h263+
video codec h264
!

7. This part is required to accept the incoming video calls, we need to have to provide the secondary numbers to the calling party, so they can call us on that numbers to add more bandwidth to the video call, that numbers will be sent out during ISO 13871 bonding stage. According to ISO 13871 only 7 digits will be sent. So there is no need or sense to configure more then 7 digits in the pool config. But you can configure less then 7 digits. The secondary called number will be crated from the primary called number by replacing the last digits with the numbers from the pool. So in case when only last 1 or 2 digits are different, you pool may have only 1 or 2 digit numbers in it.

!
voice class called number pool 3151
index 1 315140 - 315149

8. Now we need to apply that pool to the voice port to activate it:

!
voice-port 1/0:15
voice-class called-number-pool 3151
!

9. Now we are ready to proceed with the dial-peer configuration we need 4 of them, two incoming and two outgoing.
It is possible to use one POTS dial-peer as incoming and outgoing at the same time, but we will provide config for two of them for the sake of clarity:

!
dial-peer voice 99 pots
description default incoming video dial-peer
information-type video
incoming called-number 313300
bandwidth maximum 384
direct-inward-dial
!

!
dial-peer voice 9001 pots
description default outgoing video dial-peer
destination-pattern 00
information-type video
bandwidth maximum 384
port 1/0:15
forward-digits all
!

10. here is the example of the VOIP dial-peer, now we configured it as both - incoming and outgoing:

!
dial-peer voice 770 voip
description default incoming/outgoing voip dial-peer for all calls from GK w
destination-pattern 701...
voice-class codec 1000
session target ras
incoming called-number 00.
dtmf-relay h245-alphanumeric
!

==Related show Commands==
This section provides information you can use to confirm your configuration is working properly.

Certain show commands are supported by the [https://www.cisco.com/cgi-bin/Support/OutputInterpreter/home.pl Output Interpreter Tool (registered customers only)], which allows you to view an analysis of show command output.

show network-clocks
show isdn status
show dial-peer voice summary
show voice call status
show voice dsp

There also some useful commands to add and they can be used on All routers in production as well:

service nagle
service tcp-keepalives-in
service tcp-keepalives-out
service timestamps debug datetime msec
service timestamps log datetime msec

!
logging message-counter syslog
logging queue-limit 100000
logging buffered 5000000
logging rate-limit 10000
no logging console

And some very useful aliases :)

!
alias exec c conf t
alias exec r sh run
alias exec i sh ip ro
alias exec ib sh ip int brie
alias exec gs show run | s gatekeeper
alias exec ge sho gatekeeper end
alias exec sg sho gatekeeper
alias exec rs sh run | s
alias exec ri sh run | i
alias exec rb sh run | b
alias exec dp sh run | be dial-p
!

Enjoy :)

==Show running-config==

<pre>Add show running config of your device</pre>

==Related Information==
[http://www.cisco.com/web/psa/products/index.html Technical Support & Documentation - Cisco Systems]




[[Category:VoIP Configuration Examples]]
[[Category:Video Configuration Examples]]

Video Configuration Examples for IPIP GW or CUBE

2010-06-07T19:07:13Z

Msamarts:

==Introduction==

This is the basic config for any ISR router 2800 / 3800 series which runs IOS with CUBE and GK feature set.

==Design==

The example toplogy:

Tandberg VT A - H.323 GK zone A - CUBE - H.323 GK zone B - Tandberg VT B

Let assume that Tandberg A is located on Public Internet.
And we want to allow it to place calls to Tandberg B, or say MCU on an internal network only through CUBE.
Let name the zone A - PUBLICINET-with-IPIPGW
And zone B - MCU

We also have to make some assumptions about the dial-plan.
Let assume that all endpoints on the internet side will have numbers starting with 00 and all endpoints on internal network will have numbers starting with 2.

00* <-----CUBE------> 2*

We also assume that CUBE has two IP addresses.
One IP should be public IP reachable form internet, and naturally it also should be reachable from inside of your network.
In this example the internet will be represented by the subnet 33.33.33.0/24
The internal network can have IP from any private subnet range as 10.x.x.x, 172.x.x.x or 192.x.x.x

33.33.33.0 - CUBE - 10.x.x.x

==Configuration==

1. First we need to register GW and the video endpoints to the GK and we can run GK feature on the same router if we have IOS with GK feature for example - C2800NM-IPVOICE_IVS-M.
The most simple setup will be if we register endpoints with full E164 numbers to their corresponding zones and register the CUBE to the GK in public zone.
The CUBE should be registered to the zone where we want to force your endpoints to use CUBE as an access point to your network, so it will be out Public zone with real IP reachable from Public Internet.

!
gatekeeper
zone local PUBLICINET-with-IPIPGW test.com 33.33.33.1 invia PUBLICINET-with-IPIPGW outvia PUBLICINET-with-IPIPGW enable-intrazone
zone remote MCU mappets.com 10.52.218.98 1719
no zone subnet PUBLICINET-with-IPIPGW default enable
zone subnet PUBLICINET-with-IPIPGW 33.33.33.1/32 enable
zone subnet PUBLICINET-with-IPIPGW 33.33.33.101/32 enable
zone subnet PUBLICINET-with-IPIPGW 33.33.33.102/32 enable
zone subnet PUBLICINET-with-IPIPGW 33.33.33.0/24 enable
no zone subnet PUBLICINET-with-IPIPGW 172.168.0.0/16 enable
no zone subnet PUBLICINET-with-IPIPGW 192.0.0.0/8 enable
no zone subnet PUBLICINET-with-IPIPGW 10.0.0.0/8 enable
zone prefix MCU 2*
no use-proxy PUBLICINET-with-IPIPGW default inbound-to terminal
no use-proxy PUBLICINET-with-IPIPGW default outbound-from terminal
no shutdown
!

To have control over registration - we used "zone subnet" commands.
First we need them to disable registration of internal endpoints to the external zone.
And we also can use tighter restrictions - if we want to allow only some specific endpoints form internet to register the GK.
For example the command "zone subnet PUBLICINET-with-IPIPGW 33.33.33.101/32 enable" will allow to register endpoint with IP 33.33.33.101.

The matching CUBE config will be:

!
voice service voip
allow-connections h323 to h323

!
interface FastEthernet0/0
ip address 10.52.218.130 255.255.255.0
!
This interface is used only for routing, it is not involved in H.323 signaling.
!
interface FastEthernet0/1.33
encapsulation dot1Q 333
ip address 33.33.33.1 255.255.255.0
h323-gateway voip interface
h323-gateway voip id PUBLICINET-with-IPIPGW ipaddr 33.33.33.1 1719
h323-gateway voip h323-id IPIPGW-130
h323-gateway voip tech-prefix 130
h323-gateway voip bind srcaddr 33.33.33.1
!
This interface is used for H.323 signaling, so it have to be reachable for endpoints on the Internet as well as from internal network.

The matching remote GK config(we can run other GK on any other router in the network):
!
gatekeeper
zone local MCU mappets.com 10.52.218.98
zone remote PUBLICINET-with-IPIPGW test.com 33.33.33.1 1719
zone prefix PUBLICINET-with-IPIPGW 00*
no use-proxy MCU default inbound-to terminal
no use-proxy MCU default outbound-from terminal
no shutdown
!

Here we can register any internal H.323 endpoints like Tandberg Video terminals or MCU for conferencing.

The final step would be the example of the VOIP dial-peers. Here we configured two dial-peers - but each of them play the role of incoming and outgoing dial-peer at the same time.

!
dial-peer voice 2000 voip
destination-pattern 2...
session target ras
incoming called-number 2...
dtmf-relay h245-alphanumeric
codec transparent
no vad
!
dial-peer voice 1000 voip
destination-pattern 00
session target ras
incoming called-number 00
dtmf-relay h245-alphanumeric
codec transparent
no vad
!

The only specific part for video in this whole example is the "codec transparent" command :)

==Related show Commands==
This section provides information you can use to confirm your configuration is working properly.

Certain show commands are supported by the [https://www.cisco.com/cgi-bin/Support/OutputInterpreter/home.pl Output Interpreter Tool (registered customers only)], which allows you to view an analysis of show command output.

show dial-peer voice summary
show voice call status

There also some useful commands to add and they can be used on All routers in production as well:

service nagle
service tcp-keepalives-in
service tcp-keepalives-out
service timestamps debug datetime msec
service timestamps log datetime msec

!
logging message-counter syslog
logging queue-limit 100000
logging buffered 5000000
logging rate-limit 10000
no logging console

And some very useful aliases :)

!
alias exec c conf t
alias exec r sh run
alias exec i sh ip ro
alias exec ib sh ip int brie
alias exec gs show run | s gatekeeper
alias exec ge sho gatekeeper end
alias exec sg sho gatekeeper
alias exec rs sh run | s
alias exec ri sh run | i
alias exec rb sh run | b
alias exec dp sh run | be dial-p
!

Enjoy :)

==Show running-config==

<pre>Add show running config of your device</pre>

==Related Information==
[http://www.cisco.com/web/psa/products/index.html Technical Support & Documentation - Cisco Systems]





[[Category:Configuration Examples]]
[[Category:VoIP Configuration Examples]]
[[Category:Video Configuration Examples]]

Video Configuration Examples for IPIP GW or CUBE

2010-06-07T17:59:56Z

Msamarts:

[[Category:Video Configuration Examples]]

Video Configuration Examples

2010-06-07T17:59:21Z

Msamarts: Video Configuration Examples moved to Video Configuration Examples for IPIP GW or CUBE

#REDIRECT [[Video Configuration Examples for IPIP GW or CUBE]]

Video Configuration Examples for IPIP GW or CUBE

2010-06-07T17:59:21Z

Msamarts: Video Configuration Examples moved to Video Configuration Examples for IPIP GW or CUBE

[[Category:Configuration Examples]]

Video on ISR 2800 3800 H.320 GW with ISO 13871 bonding Configuration Example

2010-06-07T17:30:24Z

Msamarts:

==Introduction==

This is the basic config for any ISR router 2800 / 3800 series with PRI connection to PSTN / PBX and H.323 protocol on IP side.

==Design==

The example toplogy:

Tandberg VT - E1 PRI - PSTN - E1 PRI - ISR router - H.323 GK - Tandberg VT

==Configuration==

1. First we need to register GW and the video endpoint to the GK, we can run GK feature on the same router if we have IOS with GK feature for example - C2800NM-IPVOICE_IVS-M.
The most simple setup will be if we register endpoing with full E164 number and GW with the tech prefix, chousen in a way it will allow dialing to PSTN without any number transformation.
Assume PSTN will requre 00 for international call, in this case we can use the following config on GK:

!
gatekeeper
zone local video-98 mappets.com 10.52.218.98
no use-proxy video-98 default inbound-to terminal
no use-proxy video-98 default outbound-from terminal
no shutdown
!

There is no need to configure zone prefixes as GW will register with the tech prefix.
And VT will register with the full E164 number, so GK will always be able to resolve the them to IP.
For VT we need to allow direct calls to / from H.323 GW, so we disabling proxy requirement.

The matching GW config will be:

!
interface FastEthernet0/0
ip address 10.52.218.91 255.255.255.0
h323-gateway voip interface
h323-gateway voip id video-98 ipaddr 10.52.218.98 1719
h323-gateway voip h323-id ios-91-to-98
h323-gateway voip tech-prefix 00
h323-gateway voip bind srcaddr 10.52.218.91
!
gateway
!

Next we can proceed with the H.320 video GW configuration.

1. Specify the card type you will have:

card type e1 1 1

2. As video calls are actually the DATA calls by the nature of video content, we need to ensure the clocking is configured corectcly:

network-clock-participate slot 1
network-clock-participate wic 1
!
! Choose the one which required by your hardware setup.
!
network-clock-select 1 E1 1/0

3. You will need to specify the ISDN switch type before you can proceed with PRI group config on the controller:

isdn switch-type primary-net5

4. The controller config is the same as for any PRI connection:

controller E1 1/0
pri-group timeslots 1-31
description >>>>> Test of NEW BT PRI ports - out 338898 *** <<<<<
!

5. Now we need to configure D-channel to accept / send Data calls:

!
interface Serial1/0:15
description >>>>> Test of NEW BT PRI ports - out 338898 *** <<<<<
no ip address
encapsulation hdlc
isdn switch-type primary-net5
isdn map address .* plan unknown type unknown
isdn negotiate-bchan resend-setup
isdn bchan-number-order ascending
isdn sending-complete
isdn integrate calltype all
no cdp enable
!

6. Now we can proceed with the preparation for the dial-peer config, first let define the codecs we will use on IP side.
Please keep in mind that GW will actually do the filtering of the codes it will announce to the endpoints on both sides.

!
voice class codec 1000
codec preference 1 g711ulaw
codec preference 2 g711alaw
codec preference 3 g728
codec preference 4 g722-64
codec preference 5 g722-56
codec preference 6 g722-48
video codec h261
video codec h263
video codec h263+
video codec h264
!

7. This part is required to accept the incoming video calls, we need to have to provide the secondary numbers to the calling party, so they can call us on that numbers to add more bandwidth to the video call, that numbers will be sent out during ISO 13871 bonding stage.

!
voice class called number pool 3151
index 1 315140 - 315149

8. Now we need to apply that pool to the voice port to activate it:

!
voice-port 1/0:15
voice-class called-number-pool 3151
!

9. Now we are ready to proceed with the dial-peer configuration we need 4 of them, two incoming and two outgoing.
It is possible to use one POTS dial-peer as incoming and outgoing at the same time, but we will provide config for two of them for the sake of clarity:

!
dial-peer voice 99 pots
description default incoming video dial-peer
information-type video
incoming called-number 313300
bandwidth maximum 384
direct-inward-dial
!

!
dial-peer voice 9001 pots
description default outgoing video dial-peer
destination-pattern 00
information-type video
bandwidth maximum 384
port 1/0:15
forward-digits all
!

10. here is the example of the VOIP dial-peer, now we configured it as both - incoming and outgoing:

!
dial-peer voice 770 voip
description default incoming/outgoing voip dial-peer for all calls from GK w
destination-pattern 701...
voice-class codec 1000
session target ras
incoming called-number 00.
dtmf-relay h245-alphanumeric
!

==Related show Commands==
This section provides information you can use to confirm your configuration is working properly.

Certain show commands are supported by the [https://www.cisco.com/cgi-bin/Support/OutputInterpreter/home.pl Output Interpreter Tool (registered customers only)], which allows you to view an analysis of show command output.

show network-clocks
show isdn status
show dial-peer voice summary
show voice call status
show voice dsp

There also some useful commands to add and they can be used on All routers in production as well:

service nagle
service tcp-keepalives-in
service tcp-keepalives-out
service timestamps debug datetime msec
service timestamps log datetime msec

!
logging message-counter syslog
logging queue-limit 100000
logging buffered 5000000
logging rate-limit 10000
no logging console

And some very useful aliases :)

!
alias exec c conf t
alias exec r sh run
alias exec i sh ip ro
alias exec ib sh ip int brie
alias exec gs show run | s gatekeeper
alias exec ge sho gatekeeper end
alias exec sg sho gatekeeper
alias exec rs sh run | s
alias exec ri sh run | i
alias exec rb sh run | b
alias exec dp sh run | be dial-p
!

Enjoy :)

==Show running-config==

<pre>Add show running config of your device</pre>

==Related Information==
[http://www.cisco.com/web/psa/products/index.html Technical Support & Documentation - Cisco Systems]





[[Category:Configuration Examples]]
[[Category:VoIP Configuration Examples]]
[[Category:Video Configuration Examples]]

Video on ISR 2800 3800 H.320 GW with ISO 13871 bonding Configuration Example

2010-06-05T17:47:37Z

Msamarts:

==Introduction==

This is the basic config for any ISR router 2800 / 3800 series with PRI connection to PSTN / PBX and H.323 protocol on IP side.

==Design==

The example toplogy:

Tandberg VT - E1 PRI - PSTN - E1 PRI - ISR router - H.323 GK - Tandberg VT

==Configuration==

1. First we need to register GW and the video endpoint to the GK, we can run GK feature on the same router if we have IOS with GK feature for example - C2800NM-IPVOICE_IVS-M.
The most simple setup will be if we register endpoing with full E164 number and GW with the tech prefix, chousen in a way it will allow dialing to PSTN without any number transformation.
Assume PSTN will requre 00 for international call, in this case we can use the following config on GK:

!
gatekeeper
zone local video-98 mappets.com 10.52.218.98
no use-proxy video-98 default inbound-to terminal
no use-proxy video-98 default outbound-from terminal
no shutdown
!

There is no need to configure zone prefixes as GW will register with the tech prefix.
And VT will register with the full E164 number, so GK will always be able to resolve the them to IP.
For VT we need to allow direct calls to / from H.323 GW, so we disabling proxy requirement.

The matching GW config will be:

!
interface FastEthernet0/0
ip address 10.52.218.91 255.255.255.0
h323-gateway voip interface
h323-gateway voip id video-98 ipaddr 10.52.218.98 1719
h323-gateway voip h323-id ios-91-to-98
h323-gateway voip tech-prefix 00
h323-gateway voip bind srcaddr 10.52.218.91
!
gateway
!

Next we can proceed with the H.320 video GW configuration.

1. Specify the card type you will have:

card type e1 1 1

2. As video calls are actually the DATA calls by the nature of video content, we need to ensure the clocking is configured corectcly:

network-clock-participate slot 1
network-clock-participate wic 1
!
! Choose the one which required by your hardware setup.
!
network-clock-select 1 E1 1/0

3. You will need to specify the ISDN switch type before you can proceed with PRI group config on the controller:

isdn switch-type primary-net5

4. The controller config is the same as for any PRI connection:

controller E1 1/0
pri-group timeslots 1-31
description >>>>> Test of NEW BT PRI ports - out 338898 *** <<<<<
!

5. Now we need to configure D-channel to accept / send Data calls:

!
interface Serial1/0:15
description >>>>> Test of NEW BT PRI ports - out 338898 *** <<<<<
no ip address
encapsulation hdlc
isdn switch-type primary-net5
isdn map address .* plan unknown type unknown
isdn negotiate-bchan resend-setup
isdn bchan-number-order ascending
isdn sending-complete
isdn integrate calltype all
no cdp enable
!

6. Now we can proceed with the preparation for the dial-peer config, first let define the codecs we will use on IP side.
Please keep in mind that GW will actually do the filtering of the codes it will announce to the endpoints on both sides.

!
voice class codec 1000
codec preference 1 g711ulaw
codec preference 2 g711alaw
codec preference 3 g728
codec preference 4 g722-64
codec preference 5 g722-56
codec preference 6 g722-48
video codec h261
video codec h263
video codec h263+
video codec h264
!

7. This part is required to accept the incoming video calls, we need to have to provide the secondary numbers to the calling party, so they can call us on that numbers to add more bandwidth to the video call, that numbers will be sent out during ISO 13871 bonding stage.

!
voice class called number pool 3151
index 1 315140 - 315149

8. Now we need to apply that pool to the voice port to activate it:

!
voice-port 1/0:15
voice-class called-number-pool 3151
!

9. Now we are ready to proceed with the dial-peer configuration we need 4 of them, two incoming and two outgoing.
It is possible to use one POTS dial-peer as incoming and outgoing at the same time, but we will provide config for two of them for the sake of clarity:

!
dial-peer voice 99 pots
description default incoming video dial-peer
information-type video
incoming called-number 313300
bandwidth maximum 384
direct-inward-dial
!

!
dial-peer voice 9001 pots
description default outgoing video dial-peer
destination-pattern 00
information-type video
bandwidth maximum 384
port 1/0:15
forward-digits all
!

10. here is the example of the VOIP dial-peer, now we configured it as both - incoming and outgoing:

!
dial-peer voice 770 voip
description default incoming/outgoing voip dial-peer for all calls from GK w
destination-pattern 701...
voice-class codec 1000
session target ras
incoming called-number 00.
dtmf-relay h245-alphanumeric
!

==Related show Commands==
This section provides information you can use to confirm your configuration is working properly.

Certain show commands are supported by the [https://www.cisco.com/cgi-bin/Support/OutputInterpreter/home.pl Output Interpreter Tool (registered customers only)], which allows you to view an analysis of show command output.

show network-clocks
show isdn status
show dial-peer voice summary
show voice call status
show voice dsp

There also some useful commands to add and they can be used on All routers in production as well:

service nagle
service tcp-keepalives-in
service tcp-keepalives-out
service timestamps debug datetime msec
service timestamps log datetime msec

!
logging message-counter syslog
logging queue-limit 100000
logging buffered 5000000
logging rate-limit 10000
no logging console

And some very useful aliases :)

!
alias exec c conf t
alias exec r sh run
alias exec i sh ip ro
alias exec ib sh ip int brie
alias exec gs show run | s gatekeeper
alias exec ge sho gatekeeper end
alias exec sg sho gatekeeper
alias exec rs sh run | s
alias exec ri sh run | i
alias exec rb sh run | b
alias exec dp sh run | be dial-p
!

Enjoy :)

==Show running-config==

<pre>Add show running config of your device</pre>

==Related Information==
[http://www.cisco.com/web/psa/products/index.html Technical Support & Documentation - Cisco Systems]





[[Category:example]]
[[Category:video]]
[[Category:H.320]]
[[Category:ISR]]
[[Category:2800]]
[[Category:gatekeeper]]
[[Category:config]]
[[Category:VoIP Configuration Examples]]
[[Category:Configuration Examples]]
[[Category:Video Configuration Examples]]

Video Configuration Examples for IPIP GW or CUBE

2010-06-05T17:46:22Z

Msamarts:

[[Category:Configuration Examples]]

Video Configuration Examples for IPIP GW or CUBE

2010-06-05T17:33:31Z

Msamarts:

Video Configuration Examples

[[Category:Configuration Examples]]

Video Configuration Examples for IPIP GW or CUBE

2010-06-05T17:25:21Z

Msamarts: Video Configuration Examples

[[Category:Configuration Examples]]

Video on ISR 2800 3800 H.320 with ISO 13871 bonding Configuration Example

2010-06-05T17:10:34Z

Msamarts: Video on ISR 2800 3800 H.320 with ISO 13871 bonding Configuration Example moved to Video on ISR 2800 3800 H.320 GW with ISO 13871 bonding Configuration Example: Video category

#REDIRECT [[Video on ISR 2800 3800 H.320 GW with ISO 13871 bonding Configuration Example]]

Video on ISR 2800 3800 H.320 GW with ISO 13871 bonding Configuration Example

2010-06-05T17:10:34Z

Msamarts: Video on ISR 2800 3800 H.320 with ISO 13871 bonding Configuration Example moved to Video on ISR 2800 3800 H.320 GW with ISO 13871 bonding Configuration Example: Video category

==Introduction==

This is the basic config for any ISR router 2800 / 3800 series with PRI connection to PSTN / PBX and H.323 protocol on IP side.

==Design==

The example toplogy:

Tandberg VT - E1 PRI - PSTN - E1 PRI - ISR router - H.323 GK - Tandberg VT

==Configuration==

1. First we need to register GW and the video endpoint to the GK, we can run GK feature on the same router if we have IOS with GK feature for example - C2800NM-IPVOICE_IVS-M.
The most simple setup will be if we register endpoing with full E164 number and GW with the tech prefix, chousen in a way it will allow dialing to PSTN without any number transformation.
Assume PSTN will requre 00 for international call, in this case we can use the following config on GK:

!
gatekeeper
zone local video-98 mappets.com 10.52.218.98
no use-proxy video-98 default inbound-to terminal
no use-proxy video-98 default outbound-from terminal
no shutdown
!

There is no need to configure zone prefixes as GW will register with the tech prefix.
And VT will register with the full E164 number, so GK will always be able to resolve the them to IP.
For VT we need to allow direct calls to / from H.323 GW, so we disabling proxy requirement.

The matching GW config will be:

!
interface FastEthernet0/0
ip address 10.52.218.91 255.255.255.0
h323-gateway voip interface
h323-gateway voip id video-98 ipaddr 10.52.218.98 1719
h323-gateway voip h323-id ios-91-to-98
h323-gateway voip tech-prefix 00
h323-gateway voip bind srcaddr 10.52.218.91
!
gateway
!

Next we can proceed with the H.320 video GW configuration.

1. Specify the card type you will have:

card type e1 1 1

2. As video calls are actually the DATA calls by the nature of video content, we need to ensure the clocking is configured corectcly:

network-clock-participate slot 1
network-clock-participate wic 1
!
! Choose the one which required by your hardware setup.
!
network-clock-select 1 E1 1/0

3. You will need to specify the ISDN switch type before you can proceed with PRI group config on the controller:

isdn switch-type primary-net5

4. The controller config is the same as for any PRI connection:

controller E1 1/0
pri-group timeslots 1-31
description >>>>> Test of NEW BT PRI ports - out 338898 *** <<<<<
!

5. Now we need to configure D-channel to accept / send Data calls:

!
interface Serial1/0:15
description >>>>> Test of NEW BT PRI ports - out 338898 *** <<<<<
no ip address
encapsulation hdlc
isdn switch-type primary-net5
isdn map address .* plan unknown type unknown
isdn negotiate-bchan resend-setup
isdn bchan-number-order ascending
isdn sending-complete
isdn integrate calltype all
no cdp enable
!

6. Now we can proceed with the preparation for the dial-peer config, first let define the codecs we will use on IP side.
Please keep in mind that GW will actually do the filtering of the codes it will announce to the endpoints on both sides.

!
voice class codec 1000
codec preference 1 g711ulaw
codec preference 2 g711alaw
codec preference 3 g728
codec preference 4 g722-64
codec preference 5 g722-56
codec preference 6 g722-48
video codec h261
video codec h263
video codec h263+
video codec h264
!

7. This part is required to accept the incoming video calls, we need to have to provide the secondary numbers to the calling party, so they can call us on that numbers to add more bandwidth to the video call, that numbers will be sent out during ISO 13871 bonding stage.

!
voice class called number pool 3151
index 1 315140 - 315149

8. Now we need to apply that pool to the voice port to activate it:

!
voice-port 1/0:15
voice-class called-number-pool 3151
!

9. Now we are ready to proceed with the dial-peer configuration we need 4 of them, two incoming and two outgoing.
It is possible to use one POTS dial-peer as incoming and outgoing at the same time, but we will provide config for two of them for the sake of clarity:

!
dial-peer voice 99 pots
description default incoming video dial-peer
information-type video
incoming called-number 313300
bandwidth maximum 384
direct-inward-dial
!

!
dial-peer voice 9001 pots
description default outgoing video dial-peer
destination-pattern 00
information-type video
bandwidth maximum 384
port 1/0:15
forward-digits all
!

10. here is the example of the VOIP dial-peer, now we configured it as both - incoming and outgoing:

!
dial-peer voice 770 voip
description default incoming/outgoing voip dial-peer for all calls from GK w
destination-pattern 701...
voice-class codec 1000
session target ras
incoming called-number 00.
dtmf-relay h245-alphanumeric
!

==Related show Commands==
This section provides information you can use to confirm your configuration is working properly.

Certain show commands are supported by the [https://www.cisco.com/cgi-bin/Support/OutputInterpreter/home.pl Output Interpreter Tool (registered customers only)], which allows you to view an analysis of show command output.

show network-clocks
show isdn status
show dial-peer voice summary
show voice call status
show voice dsp

There also some useful commands to add and they can be used on All routers in production as well:

service nagle
service tcp-keepalives-in
service tcp-keepalives-out
service timestamps debug datetime msec
service timestamps log datetime msec

!
logging message-counter syslog
logging queue-limit 100000
logging buffered 5000000
logging rate-limit 10000
no logging console

And some very useful aliases :)

!
alias exec c conf t
alias exec r sh run
alias exec i sh ip ro
alias exec ib sh ip int brie
alias exec gs show run | s gatekeeper
alias exec ge sho gatekeeper end
alias exec sg sho gatekeeper
alias exec rs sh run | s
alias exec ri sh run | i
alias exec rb sh run | b
alias exec dp sh run | be dial-p
!

Enjoy :)

==Show running-config==

<pre>Add show running config of your device</pre>

==Related Information==
[http://www.cisco.com/web/psa/products/index.html Technical Support & Documentation - Cisco Systems]





[[Category:example]]
[[Category:video]]
[[Category:H.320]]
[[Category:ISR]]
[[Category:2800]]
[[Category:gatekeeper]]
[[Category:config]]
[[Category:VoIP Configuration Examples]]
[[Category:Configuration Examples]]

Video on ISR 2800 3800 H.320 GW with ISO 13871 bonding Configuration Example

2010-06-05T17:09:16Z

Msamarts:

==Introduction==

This is the basic config for any ISR router 2800 / 3800 series with PRI connection to PSTN / PBX and H.323 protocol on IP side.

==Design==

The example toplogy:

Tandberg VT - E1 PRI - PSTN - E1 PRI - ISR router - H.323 GK - Tandberg VT

==Configuration==

1. First we need to register GW and the video endpoint to the GK, we can run GK feature on the same router if we have IOS with GK feature for example - C2800NM-IPVOICE_IVS-M.
The most simple setup will be if we register endpoing with full E164 number and GW with the tech prefix, chousen in a way it will allow dialing to PSTN without any number transformation.
Assume PSTN will requre 00 for international call, in this case we can use the following config on GK:

!
gatekeeper
zone local video-98 mappets.com 10.52.218.98
no use-proxy video-98 default inbound-to terminal
no use-proxy video-98 default outbound-from terminal
no shutdown
!

There is no need to configure zone prefixes as GW will register with the tech prefix.
And VT will register with the full E164 number, so GK will always be able to resolve the them to IP.
For VT we need to allow direct calls to / from H.323 GW, so we disabling proxy requirement.

The matching GW config will be:

!
interface FastEthernet0/0
ip address 10.52.218.91 255.255.255.0
h323-gateway voip interface
h323-gateway voip id video-98 ipaddr 10.52.218.98 1719
h323-gateway voip h323-id ios-91-to-98
h323-gateway voip tech-prefix 00
h323-gateway voip bind srcaddr 10.52.218.91
!
gateway
!

Next we can proceed with the H.320 video GW configuration.

1. Specify the card type you will have:

card type e1 1 1

2. As video calls are actually the DATA calls by the nature of video content, we need to ensure the clocking is configured corectcly:

network-clock-participate slot 1
network-clock-participate wic 1
!
! Choose the one which required by your hardware setup.
!
network-clock-select 1 E1 1/0

3. You will need to specify the ISDN switch type before you can proceed with PRI group config on the controller:

isdn switch-type primary-net5

4. The controller config is the same as for any PRI connection:

controller E1 1/0
pri-group timeslots 1-31
description >>>>> Test of NEW BT PRI ports - out 338898 *** <<<<<
!

5. Now we need to configure D-channel to accept / send Data calls:

!
interface Serial1/0:15
description >>>>> Test of NEW BT PRI ports - out 338898 *** <<<<<
no ip address
encapsulation hdlc
isdn switch-type primary-net5
isdn map address .* plan unknown type unknown
isdn negotiate-bchan resend-setup
isdn bchan-number-order ascending
isdn sending-complete
isdn integrate calltype all
no cdp enable
!

6. Now we can proceed with the preparation for the dial-peer config, first let define the codecs we will use on IP side.
Please keep in mind that GW will actually do the filtering of the codes it will announce to the endpoints on both sides.

!
voice class codec 1000
codec preference 1 g711ulaw
codec preference 2 g711alaw
codec preference 3 g728
codec preference 4 g722-64
codec preference 5 g722-56
codec preference 6 g722-48
video codec h261
video codec h263
video codec h263+
video codec h264
!

7. This part is required to accept the incoming video calls, we need to have to provide the secondary numbers to the calling party, so they can call us on that numbers to add more bandwidth to the video call, that numbers will be sent out during ISO 13871 bonding stage.

!
voice class called number pool 3151
index 1 315140 - 315149

8. Now we need to apply that pool to the voice port to activate it:

!
voice-port 1/0:15
voice-class called-number-pool 3151
!

9. Now we are ready to proceed with the dial-peer configuration we need 4 of them, two incoming and two outgoing.
It is possible to use one POTS dial-peer as incoming and outgoing at the same time, but we will provide config for two of them for the sake of clarity:

!
dial-peer voice 99 pots
description default incoming video dial-peer
information-type video
incoming called-number 313300
bandwidth maximum 384
direct-inward-dial
!

!
dial-peer voice 9001 pots
description default outgoing video dial-peer
destination-pattern 00
information-type video
bandwidth maximum 384
port 1/0:15
forward-digits all
!

10. here is the example of the VOIP dial-peer, now we configured it as both - incoming and outgoing:

!
dial-peer voice 770 voip
description default incoming/outgoing voip dial-peer for all calls from GK w
destination-pattern 701...
voice-class codec 1000
session target ras
incoming called-number 00.
dtmf-relay h245-alphanumeric
!

==Related show Commands==
This section provides information you can use to confirm your configuration is working properly.

Certain show commands are supported by the [https://www.cisco.com/cgi-bin/Support/OutputInterpreter/home.pl Output Interpreter Tool (registered customers only)], which allows you to view an analysis of show command output.

show network-clocks
show isdn status
show dial-peer voice summary
show voice call status
show voice dsp

There also some useful commands to add and they can be used on All routers in production as well:

service nagle
service tcp-keepalives-in
service tcp-keepalives-out
service timestamps debug datetime msec
service timestamps log datetime msec

!
logging message-counter syslog
logging queue-limit 100000
logging buffered 5000000
logging rate-limit 10000
no logging console

And some very useful aliases :)

!
alias exec c conf t
alias exec r sh run
alias exec i sh ip ro
alias exec ib sh ip int brie
alias exec gs show run | s gatekeeper
alias exec ge sho gatekeeper end
alias exec sg sho gatekeeper
alias exec rs sh run | s
alias exec ri sh run | i
alias exec rb sh run | b
alias exec dp sh run | be dial-p
!

Enjoy :)

==Show running-config==

<pre>Add show running config of your device</pre>

==Related Information==
[http://www.cisco.com/web/psa/products/index.html Technical Support & Documentation - Cisco Systems]





[[Category:example]]
[[Category:video]]
[[Category:H.320]]
[[Category:ISR]]
[[Category:2800]]
[[Category:gatekeeper]]
[[Category:config]]
[[Category:VoIP Configuration Examples]]
[[Category:Configuration Examples]]

Cisco ISR H.320 Video with ISO 13871 bonding Configuration Example

2010-06-05T16:58:43Z

Msamarts: Cisco ISR H.320 Video with ISO 13871 bonding Configuration Example moved to Video on ISR 2800 3800 H.320 with ISO 13871 bonding Configuration Example: Vide category

#REDIRECT [[Video on ISR 2800 3800 H.320 with ISO 13871 bonding Configuration Example]]

Video on ISR 2800 3800 H.320 GW with ISO 13871 bonding Configuration Example

2010-06-05T16:58:43Z

Msamarts: Cisco ISR H.320 Video with ISO 13871 bonding Configuration Example moved to Video on ISR 2800 3800 H.320 with ISO 13871 bonding Configuration Example: Vide category

==Introduction==

This is the basic config for any ISR router 2800 / 3800 series with PRI connection to PSTN / PBX and H.323 protocol on IP side.

==Design==

The example toplogy:

Tandberg VT - E1 PRI - PSTN - E1 PRI - ISR router - H.323 GK - Tandberg VT

==Configuration==

1. First we need to register GW and the video endpoint to the GK.
The most simple setup will be if we register endpoing with full E164 number and GW with the tech prefix, chousen in a way it will allow dialing to PSTN without any number transformation.
Assume PSTN will requre 00 for international call, in this case we can use the following config on GK:

!
gatekeeper
zone local video-98 mappets.com 10.52.218.98
no use-proxy video-98 default inbound-to terminal
no use-proxy video-98 default outbound-from terminal
no shutdown
!

There is no need to configure zone prefixes as GW will register with the tech prefix.
And VT will register with the full E164 number, so GK will always be able to resolve the them to IP.
For VT we need to allow direct calls to / from H.323 GW, so we disabling proxy requirement.

The matching GW config will be:

!
interface FastEthernet0/0
ip address 10.52.218.91 255.255.255.0
h323-gateway voip interface
h323-gateway voip id video-98 ipaddr 10.52.218.98 1719
h323-gateway voip h323-id ios-91-to-98
h323-gateway voip tech-prefix 00
h323-gateway voip bind srcaddr 10.52.218.91
!
gateway
!

Next we can proceed with the H.320 video GW configuration.

1. Specify the card type you will have:

card type e1 1 1

2. As video calls are actually the DATA calls by the nature of video content, we need to ensure the clocking is configured corectcly:

network-clock-participate slot 1
network-clock-participate wic 1
!
! Choose the one which required by your hardware setup.
!
network-clock-select 1 E1 1/0

3. You will need to specify the ISDN switch type before you can proceed with PRI group config on the controller:

isdn switch-type primary-net5

4. The controller config is the same as for any PRI connection:

controller E1 1/0
pri-group timeslots 1-31
description >>>>> Test of NEW BT PRI ports - out 338898 *** <<<<<
!

5. Now we need to configure D-channel to accept / send Data calls:

!
interface Serial1/0:15
description >>>>> Test of NEW BT PRI ports - out 338898 *** <<<<<
no ip address
encapsulation hdlc
isdn switch-type primary-net5
isdn map address .* plan unknown type unknown
isdn negotiate-bchan resend-setup
isdn bchan-number-order ascending
isdn sending-complete
isdn integrate calltype all
no cdp enable
!

6. Now we can proceed with the preparation for the dial-peer config, first let define the codecs we will use on IP side.
Please keep in mind that GW will actually do the filtering of the codes it will announce to the endpoints on both sides.

!
voice class codec 1000
codec preference 1 g711ulaw
codec preference 2 g711alaw
codec preference 3 g728
codec preference 4 g722-64
codec preference 5 g722-56
codec preference 6 g722-48
video codec h261
video codec h263
video codec h263+
video codec h264
!

7. This part is required to accept the incoming video calls, we need to have to provide the secondary numbers to the calling party, so they can call us on that numbers to add more bandwidth to the video call, that numbers will be sent out during ISO 13871 bonding stage.

!
voice class called number pool 3151
index 1 315140 - 315149

8. Now we need to apply that pool to the voice port to activate it:

!
voice-port 1/0:15
voice-class called-number-pool 3151
!

9. Now we are ready to proceed with the dial-peer configuration we need 4 of them, two incoming and two outgoing.
It is possible to use one POTS dial-peer as incoming and outgoing at the same time, but we will provide config for two of them for the sake of clarity:

!
dial-peer voice 99 pots
description default incoming video dial-peer
information-type video
incoming called-number 313300
bandwidth maximum 384
direct-inward-dial
!

!
dial-peer voice 9001 pots
description default outgoing video dial-peer
destination-pattern 00
information-type video
bandwidth maximum 384
port 1/0:15
forward-digits all
!

10. here is the example of the VOIP dial-peer, now we configured it as both - incoming and outgoing:

!
dial-peer voice 770 voip
description default incoming/outgoing voip dial-peer for all calls from GK w
destination-pattern 701...
voice-class codec 1000
session target ras
incoming called-number 00.
dtmf-relay h245-alphanumeric
!

==Related show Commands==
This section provides information you can use to confirm your configuration is working properly.

Certain show commands are supported by the [https://www.cisco.com/cgi-bin/Support/OutputInterpreter/home.pl Output Interpreter Tool (registered customers only)], which allows you to view an analysis of show command output.

show network-clocks
show isdn status
show dial-peer voice summary
show voice call status
show voice dsp

There also some useful commands to add and they can be used on All routers in production as well:

service nagle
service tcp-keepalives-in
service tcp-keepalives-out
service timestamps debug datetime msec
service timestamps log datetime msec

!
logging message-counter syslog
logging queue-limit 100000
logging buffered 5000000
logging rate-limit 10000
no logging console

And some very useful aliases :)

!
alias exec c conf t
alias exec r sh run
alias exec i sh ip ro
alias exec ib sh ip int brie
alias exec gs show run | s gatekeeper
alias exec ge sho gatekeeper end
alias exec sg sho gatekeeper
alias exec rs sh run | s
alias exec ri sh run | i
alias exec rb sh run | b
alias exec dp sh run | be dial-p
!

Enjoy :)

==Show running-config==

<pre>Add show running config of your device</pre>

==Related Information==
[http://www.cisco.com/web/psa/products/index.html Technical Support & Documentation - Cisco Systems]





[[Category:example]]
[[Category:video]]
[[Category:ISR]]
[[Category:2800]]
[[Category:gatekeeper]]
[[Category:config]]
[[Category:VoIP Configuration Examples]]
[[Category:Configuration Examples]]

Video on ISR 2800 3800 H.320 GW with ISO 13871 bonding Configuration Example

2010-06-05T16:55:55Z

Msamarts:

==Introduction==

This is the basic config for any ISR router 2800 / 3800 series with PRI connection to PSTN / PBX and H.323 protocol on IP side.

==Design==

The example toplogy:

Tandberg VT - E1 PRI - PSTN - E1 PRI - ISR router - H.323 GK - Tandberg VT

==Configuration==

1. First we need to register GW and the video endpoint to the GK.
The most simple setup will be if we register endpoing with full E164 number and GW with the tech prefix, chousen in a way it will allow dialing to PSTN without any number transformation.
Assume PSTN will requre 00 for international call, in this case we can use the following config on GK:

!
gatekeeper
zone local video-98 mappets.com 10.52.218.98
no use-proxy video-98 default inbound-to terminal
no use-proxy video-98 default outbound-from terminal
no shutdown
!

There is no need to configure zone prefixes as GW will register with the tech prefix.
And VT will register with the full E164 number, so GK will always be able to resolve the them to IP.
For VT we need to allow direct calls to / from H.323 GW, so we disabling proxy requirement.

The matching GW config will be:

!
interface FastEthernet0/0
ip address 10.52.218.91 255.255.255.0
h323-gateway voip interface
h323-gateway voip id video-98 ipaddr 10.52.218.98 1719
h323-gateway voip h323-id ios-91-to-98
h323-gateway voip tech-prefix 00
h323-gateway voip bind srcaddr 10.52.218.91
!
gateway
!

Next we can proceed with the H.320 video GW configuration.

1. Specify the card type you will have:

card type e1 1 1

2. As video calls are actually the DATA calls by the nature of video content, we need to ensure the clocking is configured corectcly:

network-clock-participate slot 1
network-clock-participate wic 1
!
! Choose the one which required by your hardware setup.
!
network-clock-select 1 E1 1/0

3. You will need to specify the ISDN switch type before you can proceed with PRI group config on the controller:

isdn switch-type primary-net5

4. The controller config is the same as for any PRI connection:

controller E1 1/0
pri-group timeslots 1-31
description >>>>> Test of NEW BT PRI ports - out 338898 *** <<<<<
!

5. Now we need to configure D-channel to accept / send Data calls:

!
interface Serial1/0:15
description >>>>> Test of NEW BT PRI ports - out 338898 *** <<<<<
no ip address
encapsulation hdlc
isdn switch-type primary-net5
isdn map address .* plan unknown type unknown
isdn negotiate-bchan resend-setup
isdn bchan-number-order ascending
isdn sending-complete
isdn integrate calltype all
no cdp enable
!

6. Now we can proceed with the preparation for the dial-peer config, first let define the codecs we will use on IP side.
Please keep in mind that GW will actually do the filtering of the codes it will announce to the endpoints on both sides.

!
voice class codec 1000
codec preference 1 g711ulaw
codec preference 2 g711alaw
codec preference 3 g728
codec preference 4 g722-64
codec preference 5 g722-56
codec preference 6 g722-48
video codec h261
video codec h263
video codec h263+
video codec h264
!

7. This part is required to accept the incoming video calls, we need to have to provide the secondary numbers to the calling party, so they can call us on that numbers to add more bandwidth to the video call, that numbers will be sent out during ISO 13871 bonding stage.

!
voice class called number pool 3151
index 1 315140 - 315149

8. Now we need to apply that pool to the voice port to activate it:

!
voice-port 1/0:15
voice-class called-number-pool 3151
!

9. Now we are ready to proceed with the dial-peer configuration we need 4 of them, two incoming and two outgoing.
It is possible to use one POTS dial-peer as incoming and outgoing at the same time, but we will provide config for two of them for the sake of clarity:

!
dial-peer voice 99 pots
description default incoming video dial-peer
information-type video
incoming called-number 313300
bandwidth maximum 384
direct-inward-dial
!

!
dial-peer voice 9001 pots
description default outgoing video dial-peer
destination-pattern 00
information-type video
bandwidth maximum 384
port 1/0:15
forward-digits all
!

10. here is the example of the VOIP dial-peer, now we configured it as both - incoming and outgoing:

!
dial-peer voice 770 voip
description default incoming/outgoing voip dial-peer for all calls from GK w
destination-pattern 701...
voice-class codec 1000
session target ras
incoming called-number 00.
dtmf-relay h245-alphanumeric
!

==Related show Commands==
This section provides information you can use to confirm your configuration is working properly.

Certain show commands are supported by the [https://www.cisco.com/cgi-bin/Support/OutputInterpreter/home.pl Output Interpreter Tool (registered customers only)], which allows you to view an analysis of show command output.

show network-clocks
show isdn status
show dial-peer voice summary
show voice call status
show voice dsp

There also some useful commands to add and they can be used on All routers in production as well:

service nagle
service tcp-keepalives-in
service tcp-keepalives-out
service timestamps debug datetime msec
service timestamps log datetime msec

!
logging message-counter syslog
logging queue-limit 100000
logging buffered 5000000
logging rate-limit 10000
no logging console

And some very useful aliases :)

!
alias exec c conf t
alias exec r sh run
alias exec i sh ip ro
alias exec ib sh ip int brie
alias exec gs show run | s gatekeeper
alias exec ge sho gatekeeper end
alias exec sg sho gatekeeper
alias exec rs sh run | s
alias exec ri sh run | i
alias exec rb sh run | b
alias exec dp sh run | be dial-p
!

Enjoy :)

==Show running-config==

<pre>Add show running config of your device</pre>

==Related Information==
[http://www.cisco.com/web/psa/products/index.html Technical Support & Documentation - Cisco Systems]





[[Category:example]]
[[Category:video]]
[[Category:ISR]]
[[Category:2800]]
[[Category:gatekeeper]]
[[Category:config]]
[[Category:VoIP Configuration Examples]]
[[Category:Configuration Examples]]

Video on ISR 2800 3800 H.320 GW with ISO 13871 bonding Configuration Example

2010-06-05T16:43:04Z

Msamarts:

==Introduction==

This is the basic config for any ISR router 2800 / 3800 series with PRI connection to PSTN / PBX and H.323 protocol on IP side.

==Design==

The example toplogy:

Tandberg VT - E1 PRI - PSTN - E1 PRI - ISR router - H.323 GK - Tandberg VT

==Configuration==

1. First we need to register GW and the video endpoint to the GK.
The most simple setup will be if we register endpoing with full E164 number and GW with the tech prefix, chousen in a way it will allow dialing to PSTN without any number transformation.
Assume PSTN will requre 00 for international call, in this case we can use the following config on GK:

!
gatekeeper
zone local video-98 mappets.com 10.52.218.98
no use-proxy video-98 default inbound-to terminal
no use-proxy video-98 default outbound-from terminal
no shutdown
!

There is no need to configure zone prefixes as GW will register with the tech prefix.
And VT will register with the full E164 number, so GK will always be able to resolve the them to IP.
For VT we need to allow direct calls to / from H.323 GW, so we disabling proxy requirement.

The matching GW config will be:

!
interface FastEthernet0/0
ip address 10.52.218.91 255.255.255.0
h323-gateway voip interface
h323-gateway voip id video-98 ipaddr 10.52.218.98 1719
h323-gateway voip h323-id ios-91-to-98
h323-gateway voip tech-prefix 00
h323-gateway voip bind srcaddr 10.52.218.91
!
gateway
!

Next we can proceed with the H.320 video GW configuration.

1. Specify the card type you will have:

card type e1 1 1

2. As video calls are actually the DATA calls by the nature of video content, we need to ensure the clocking is configured corectcly:

network-clock-participate slot 1
network-clock-participate wic 1
! Choose the one which required by your hardware setup.
!
network-clock-select 1 E1 1/0

3. You will need to specify the ISDN switch type before you can proceed with PRI group config on the controller:

isdn switch-type primary-net5

4. The controller config is the same as for any PRI connection:

controller E1 1/0
pri-group timeslots 1-31
description >>>>> Test of NEW BT PRI ports - out 338898 *** <<<<<
!

5. Now we need to configure D-channel to accept / send Data calls:

!
interface Serial1/0:15
description >>>>> Test of NEW BT PRI ports - out 338898 *** <<<<<
no ip address
encapsulation hdlc
isdn switch-type primary-net5
isdn map address .* plan unknown type unknown
isdn negotiate-bchan resend-setup
isdn bchan-number-order ascending
isdn sending-complete
isdn integrate calltype all
no cdp enable
!

6. Now we can proceed with the preparation for the dial-peer config, first let define the codecs we will use on IP side.
Please keep in mind that GW will actually do the filtering of the codes it will announce to the endpoints on both sides.

!
voice class codec 1000
codec preference 1 g711ulaw
codec preference 2 g711alaw
codec preference 3 g728
codec preference 4 g722-64
codec preference 5 g722-56
codec preference 6 g722-48
video codec h261
video codec h263
video codec h263+
video codec h264
!

7. This part is required to accept the incoming video calls, we need to have to provide the secondary numbers to the calling party, so they can call us on that numbers to add more bandwidth to the video call, that numbers will be sent out during ISO 13871 bonding stage.

!
voice class called number pool 3151
index 1 315140 - 315149

8. Now we need to apply that pool to the voice port to activate it:

!
voice-port 1/0:15
voice-class called-number-pool 3151
!

9. Now we are ready to proceed with the dial-peer configuration we need 4 of them, two incoming and two outgoing.
It is possible to use one POTS dial-peer as incoming and outgoing at the same time, but we will provide config for two of them for the sake of clarity:

!
dial-peer voice 99 pots
description default incoming video dial-peer
information-type video
incoming called-number 313300
bandwidth maximum 384
direct-inward-dial
!

!
dial-peer voice 9001 pots
description default outgoing video dial-peer
destination-pattern 00
information-type video
bandwidth maximum 384
port 1/0:15
forward-digits all
!

10. here is the example of the VOIP dial-peer, now we configured it as both - incoming and outgoing:

!
dial-peer voice 770 voip
description default incoming/outgoing voip dial-peer for all calls from GK w
destination-pattern 701...
voice-class codec 1000
session target ras
incoming called-number 00.
dtmf-relay h245-alphanumeric
!

==Related show Commands==
This section provides information you can use to confirm your configuration is working properly.

Certain show commands are supported by the [https://www.cisco.com/cgi-bin/Support/OutputInterpreter/home.pl Output Interpreter Tool (registered customers only)], which allows you to view an analysis of show command output.

show network-clocks
show isdn status
show dial-peer voice summary
show voice call status
show voice dsp

There also some useful commands to add and they can be used on All routers in production as well:

service nagle
service tcp-keepalives-in
service tcp-keepalives-out
service timestamps debug datetime msec
service timestamps log datetime msec

!
logging message-counter syslog
logging queue-limit 100000
logging buffered 5000000
logging rate-limit 10000
no logging console

And some very useful aliases :)

!
alias exec c conf t
alias exec r sh run
alias exec i sh ip ro
alias exec ib sh ip int brie
alias exec gs show run | s gatekeeper
alias exec ge sho gatekeeper end
alias exec sg sho gatekeeper
alias exec rs sh run | s
alias exec ri sh run | i
alias exec rb sh run | b
alias exec dp sh run | be dial-p
!

Enjoy :)

==Show running-config==

<pre>Add show running config of your device</pre>

==Related Information==
[http://www.cisco.com/web/psa/products/index.html Technical Support & Documentation - Cisco Systems]





[[Category:example]]
[[Category:video]]
[[Category:ISR]]
[[Category:2800]]
[[Category:gatekeeper]]
[[Category:config]]
[[Category:VoIP Configuration Examples]]
[[Category:Configuration Examples]]

Video on ISR 2800 3800 H.320 GW with ISO 13871 bonding Configuration Example

2010-06-05T16:37:23Z

Msamarts:

==Introduction==

This is the basic config for any ISR router 2800 / 3800 series with PRI connection to PSTN / PBX and H.323 protocol on IP side.

==Design==

The example toplogy:

Tandberg VT - E1 PRI - PSTN - E1 PRI - ISR router - H.323 GK - Tandberg VT

==Configuration==

1. First we need to register GW and the video endpoint to the GK.
The most simple setup will be if we register endpoing with full E164 number and GW with the tech prefix, chousen in a way it will allow dialing to PSTN without any number transformation.
Assume PSTN will requre 00 for international call, in this case we can use the following config on GK:

!
gatekeeper
zone local video-98 mappets.com 10.52.218.98
no use-proxy video-98 default inbound-to terminal
no use-proxy video-98 default outbound-from terminal
no shutdown
!

There is no need to configure zone prefixes as GW will register with the tech prefix.
And VT will register with the full E164 number, so GK will always be able to resolve the them to IP.
For VT we need to allow direct calls to / from H.323 GW, so we disabling proxy requirement.

The matching GW config will be:

!
interface FastEthernet0/0
ip address 10.52.218.91 255.255.255.0
h323-gateway voip interface
h323-gateway voip id video-98 ipaddr 10.52.218.98 1719
h323-gateway voip h323-id ios-91-to-98
h323-gateway voip tech-prefix 00
h323-gateway voip bind srcaddr 10.52.218.91
!
gateway
!

Next we can proceed with the H.320 video GW configuration.

1. Specify the card type you will have:

card type e1 1 1

2. As video calls are actually the DATA calls by the nature of video content, we need to ensure the clocking is configured corectcly:

network-clock-participate slot 1
network-clock-participate wic 1
! Choose the one which required by your hardware setup.
!
network-clock-select 1 E1 1/0

3. You will need to specify the ISDN switch type before you can proceed with PRI group config on the controller:

isdn switch-type primary-net5

4. The controller config is the same as for any PRI connection:

controller E1 1/0
pri-group timeslots 1-31
description >>>>> Test of NEW BT PRI ports - out 338898 *** <<<<<
!

5. Now we need to configure D-channel to accept / send Data calls:

!
interface Serial1/0:15
description >>>>> Test of NEW BT PRI ports - out 338898 *** <<<<<
no ip address
encapsulation hdlc
isdn switch-type primary-net5
isdn map address .* plan unknown type unknown
isdn negotiate-bchan resend-setup
isdn bchan-number-order ascending
isdn sending-complete
isdn integrate calltype all
no cdp enable
!

6. Now we can proceed with the preparation for the dial-peer config, first let define the codecs we will use on IP side.
Please keep in mind that GW will actually do the filtering of the codes it will announce to the endpoints on both sides.

!
voice class codec 1000
codec preference 1 g711ulaw
codec preference 2 g711alaw
codec preference 3 g728
codec preference 4 g722-64
codec preference 5 g722-56
codec preference 6 g722-48
video codec h261
video codec h263
video codec h263+
video codec h264
!

7. This part is required to accept the incoming video calls, we need to have to provide the secondary numbers to the calling party, so they can call us on that numbers to add more bandwidth to the video call, that numbers will be sent out during ISO 13871 bonding stage.

!
voice class called number pool 3151
index 1 315140 - 315149

8. Now we need to apply that pool to the voice port to activate it:

!
voice-port 1/0:15
voice-class called-number-pool 3151
!

9. Now we are ready to proceed with the dial-peer configuration we need 4 of them, two incoming and two outgoing.
It is possible to use one POTS dial-peer as incoming and outgoing at the same time, but we will provide config for two of them for the sake of clarity:

!
dial-peer voice 99 pots
description default incoming video dial-peer
information-type video
incoming called-number 313300
bandwidth maximum 384
direct-inward-dial
!

!
dial-peer voice 9001 pots
description default outgoing video dial-peer
destination-pattern 00
information-type video
bandwidth maximum 384
port 1/0:15
forward-digits all
!

10. here is the example of the VOIP dial-peer, now we configured it as both - incoming and outgoing:

!
dial-peer voice 770 voip
description default incoming/outgoing voip dial-peer for all calls from GK w
destination-pattern 701...
voice-class codec 1000
session target ras
incoming called-number 00.
dtmf-relay h245-alphanumeric
!

==Related show Commands==
This section provides information you can use to confirm your configuration is working properly.

Certain show commands are supported by the [https://www.cisco.com/cgi-bin/Support/OutputInterpreter/home.pl Output Interpreter Tool (registered customers only)], which allows you to view an analysis of show command output.

show network-clocks
show isdn status
show dial-peer voice summary
show voice call status
show voice dsp

There also some useful commands to add and they can be used on All routers in production as well:

service nagle
service tcp-keepalives-in
service tcp-keepalives-out
service timestamps debug datetime msec
service timestamps log datetime msec

!
logging message-counter syslog
logging queue-limit 100000
logging buffered 5000000
logging rate-limit 10000
no logging console

And some very useful aliases :)

!
alias exec c conf t
alias exec r sh run
alias exec i sh ip ro
alias exec ib sh ip int brie
alias exec gs show run | s gatekeeper
alias exec ge sho gatekeeper end
alias exec sg sho gatekeeper
alias exec rs sh run | s
alias exec ri sh run | i
alias exec rb sh run | b
alias exec dp sh run | be dial-p
!

Enjoy :)

==Show running-config==

<pre>Add show running config of your device</pre>

==Related Information==
[http://www.cisco.com/web/psa/products/index.html Technical Support & Documentation - Cisco Systems]





[[Category:example]]
[[Category:video]]
[[Category:ISR]]
[[Category:2800]]
[[Category:gatekeeper]]
[[Category:config]]
[[Category:VoIP Configuration Examples]]

Video on ISR 2800 3800 H.320 GW with ISO 13871 bonding Configuration Example

2010-06-05T16:33:07Z

Msamarts: Cisco ISR H.320 Video with ISO 13871 bonding Configuration Example

==Introduction==

This is the basic config for any ISR router 2800 / 3800 series with PRI connection to PSTN / PBX and H.323 protocol on IP side.

==Design==

The example toplogy:

Tandberg VT - E1 PRI - PSTN - E1 PRI - ISR router - H.323 GK - Tandberg VT

==Configuration==

1. First we need to register GW and the video endpoint to the GK.
The most simple setup will be if we register endpoing with full E164 number and GW with the tech prefix, chousen in a way it will allow dialing to PSTN without any number transformation.
Assume PSTN will requre 00 for international call, in this case we can use the following config on GK:

!
gatekeeper
zone local video-98 mappets.com 10.52.218.98
no use-proxy video-98 default inbound-to terminal
no use-proxy video-98 default outbound-from terminal
no shutdown
!

There is no need to configure zone prefixes as GW will register with the tech prefix.
And VT will register with the full E164 number, so GK will always be able to resolve the them to IP.
For VT we need to allow direct calls to / from H.323 GW, so we disabling proxy requirement.

The matching GW config will be:

!
interface FastEthernet0/0
ip address 10.52.218.91 255.255.255.0
h323-gateway voip interface
h323-gateway voip id video-98 ipaddr 10.52.218.98 1719
h323-gateway voip h323-id ios-91-to-98
h323-gateway voip tech-prefix 00
h323-gateway voip bind srcaddr 10.52.218.91
!
gateway
!

Next we can proceed with the H.320 video GW configuration.

1. Specify the card type you will have:

card type e1 1 1

2. As video calls are actually the DATA calls by the nature of video content, we need to ensure the clocking is configured corectcly:

network-clock-participate slot 1
network-clock-participate wic 1
! Choose the one which required by your hardware setup.
!
network-clock-select 1 E1 1/0

3. You will need to specify the ISDN switch type before you can proceed with PRI group config on the controller:

isdn switch-type primary-net5

4. The controller config is the same as for any PRI connection:

controller E1 1/0
pri-group timeslots 1-31
description >>>>> Test of NEW BT PRI ports - out 338898 *** <<<<<
!

5. Now we need to configure D-channel to accept / send Data calls:

!
interface Serial1/0:15
description >>>>> Test of NEW BT PRI ports - out 338898 *** <<<<<
no ip address
encapsulation hdlc
isdn switch-type primary-net5
isdn map address .* plan unknown type unknown
isdn negotiate-bchan resend-setup
isdn bchan-number-order ascending
isdn sending-complete
isdn integrate calltype all
no cdp enable
!

6. Now we can proceed with the preparation for the dial-peer config, first let define the codecs we will use on IP side.
Please keep in mind that GW will actually do the filtering of the codes it will announce to the endpoints on both sides.

!
voice class codec 1000
codec preference 1 g711ulaw
codec preference 2 g711alaw
codec preference 3 g728
codec preference 4 g722-64
codec preference 5 g722-56
codec preference 6 g722-48
video codec h261
video codec h263
video codec h263+
video codec h264
!

7. This part is required to accept the incoming video calls, we need to have to provide the secondary numbers to the calling party, so they can call us on that numbers to add more bandwidth to the video call, that numbers will be sent out during ISO 13871 bonding stage.

!
voice class called number pool 3151
index 1 315140 - 315149

8. Now we need to apply that pool to the voice port to activate it:

!
voice-port 1/0:15
voice-class called-number-pool 3151
!

9. Now we are ready to proceed with the dial-peer configuration we need 4 of them, two incoming and two outgoing.
It is possible to use one POTS dial-peer as incoming and outgoing at the same time, but we will provide config for two of them for the sake of clarity:

!
dial-peer voice 99 pots
description default incoming video dial-peer
information-type video
incoming called-number 313300
bandwidth maximum 384
direct-inward-dial
!

!
dial-peer voice 9001 pots
description default outgoing video dial-peer
destination-pattern 00
information-type video
bandwidth maximum 384
port 1/0:15
forward-digits all
!

10. here is the example of the VOIP dial-peer, now we configured it as both - incoming and outgoing:

!
dial-peer voice 770 voip
description default incoming/outgoing voip dial-peer for all calls from GK w
destination-pattern 701...
voice-class codec 1000
session target ras
incoming called-number 00.
dtmf-relay h245-alphanumeric
!

==Related show Commands==
This section provides information you can use to confirm your configuration is working properly.

Certain show commands are supported by the [https://www.cisco.com/cgi-bin/Support/OutputInterpreter/home.pl Output Interpreter Tool (registered customers only)], which allows you to view an analysis of show command output.

show network-clocks
show isdn status
show dial-peer voice summary
show voice call status
show voice dsp

There also some useful commands to add and they can be used on All routers in production as well:

service nagle
service tcp-keepalives-in
service tcp-keepalives-out
service timestamps debug datetime msec
service timestamps log datetime msec

!
logging message-counter syslog
logging queue-limit 100000
logging buffered 5000000
logging rate-limit 10000
no logging console

And some very useful aliases :)

!
alias exec c conf t
alias exec r sh run
alias exec i sh ip ro
alias exec ib sh ip int brie
alias exec gs show run | s gatekeeper
alias exec ge sho gatekeeper end
alias exec sg sho gatekeeper
alias exec rs sh run | s
alias exec ri sh run | i
alias exec rb sh run | b
alias exec dp sh run | be dial-p
!

Enjoy :)

==Show running-config==

<pre>Add show running config of your device</pre>

==Related Information==
[http://www.cisco.com/web/psa/products/index.html Technical Support & Documentation - Cisco Systems]





[[Category:example]]
[[Category:video]]
[[Category:ISR]]
[[Category:2800]]
[[Category:gatekeeper]]
[[Category:config]]

Category:Configuration Examples

2010-06-05T12:28:37Z

Msamarts:

[[image:Gears.gif|40px|left]] Please feel free to contribute to the Configuration Example collection. You must log into DocWiki using your Cisco.com credentials before you can add content. Type the name of your Configuration Example into the box below using the following syntax:

'''<product name> <feature/description> Configuration Example'''

For example, "Unity Express Networking with Direct IP Addressing Configuration Example"
<inputbox>
type=create
preload=Template:Configuration Example/Preload
</inputbox>

{{note|If you enter the name of an article that already exists, the existing article will appear in the edit window.}}
{{note|This template contains details that might not be applicable to your example. Please edit at your discretion.}}

For help, see [[Help:Creating Configuration Examples]].

The Configuration Examples category contains configuration examples listed by product, technology, or system.

Category:Configuration Examples

2010-06-05T11:40:28Z

Msamarts: Cisco ISR H.320 Video with ISO 13871 bonding Config Example

'''Cisco ISR H.320 Video with ISO 13871 bonding Config Example'''

<inputbox>
type=create
preload=Template:Configuration Example/Preload
</inputbox>

Cisco ISR H.320 Video with ISO 13871 bonding Config Example

This is the basic config for any ISR router 2800 / 3800 series with PRI connection to PSTN / PBX and H.323 protocol on IP side.

The example toplogy:

Tandberg VT - E1 PRI - PSTN - E1 PRI - ISR router - H.323 GK - Tandberg VT

1. First we need to register GW and the video endpoint to the GK.
The most simple setup will be if we register endpoing with full E164 number and GW with the tech prefix, chousen in a way it will allow dialing to PSTN without any number transformation.
Assume PSTN will requre 00 for international call, in this case we can use the following config on GK:

!
gatekeeper
zone local video-98 mappets.com 10.52.218.98
no use-proxy video-98 default inbound-to terminal
no use-proxy video-98 default outbound-from terminal
no shutdown
!

There is no need to configure zone prefixes as GW will register with the tech prefix.
And VT will register with the full E164 number, so GK will always be able to resolve the them to IP.
For VT we need to allow direct calls to / from H.323 GW, so we disabling proxy requirement.

The matching GW config will be:

!
interface FastEthernet0/0
ip address 10.52.218.91 255.255.255.0
h323-gateway voip interface
h323-gateway voip id video-98 ipaddr 10.52.218.98 1719
h323-gateway voip h323-id ios-91-to-98
h323-gateway voip tech-prefix 00
h323-gateway voip bind srcaddr 10.52.218.91
!
gateway
!

Next we can proceed with the H.320 video GW configuration.

1. Specify the card type you will have:

card type e1 1 1

2. As video calls are actually the DATA calls by the nature of video content, we need to ensure the clocking is configured corectcly:

network-clock-participate slot 1
network-clock-participate wic 1
! Choose the one which required by your hardware setup.
!
network-clock-select 1 E1 1/0

3. You will need to specify the ISDN switch type before you can proceed with PRI group config on the controller:

isdn switch-type primary-net5

4. The controller config is the same as for any PRI connection:

controller E1 1/0
pri-group timeslots 1-31
description >>>>> Test of NEW BT PRI ports - out 338898 *** <<<<<
!

5. Now we need to configure D-channel to accept / send Data calls:

!
interface Serial1/0:15
description >>>>> Test of NEW BT PRI ports - out 338898 *** <<<<<
no ip address
encapsulation hdlc
isdn switch-type primary-net5
isdn map address .* plan unknown type unknown
isdn negotiate-bchan resend-setup
isdn bchan-number-order ascending
isdn sending-complete
isdn integrate calltype all
no cdp enable
!

6. Now we can proceed with the preparation for the dial-peer config, first let define the codecs we will use on IP side.
Please keep in mind that GW will actually do the filtering of the codes it will announce to the endpoints on both sides.

!
voice class codec 1000
codec preference 1 g711ulaw
codec preference 2 g711alaw
codec preference 3 g728
codec preference 4 g722-64
codec preference 5 g722-56
codec preference 6 g722-48
video codec h261
video codec h263
video codec h263+
video codec h264
!

7. This part is required to accept the incoming video calls, we need to have to provide the secondary numbers to the calling party, so they can call us on that numbers to add more bandwidth to the video call, that numbers will be sent out during ISO 13871 bonding stage.

!
voice class called number pool 3151
index 1 315140 - 315149

8. Now we need to apply that pool to the voice port to activate it:

!
voice-port 1/0:15
voice-class called-number-pool 3151
!

9. Now we are ready to proceed with the dial-peer configuration we need 4 of them, two incoming and two outgoing.
It is possible to use one POTS dial-peer as incoming and outgoing at the same time, but we will provide config for two of them for the sake of clarity:

!
dial-peer voice 99 pots
description default incoming video dial-peer
information-type video
incoming called-number 313300
bandwidth maximum 384
direct-inward-dial
!

!
dial-peer voice 9001 pots
description default outgoing video dial-peer
destination-pattern 00
information-type video
bandwidth maximum 384
port 1/0:15
forward-digits all
!

10. here is the example of the VOIP dial-peer, now we configured it as both - incoming and outgoing:

!
dial-peer voice 770 voip
description default incoming/outgoing voip dial-peer for all calls from GK w
destination-pattern 701...
voice-class codec 1000
session target ras
incoming called-number 00.
dtmf-relay h245-alphanumeric
!

There also some useful commands to add and they can be used on All routers in production as well:

service nagle
service tcp-keepalives-in
service tcp-keepalives-out
service timestamps debug datetime msec
service timestamps log datetime msec

!
logging message-counter syslog
logging queue-limit 100000
logging buffered 5000000
logging rate-limit 10000
no logging console

And some very useful aliases :)

!
alias exec c conf t
alias exec r sh run
alias exec i sh ip ro
alias exec ib sh ip int brie
alias exec gs show run | s gatekeeper
alias exec ge sho gatekeeper end
alias exec sg sho gatekeeper
alias exec rs sh run | s
alias exec ri sh run | i
alias exec rb sh run | b
alias exec dp sh run | be dial-p
!

Enjoy :)