Thanks Pavek,
It was a codec mismatch which has been sorted out now. Two other issues I
have found are that when initiating the call from Asterisk (ooh323 being the
endpoint), ooh323 won't negotiate the framesPerPkt down, chan_ooh323 offers
4, however the ATA wants 3. Examination of the ooh323 stack source reveals
an empty stub to reduce the endpoint transmission framesPerPkt rate
(ooCapability.c, line 974 of 0.8.2). This was worked around by changing the
default framesPerPkt from 4 to 3 in the g723.1 capabilities function of
ooh323cDriver.c. There is no problem when the call originates from the ATA
as ooh323 will happily match the reduced framesPerPkt in this instance.
One final issue, a different ATA model from Hughes will only support G729AB,
which ooh323 interprets as G729B. Searching around a bit on google shows
that G729AB seems to be different to G729B and there are suggestions that
G729AB may be compatible with G729A. Is this true?, if so then I could
possibly get a successful connection by modifying the codec compare code in
ooh323 (ooCapability.c) to match G729B to G729A and ensuring that VAD is
disabled on the ata.
The reason I am stuck with the particular ata's is because I am trying to
have asterisk work across a satellite link provided by Hughes Satellite
Broadband ( www.hns.com ), and the ata is provided by Hughes. Other ata's
have been tried, however the Hughes one has some proprietary way of
requesting and receiving traffic priority across the satellite. Normal
ata's are subject to massive jitter.
Craig
----- Original Message -----
From: "Pavel Jezek" <[EMAIL PROTECTED]>
To: "Craig Guy" <[EMAIL PROTECTED]>
Sent: Thursday, February 01, 2007 5:50 PM
Subject: Re: [ooh323c-devel] ooh323c stack calling ATA problem
>I think, g711 is mandatory codecs, what all devices must supoort,
> I have no other idea abot thos issue,
> I'm using asterisk 1.4 branch with original chan_h323 included in tree
> (channels/h323), it working fine for me.
> PJ
>
>
> Craig Guy wrote:
>> Hi Pavel,
>>
>> I've been told this ata only supports g723.1, the ata is able to call a
>> test extension on asterisk that plays back a gsm file. The asterisk
>> server has g723.1 and g729 codecs installed, and the ooh323 channel
>> driver explicitly states that those codecs are supported. Do you think
>> the important part of the log is in these lines:
>>
>> 16:28:04:040 Comparing channel with codec type: 9
>> 16:28:04:040 Comparing codecs: channel's=12, requested=9
>>
>> Is there a a table listing the codec types and numbers?
>>
>> Thankyou for your reply
>>
>> Craig
>>
>> ----- Original Message ----- From: "Pavel Jezek" <[EMAIL PROTECTED]>
>> To: "Craig Guy" <[EMAIL PROTECTED]>
>> Sent: Thursday, February 01, 2007 8:11 AM
>> Subject: Re: [ooh323c-devel] ooh323c stack calling ATA problem
>>
>>
>>> maybe codecs mismatch? try to use g711 (on ooh323 side), instead of
>>> g723...
>>> PJ
>>>
>>>
>>> Craig Guy wrote:
>>>> Hi list, second attempt to post so please forgive me if it appears
>>>> twice.
>>>>
>>>> I'm trying to get asterisk and ooh323 working with a Hughes Electronics
>>>> 6040
>>>> series ata. Calls from the ATA to asterisk are ok, however calls
>>>> originating from ooh323 are failing just after chan_ooh323 receives the
>>>> connect message from the ATA.
>>>>
>>>> I have updated chan_ooh323 to use ooh323 0.8.3 and the error persists.
>>>> I
>>>> don't know enough about H.323 to determine why the call is failing. I
>>>> am
>>>> able to test and provide any output required, including tcpdumps to
>>>> determine the nature of the problm. Debug was enabled on ooh323 with a
>>>> call
>>>> being placed from the ATA to asterisk where asterisk then dialled a
>>>> different port on the ATA. The first handset received a ringing tone
>>>> and
>>>> the second handset started to ring. After answering the second handset
>>>> the
>>>> error message appeared and the ringing tone continued in the dialling
>>>> handset. The following is the output surrounding the error message (at
>>>> 16:28:04:040): (full log available if required)
>>>>
>>>> 16:28:04:024 H.225 Connect message received (outgoing, ooh323c_o_1)
>>>> 16:28:04:024 Deleted CallESTB timer. (outgoing, ooh323c_o_1)
>>>> 16:28:04:024 FastStart Elements = {
>>>> 16:28:04:024 forwardLogicalChannelNumber = {
>>>> 16:28:04:024 1006
>>>> 16:28:04:024 }
>>>> 16:28:04:024 forwardLogicalChannelParameters = {
>>>> 16:28:04:024 dataType = {
>>>> 16:28:04:024 audioData = {
>>>> 16:28:04:025 g7231 = {
>>>> 16:28:04:025 maxAl_sduAudioFrames = {
>>>> 16:28:04:025 3
>>>> 16:28:04:025 }
>>>> 16:28:04:026 silenceSuppression = {
>>>> 16:28:04:026 TRUE
>>>> 16:28:04:026 }
>>>> 16:28:04:027 }
>>>> 16:28:04:027 }
>>>> 16:28:04:027 }
>>>> 16:28:04:027 multiplexParameters = {
>>>> 16:28:04:027 h2250LogicalChannelParameters = {
>>>> 16:28:04:028 sessionID = {
>>>> 16:28:04:028 1
>>>> 16:28:04:028 }
>>>> 16:28:04:028 mediaChannel = {
>>>> 16:28:04:029 unicastAddress = {
>>>> 16:28:04:029 iPAddress = {
>>>> 16:28:04:029 network = {
>>>> 16:28:04:030 'ac129a02'H
>>>> 16:28:04:030 }
>>>> 16:28:04:031 tsapIdentifier = {
>>>> 16:28:04:031 6010
>>>> 16:28:04:032 }
>>>> 16:28:04:032 }
>>>> 16:28:04:032 }
>>>> 16:28:04:033 }
>>>> 16:28:04:033 mediaGuaranteedDelivery = {
>>>> 16:28:04:033 FALSE
>>>> 16:28:04:033 }
>>>> 16:28:04:034 mediaControlChannel = {
>>>> 16:28:04:034 unicastAddress = {
>>>> 16:28:04:034 iPAddress = {
>>>> 16:28:04:035 network = {
>>>> 16:28:04:035 'ac129a02'H
>>>> 16:28:04:035 }
>>>> 16:28:04:036 tsapIdentifier = {
>>>> 16:28:04:036 6011
>>>> 16:28:04:037 }
>>>> 16:28:04:037 }
>>>> 16:28:04:037 }
>>>> 16:28:04:038 }
>>>> 16:28:04:038 mediaControlGuaranteedDelivery = {
>>>> 16:28:04:038 FALSE
>>>> 16:28:04:039 }
>>>> 16:28:04:039 silenceSuppression = {
>>>> 16:28:04:039 FALSE
>>>> 16:28:04:039 }
>>>> 16:28:04:040 }
>>>> 16:28:04:040 }
>>>> 16:28:04:040 }
>>>> 16:28:04:040 ooFindLogicalChannel by olc 1006 (outgoing, ooh323c_o_1)
>>>> 16:28:04:040 Finding transmit channel (outgoing, ooh323c_o_1)
>>>> 16:28:04:040 ooFindLogicalChannel, checking channel: 1:receive
>>>> 16:28:04:040 ooFindLogicalChannel, checking channel: 1:transmit
>>>> 16:28:04:040 ooFindLogicalChannel, comparing channel: 1:transmit
>>>> 16:28:04:040 Comparing channel with codec type: 9
>>>> 16:28:04:040 Comparing codecs: channel's=12, requested=9
>>>> 16:28:04:040 ooFindLogicalChannel, checking channel: 0:receive
>>>> 16:28:04:040 ooFindLogicalChannel, checking channel: 0:transmit
>>>> 16:28:04:040 ooFindLogicalChannel, checking channel: 0:receive
>>>> 16:28:04:040 ooFindLogicalChannel, checking channel: 0:transmit
>>>> 16:28:04:040 ERROR: Logical Channel 1006 not found, fasts start
>>>> answered.
>>>> (outgoing, ooh323c_o_1)
>>>> 16:28:04:040 }
>>>> 16:28:04:040 Error:Invalid Connect message received. (outgoing,
>>>> ooh323c_o_1)
>>>>
>>>>
>>>> -------------------------------------------------------------------------
>>>>
>>>> Using Tomcat but need to do more? Need to support web services,
>>>> security?
>>>> Get stuff done quickly with pre-integrated technology to make your job
>>>> easier.
>>>> Download IBM WebSphere Application Server v.1.0.1 based on Apache
>>>> Geronimo
>>>> http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642
>>>> _______________________________________________
>>>> ooh323c-devel mailing list
>>>> [email protected]
>>>> https://lists.sourceforge.net/lists/listinfo/ooh323c-devel
>>>>
>>>>
>>
>
-------------------------------------------------------------------------
Using Tomcat but need to do more? Need to support web services, security?
Get stuff done quickly with pre-integrated technology to make your job easier.
Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642
_______________________________________________
ooh323c-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/ooh323c-devel
