cancel
Showing results for 
Search instead for 
Did you mean: 
cancel
Announcements
281
Views
0
Helpful
1
Replies
Highlighted

issues with gatekeepers

                   Hello guys I am wondering if someone have faced this situation.

I have 2 central gatekeepers wich controls the customer dial-plan. To this gatekeeper are registered all the equipments that creates the telephony network.

I have two gateways that are working as cme this two gateways were registered correctly to both gatekeepers and working. The issue is that randomly these gateways loose the registration to both gatekeepers and logically to all the telephony network. In order to register the gateways again we just reset the connection trough the cli with no gateway and gateway again until them lost the registration again.

We have tested the conectivity to the gatekeepers and in does not seems to be an issue.

Any ideas.

Regards

1 ACCEPTED SOLUTION

Accepted Solutions
Highlighted
Rising star

You can debug your registration issue using "debug h225 asn1".

Here you can find more info:

http://www.cisco.com/en/US/tech/tk1077/technologies_tech_note09186a008011221e.shtml

You can also try to set a RAS timeout to get a more frequent registration, e.g. every minute:

The ras timeout command configures the number of seconds for the gateway to wait before resending a RAS message to a gatekeeper. The ras retry command configures the number of times to resend the RAS message after  the timeout period expires. The default values for timeouts and retries  are acceptable in most networks. You can use these commands if you are  experiencing problems in RAS message transmission between gateways and  gatekeepers. For example, if you have gatekeepers that are slow to  respond to a type of RAS request, increasing the timeout value and the  number of retries increases the call success rate, preventing lost  billing information and unnecessary switchover to an alternate  gatekeeper.

The ras rrq ttl command configures the number  of seconds that the gateway should be considered active by the  gatekeeper. The gateway transmits this value in the RRQ message to the  gatekeeper. The margin time keyword and argument allow the gateway to transmit an early RRQ to the  gatekeeper before the time-to-live value advertised to the gatekeeper.

SUMMARY STEPS

1. voice service voip

2. h323

3. ras timeout {all | arq | brq | drq | grq | rai | rrq} value

4. ras retry {all | arq | brq | drq | grq | rai | rrq} value

5. exit

More info at this link:

http://www.cisco.com/en/US/docs/ios/12_3/vvf_c/cisco_ios_h323_configuration_guide/old_archives_h323/4gwconf.html

Regards.

View solution in original post

1 REPLY 1
Highlighted
Rising star

You can debug your registration issue using "debug h225 asn1".

Here you can find more info:

http://www.cisco.com/en/US/tech/tk1077/technologies_tech_note09186a008011221e.shtml

You can also try to set a RAS timeout to get a more frequent registration, e.g. every minute:

The ras timeout command configures the number of seconds for the gateway to wait before resending a RAS message to a gatekeeper. The ras retry command configures the number of times to resend the RAS message after  the timeout period expires. The default values for timeouts and retries  are acceptable in most networks. You can use these commands if you are  experiencing problems in RAS message transmission between gateways and  gatekeepers. For example, if you have gatekeepers that are slow to  respond to a type of RAS request, increasing the timeout value and the  number of retries increases the call success rate, preventing lost  billing information and unnecessary switchover to an alternate  gatekeeper.

The ras rrq ttl command configures the number  of seconds that the gateway should be considered active by the  gatekeeper. The gateway transmits this value in the RRQ message to the  gatekeeper. The margin time keyword and argument allow the gateway to transmit an early RRQ to the  gatekeeper before the time-to-live value advertised to the gatekeeper.

SUMMARY STEPS

1. voice service voip

2. h323

3. ras timeout {all | arq | brq | drq | grq | rai | rrq} value

4. ras retry {all | arq | brq | drq | grq | rai | rrq} value

5. exit

More info at this link:

http://www.cisco.com/en/US/docs/ios/12_3/vvf_c/cisco_ios_h323_configuration_guide/old_archives_h323/4gwconf.html

Regards.

View solution in original post