A have a VoIP environment kind of: ATA-186 <---> 1751V <--64K--> 1751V<---> Software Gatekeeper H.323 fully compliant.
All devices are configured to use G.723 codec.
The problem is: when a call is placed from the phone connected to ATA-186, it sends bandwidth parameter 640(0x280) what equals to 64K. causing GK to assume that no other call can be admitted. While 1751V sends the correct bandwidth parameter 126(0x7e).
Thus I can not place one more call because the GK thinks that the whole bandwidth is consumed by the previous call.
This is the debug from GK
Cisco ATA-186I1 (IP = 126.96.36.199) when trying to call 11 :
I think ATA is reporting unidirectional BW of 640 ( 64 Kps) to GK while initiating the call. At that the time of ARQ , ATA may not know the actual codec , BW that will be used for the call as they might be negotiated dynamically during the call. If the ATA supports BRQ, it can be used to report to the GK the call BW used by the call after the negotiation is over.
I am not sure why 1751 sends 126 as the BW in ARQ. ( for g.723)
Are you getting this error “Installer User Interface Mode Not Supported. The installer cannot run in this UI mode. To specify the interface mode, use the -i command-line option, followed by the UI mode identifier. The value UI mode identifiers...
The below trick might come handy when you have to add a new node to a cluster but you don't have or is unsure of the security password for the publisher. This procedure has been around for ages.
1) Login into the CLI of the Publisher.