01-22-2004 04:50 AM - edited 03-17-2019 08:09 PM
HI,
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 = 191.103.101.235) when trying to call 11 :
15/01/2004 12:45:18 EndpointIdentifier: '191.103.101.235:1720'
15/01/2004 12:45:18 DestinationInfo count(1) {
15/01/2004 12:45:18 #0 DialedDigits: '11'
15/01/2004 12:45:18 }
15/01/2004 12:45:18 SrcInfo count(2) {
15/01/2004 12:45:18 #0 DialedDigits: '00'
15/01/2004 12:45:18 #1 H323_ID: 'ata00'
15/01/2004 12:45:18 }
15/01/2004 12:45:18 SrcCallSignalAddress IpAddress {
15/01/2004 12:45:18 Ip: 4 octets [C1 64 65 FB] (193.100.101.251)
15/01/2004 12:45:18 Port: 1720 (0x6b8)
15/01/2004 12:45:18 }
15/01/2004 12:45:18 BandWidth: 640 (0x280)
15/01/2004 12:45:18 CallReferenceValue: 10732 (0x29ec)
15/01/2004 12:45:18 NonStandardData {
15/01/2004 12:45:18 NonStandardIdentifier H221NonStandard {
15/01/2004 12:45:18 T35CountryCode: 181 (0xb5)
15/01/2004 12:45:18 T35Extension: 0 (0x0)
15/01/2004 12:45:18 ManufacturerCode: 18 (0x12)
15/01/2004 12:45:18 }
15/01/2004 12:45:18 Data: 7 octets [80 00 00 02 80 01 80]
15/01/2004 12:45:18 }
15/01/2004 12:45:18 ConferenceID: 16 octets [00 00 00 00 DC 74 44 14 19 00 00 08 A3 96 45 5D]
15/01/2004 12:45:18 ActiveMC: false
15/01/2004 12:45:18 AnswerCall: false
15/01/2004 12:45:18 CanMapAlias: true
15/01/2004 12:45:18 CallIdentifier {
15/01/2004 12:45:18 Guid: 16 octets [00 00 00 00 8C 81 AA 17 18 1D 00 08 A3 96 45 5D]
15/01/2004 12:45:18 }
15/01/2004 12:45:18 WillSupplyUUIEs: false
15/01/2004 12:45:18 }
Cisco 1751V (IP = 192.168.1.254) when trying to call 11 :
16/01/2004 09:37:04 RAS, got message from 192.168.1.254:54569
16/01/2004 09:37:04 Message AdmissionRequest {
16/01/2004 09:37:04 RequestSeqNum: 17960 (0x4628)
16/01/2004 09:37:04 CallType PointToPoint
16/01/2004 09:37:04 CallModel Direct
16/01/2004 09:37:04 EndpointIdentifier: '192.168.1.254:1720'
16/01/2004 09:37:04 DestinationInfo count(1) {
16/01/2004 09:37:04 #0 DialedDigits: '11'
16/01/2004 09:37:04 }
16/01/2004 09:37:04 SrcInfo count(1) {
16/01/2004 09:37:04 #0 H323_ID: '932'
16/01/2004 09:37:04 }
16/01/2004 09:37:04 BandWidth: 126 (0x7e)
16/01/2004 09:37:04 CallReferenceValue: 1491 (0x5d3)
16/01/2004 09:37:04 NonStandardData {
16/01/2004 09:37:04 NonStandardIdentifier H221NonStandard {
16/01/2004 09:37:04 T35CountryCode: 181 (0xb5)
16/01/2004 09:37:04 T35Extension: 0 (0x0)
16/01/2004 09:37:04 ManufacturerCode: 18 (0x12)
16/01/2004 09:37:04 }
16/01/2004 09:37:04 Data: 89 octets [80 00 00 0E 38 08 0C 46 58 4F 20 32 2F 31 19 2E 4E 39 35 31 20 74 6F 20 50 61 6E 61 73 6F 6E 69 63 31 32 33 32 44 42 58 30 00 2D 49 41 4D 2C 0D 0A 47 43 49 2C 39 34 64 63 36 36 37 64 34 37 32 64 31 31 64 38 38 34 31 32 61 63 39 63 65 31 66 66 35 37 66 61 0D 0A 0D 0A]
16/01/2004 09:37:04 }
16/01/2004 09:37:04 ConferenceID: 16 octets [94 DC 66 7D 47 2D 11 D8 84 12 AC 9C E1 FF 57 FA]
16/01/2004 09:37:04 ActiveMC: false
16/01/2004 09:37:04 AnswerCall: false
16/01/2004 09:37:04 CanMapAlias: true
16/01/2004 09:37:04 CallIdentifier {
16/01/2004 09:37:04 Guid: 16 octets [94 DD 02 A5 47 2D 11 D8 84 14 AC 9C E1 FF 57 FA]
16/01/2004 09:37:04 }
16/01/2004 09:37:04 WillSupplyUUIEs: false
16/01/2004 09:37:04 }
16/01/2004 09:37:04 Bandwidth occupied: 126*10^2 bits with 1 zone(s) involved.
16/01/2004 09:37:04 in replace of: 0*10^2 bits with 0 zone(s) involved.
Any ideas why?
thanks in advance for help.
01-28-2004 01:37 PM
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)
http://www.cisco.com/en/US/tech/tk652/tk701/technologies_white_paper09186a00800c5f67.shtml
02-05-2004 01:40 PM
But if this is the situation (ATA is sending unidirectional BW of 640) then whatever GK i'll use it will assume that a call originating from an ATA consumes the full 64k.
thus not allowing any other call over a 64K channel.
Is it TRUE?!
i mean does anyone have an VoIP environment with ATAs in? Can you tell me how is it working?
do i need to have a Nx64K channel for N-calls?
thanks in advance,
Marcel
Discover and save your favorite ideas. Come back to expert answers, step-by-step guides, recent topics, and more.
New here? Get started with these tips. How to use Community New member guide