[OSL | CCIE_Voice] Gatekeeper configuration

2011-10-04 Thread darshan
 

Dear All;

 

I have 2 requirements and I don't know which one is the correct
configuration..

 

1.  For SIte C CME gateway

 

Configure SIteC Router as H323 gateway.

Make sure that all inbound  outbound H323 traffic is
sourced from the local interface

144.102.66.254/24

 

2.In Gatekeeper another Question is there

 

SIte C should use its Loopback address for all
communication with the gatekeeper.

 

 

My configuration is

 

Sc#interface loopback 0

desc SC Loopback

h323-gateway voip interface

ip address 144.1.66.254 255.255.255.0

h323-gateway voip interface

h323-gateway voip id GK ipaddr 144.1.64.254 1719

h323-gateway voip bind srcaddr 144.1.66.254

 

OR

 

Sc#interface vlan502

desc SC Voice

h323-voip interface

ip address 144.102.66.254 255.255.255.0

h323-gateway voip interface

h323-gateway voip id GK ipaddr 144.1.64.254 1719

h323-gateway voip bind srcaddr 144.102.66.254

 

 

144.1.66.254--- is the SIte C Loopback address

144.102.66.254-- is the Site C Voice Vlan 502

 

 

Appreciate to help me in this regard..

 

reagrds

Tashu

 

___
For more information regarding industry leading CCIE Lab training, please visit 
www.ipexpert.com

Are you a CCNP or CCIE and looking for a job? Check out 
www.PlatinumPlacement.com

Re: [OSL | CCIE_Voice] Gatekeeper configuration

2011-10-04 Thread Mohd Baqari
In h323 only one interface can be used as source IP for all h323 messages. You 
cant have two h323 sources in same router. Maybe typo error

Regards,
Mohammed Al Baqari

Sent from my iPhone

On Oct 4, 2011, at 12:12 PM, darshan ccievoice0...@hotmail.com wrote:

  
 
 Dear All;
 
  
 
 I have 2 requirements and I don’t know which one is the correct 
 configuration..
 
  
 
 1.  For SIte C CME gateway
 
  
 
 Configure SIteC Router as H323 gateway.
 
 Make sure that all inbound  outbound H323 traffic is 
 sourced from the local interface
 
 144.102.66.254/24
 
  
 
 2.In Gatekeeper another Question is there
 
  
 
 SIte C should use its Loopback address for all communication 
 with the gatekeeper.
 
  
 
  
 
 My configuration is
 
  
 
 Sc#interface loopback 0
 
 desc SC Loopback
 
 h323-gateway voip interface
 
 ip address 144.1.66.254 255.255.255.0
 
 h323-gateway voip interface
 
 h323-gateway voip id GK ipaddr 144.1.64.254 1719
 
 h323-gateway voip bind srcaddr 144.1.66.254
 
  
 
 OR
 
  
 
 Sc#interface vlan502
 
 desc SC Voice   
 
 h323-voip interface
 
 ip address 144.102.66.254 255.255.255.0
 
 h323-gateway voip interface
 
 h323-gateway voip id GK ipaddr 144.1.64.254 1719
 
 h323-gateway voip bind srcaddr 144.102.66.254
 
  
 
  
 
 144.1.66.254--- is the SIte C Loopback address
 
 144.102.66.254-- is the Site C Voice Vlan 502
 
  
 
  
 
 Appreciate to help me in this regard..
 
  
 
 reagrds
 
 Tashu
 
  
 
 ___
 For more information regarding industry leading CCIE Lab training, please 
 visit www.ipexpert.com
 
 Are you a CCNP or CCIE and looking for a job? Check out 
 www.PlatinumPlacement.com
___
For more information regarding industry leading CCIE Lab training, please visit 
www.ipexpert.com

Are you a CCNP or CCIE and looking for a job? Check out 
www.PlatinumPlacement.com

Re: [OSL | CCIE_Voice] Gatekeeper configuration

2011-10-04 Thread darshan
Yes Mohd this is right..but In SiteC CME gateway it asks for Vlan 502 IP and 
gatekeeper to use local loopback..so I am really confused.

 

Regards

Darsh

 

From: Mohd Baqari [mailto:baqari.voic...@gmail.com] 
Sent: Tuesday, October 04, 2011 4:37 PM
To: darshan
Cc: ccie_voice@onlinestudylist.com
Subject: Re: [OSL | CCIE_Voice] Gatekeeper configuration

 

In h323 only one interface can be used as source IP for all h323 messages. You 
cant have two h323 sources in same router. Maybe typo error

Regards,

Mohammed Al Baqari

 

Sent from my iPhone


On Oct 4, 2011, at 12:12 PM, darshan ccievoice0...@hotmail.com wrote:

 

Dear All;

 

I have 2 requirements and I don’t know which one is the correct configuration..

 

1.  For SIte C CME gateway

 

Configure SIteC Router as H323 gateway.

Make sure that all inbound  outbound H323 traffic is sourced 
from the local interface

144.102.66.254/24

 

2.In Gatekeeper another Question is there

 

SIte C should use its Loopback address for all communication 
with the gatekeeper.

 

 

My configuration is

 

Sc#interface loopback 0

desc SC Loopback

h323-gateway voip interface

ip address 144.1.66.254 255.255.255.0

h323-gateway voip interface

h323-gateway voip id GK ipaddr 144.1.64.254 1719

h323-gateway voip bind srcaddr 144.1.66.254

 

OR

 

Sc#interface vlan502

desc SC Voice

h323-voip interface

ip address 144.102.66.254 255.255.255.0

h323-gateway voip interface

h323-gateway voip id GK ipaddr 144.1.64.254 1719

h323-gateway voip bind srcaddr 144.102.66.254

 

 

144.1.66.254--- is the SIte C Loopback address

144.102.66.254-- is the Site C Voice Vlan 502

 

 

Appreciate to help me in this regard..

 

reagrds

Tashu

 

___
For more information regarding industry leading CCIE Lab training, please visit 
www.ipexpert.com

Are you a CCNP or CCIE and looking for a job? Check out 
www.PlatinumPlacement.com

___
For more information regarding industry leading CCIE Lab training, please visit 
www.ipexpert.com

Are you a CCNP or CCIE and looking for a job? Check out 
www.PlatinumPlacement.com

Re: [OSL | CCIE_Voice] Gatekeeper configuration

2011-10-04 Thread Rrcrumm
Did you do a gateway in config mode on the branch rtr? Is it registered?

Randall

Sent from my iPhone

On Oct 4, 2011, at 1:12 AM, darshan ccievoice0...@hotmail.com wrote:

  
 
 Dear All;
 
  
 
 I have 2 requirements and I don’t know which one is the correct 
 configuration..
 
  
 
 1.  For SIte C CME gateway
 
  
 
 Configure SIteC Router as H323 gateway.
 
 Make sure that all inbound  outbound H323 traffic is 
 sourced from the local interface
 
 144.102.66.254/24
 
  
 
 2.In Gatekeeper another Question is there
 
  
 
 SIte C should use its Loopback address for all communication 
 with the gatekeeper.
 
  
 
  
 
 My configuration is
 
  
 
 Sc#interface loopback 0
 
 desc SC Loopback
 
 h323-gateway voip interface
 
 ip address 144.1.66.254 255.255.255.0
 
 h323-gateway voip interface
 
 h323-gateway voip id GK ipaddr 144.1.64.254 1719
 
 h323-gateway voip bind srcaddr 144.1.66.254
 
  
 
 OR
 
  
 
 Sc#interface vlan502
 
 desc SC Voice   
 
 h323-voip interface
 
 ip address 144.102.66.254 255.255.255.0
 
 h323-gateway voip interface
 
 h323-gateway voip id GK ipaddr 144.1.64.254 1719
 
 h323-gateway voip bind srcaddr 144.102.66.254
 
  
 
  
 
 144.1.66.254--- is the SIte C Loopback address
 
 144.102.66.254-- is the Site C Voice Vlan 502
 
  
 
  
 
 Appreciate to help me in this regard..
 
  
 
 reagrds
 
 Tashu
 
  
 
 ___
 For more information regarding industry leading CCIE Lab training, please 
 visit www.ipexpert.com
 
 Are you a CCNP or CCIE and looking for a job? Check out 
 www.PlatinumPlacement.com
___
For more information regarding industry leading CCIE Lab training, please visit 
www.ipexpert.com

Are you a CCNP or CCIE and looking for a job? Check out 
www.PlatinumPlacement.com

Re: [OSL | CCIE_Voice] Gatekeeper configuration

2011-10-04 Thread Ashraf Ayyash
Guys ,

the h323 bind command is not a GK command , its for the H323 GW so you
can have GK on interface and have the normal config of the GK
and the H323 bind under the interface which will work as H323 GW with the ccm

H323 bind can be usefull if you have Q said bind all media and
signalling to specific interface IP , h323 bind in this case will do
RTP binding for you ,

i hope this is clear

Ash

On Tue, Oct 4, 2011 at 8:45 AM, Rrcrumm rrcr...@yahoo.com wrote:
 Did you do a gateway in config mode on the branch rtr? Is it registered?
 Randall

 Sent from my iPhone
 On Oct 4, 2011, at 1:12 AM, darshan ccievoice0...@hotmail.com wrote:



 Dear All;



 I have 2 requirements and I don’t know which one is the correct
 configuration..



 1.  For SIte C     CME gateway



     Configure SIteC Router as H323 gateway.

     Make sure that all inbound  outbound H323 traffic is
 sourced from the local interface

     144.102.66.254/24



 2.In Gatekeeper another Question is there



     SIte C should use its Loopback address for all
 communication with the gatekeeper.





 My configuration is



 Sc#interface loopback 0

     desc SC Loopback

     h323-gateway voip interface

     ip address 144.1.66.254 255.255.255.0

     h323-gateway voip interface

     h323-gateway voip id GK ipaddr 144.1.64.254 1719

     h323-gateway voip bind srcaddr 144.1.66.254



 OR



 Sc#interface vlan502

     desc SC Voice

     h323-voip interface

     ip address 144.102.66.254 255.255.255.0

     h323-gateway voip interface

     h323-gateway voip id GK ipaddr 144.1.64.254 1719

     h323-gateway voip bind srcaddr 144.102.66.254





 144.1.66.254--- is the SIte C Loopback address

 144.102.66.254-- is the Site C Voice Vlan 502





 Appreciate to help me in this regard..



 reagrds

 Tashu



 ___
 For more information regarding industry leading CCIE Lab training, please
 visit www.ipexpert.com

 Are you a CCNP or CCIE and looking for a job? Check out
 www.PlatinumPlacement.com

 ___
 For more information regarding industry leading CCIE Lab training, please
 visit www.ipexpert.com

 Are you a CCNP or CCIE and looking for a job? Check out
 www.PlatinumPlacement.com

___
For more information regarding industry leading CCIE Lab training, please visit 
www.ipexpert.com

Are you a CCNP or CCIE and looking for a job? Check out 
www.PlatinumPlacement.com


[OSL | CCIE_Voice] Gatekeeper configuration question- Proctor lab guide

2008-04-04 Thread Vik Ahuja
Members,
  Question 19 from lab 1 for proctor lab guide given at that bootcamp relates 
to configuring gatekeeper, it states to configure both zones as local for CCM 
and BR2. Why are both of these considering local?, I would think the BR2 site 
would considered a remote site. If someone could please elaborate on this that 
would be helpful.
   
  Thanks!. 


Sincerely, 
Vik Ahuja 
VATech IT consulting services 
  CCIE # 11958 (Security, RS) CISSP, CCNP 
Cell : 510-304-9423 
Email: [EMAIL PROTECTED]


Re: [OSL | CCIE_Voice] Gatekeeper configuration question- Proctor lab guide

2008-04-04 Thread Jonathan Charles
Because they are both controlled by THIS gatekeeper.

A remote zone is a zone controlled by a different Gatekeeper.


Jonathan

On Fri, Apr 4, 2008 at 11:57 AM, Vik Ahuja [EMAIL PROTECTED] wrote:
 Members,
 Question 19 from lab 1 for proctor lab guide given at that bootcamp relates
 to configuring gatekeeper, it states to configure both zones as local for
 CCM and BR2. Why are both of these considering local?, I would think the BR2
 site would considered a remote site. If someone could please elaborate on
 this that would be helpful.

 Thanks!.

 Sincerely,
 Vik Ahuja
 VATech IT consulting services
 CCIE # 11958 (Security, RS) CISSP, CCNP
 Cell : 510-304-9423
 Email: [EMAIL PROTECTED]


Re: [OSL | CCIE_Voice] Gatekeeper Configuration and MTP

2007-12-13 Thread Mark Snow
If the call comes in G711 - and forwards properly to CUE and the ONLY  
thing that is changing for it not to work is that you change the  
incoming DP to G729 - then the problem must be with the transcoders  
not invoking properly.


What debugs have you run to try to troubleshoot this problem?

Mark Snow
CCIE #14073 (Voice, Security)
CCSI #31583
Senior Technical Instructor - IPexpert, Inc.
A Cisco Learning Partner - We Accept Learning Credits!
Telephone: +1.810.326.1444
Fax: +1.309.413.4097
Mailto: [EMAIL PROTECTED]

IPexpert - The Global Leader in Self-Study, Classroom-Based, Video On  
Demand and Audio Certification Training Tools for the Cisco CCIE RS  
Lab, CCIE Security Lab, CCIE Service Provider Lab , CCIE Voice Lab and  
CCIE Storage Lab Certifications.



On Dec 13, 2007, at 12:44 AM, Balamurugan Singaram wrote:


Hi,

Thanks Mark.

When I have try voice class codec command, in CME side call-forward  
busy is not working when the class comes as g729  [call is not  
hitting the CUE] even when the transcoder is up on CME.


When I remove the voice class codec the call is hitting the CUE.

Could you please suggest me a good solution for codec match and call  
forward busy to work in CME side.


Thanks,
Bala.

Mark Snow [EMAIL PROTECTED] wrote:
When trying to control BW and using a H323 GK - doing the CAC on the  
GK and NOT on the CCM side with Locations is recommended.

Both will work - it is just less to troubleshoot.

As far as having codec selection on a DP - create a voice class  
codec globally, define your codecs with their preference, and then  
call that voice class codec from your DP.


HTH,

Mark Snow
CCIE #14073 (Voice, Security)
CCSI #31583
Senior Technical Instructor - IPexpert, Inc.
A Cisco Learning Partner - We Accept Learning Credits!
Telephone: +1.810.326.1444
Fax: +1.309.413.4097
Mailto: [EMAIL PROTECTED]

IPexpert - The Global Leader in Self-Study, Classroom-Based, Video  
On Demand and Audio Certification Training Tools for the Cisco CCIE  
RS Lab, CCIE Security Lab, CCIE Service Provider Lab , CCIE Voice  
Lab and CCIE Storage Lab Certifications.



On Dec 12, 2007, at 1:07 AM, Balamurugan Singaram wrote:


Hi,

For Gatekeeper CAC, update the region as g711 and for Gatekeeper  
device pool update the region [g711] and left none for location.


Gatekeeper bandwidth is controlled  via bandwidth command
as zone bw ipexpert 144 this example could support up to one G. 
711 and one g.729 calls.



when I try calling CME form CCM or vice versa, it hit the CME or  
ccm as g.729 call only.


In CME when the incoming called-number . with codec g711ulaw
all call are coming as g711 call only. The incoming dial peer is  
not receiving both g.729 and g.711.



Could please some one explain how to control codec selection  
between CCM - GK - CME [h.323 gateway].


Note - To control Bandwidth via gatekeeper, zone Bw is good idea  
[IOS gatekeeper command] or using location in gatekeeper device  
pool is better option?



Thanks,
Bala.

Mark Snow [EMAIL PROTECTED] wrote:
If you were to call from CCM over to CME and didn't have the MTP
checked - then transferred the call or various other things known as
'supplementary services' - they would most probably fail.

The 'enable outbound faststart' is due to the fact that the IPIPGW in
IOS 12.4 mainline only supports:
- H323 FastStart -- SIP Early Media
- H323 SlowStart -- SIP Delayed Media
but NOT
- H323 FastStart -- SIP Delayed Media
- H323 SlowStart -- SIP Early Media

And the IOS Router running CME defaults to SIP Early Media.

Another valid option to this would be to leave the CCM GK Controlled
Trunk with 'enable outbound faststart' unchecked and instead to  
change

the IOS CME Router to:
!
sip-ua
disable-early-media 180
!


HTH,

Mark Snow
CCIE #14073 (Voice, Security)
CCSI #31583
Senior Technical Instructor - IPexpert, Inc.
A Cisco Learning Partner - We Accept Learning Credits!
Telephone: +1.810.326.1444
Fax: +1.309.413.4097
Mailto: [EMAIL PROTECTED]

IPexpert - The Global Leader in Self-Study, Classroom-Based, Video On
Demand and Audio Certification Training Tools for the Cisco CCIE RS
Lab, CCIE Security Lab, CCIE Service Provider Lab , CCIE Voice Lab  
and

CCIE Storage Lab Certifications.


On Dec 9, 2007, at 2:38 AM, Balamurugan Singaram wrote:

 Hi,

 In CCM Gatekeeper trunk configuration, if Media termination point
 required is enable or disable I am able to hit CUE voice mail, In
 CME Transcoder is configured and SCCP is up.

 So if Transcoder is enabled in CME, Media termination point
 required is not required to enable on Gatekeeper configuration  
page.


 Could you please correct me if I am wrong or let me know the
 explanation of Media termination point required and “enable
 outbound faststart” in Gatekeeper configuration page.

 Thanks,
 Bala.
 Send instant messages to your online friends http://uk.messenger.yahoo.com



Send instant messages to your online friends http://uk.messenger.yahoo.com



Send instant messages to your