Re: [Opalvoip-devel] H.323/Gatekeeper: wrong destCallSignalAddress in Setup PDU after receiving Facility message

[Robert J. <ro...@vo...>]

Patch applied.


Thank you very much, once again!

Robert Jongbloed
*OPAL/OpenH323/PTLib Architect and Co-founder*.

On 30 January 2015 at 01:39, Harald Karner <har...@gm...> wrote:

> Same test scenario, another issue found...
>
> On 28.01.2015 14:31, Harald Karner wrote:
>
>> I've been conducting some tests using a gatekeeper and stumbled upon the
>> following issue:
>>
>> My setup:
>> - System A: OPAL, not registered with gatekeeper
>> - System B, Cisco, registered with gatekeeper
>> - Gatekeeper
>>
>> When I make a call from System A to System B directly, B will respond to
>> the Setup message with a Facility message containing
>> reason=routeCallToGatekeeper and the gatekeepers address. So far, so good.
>> System A will then send a releaseComplete to System B and a new Setup
>> message to the gatekeeper.
>>
>
> The Problem: The second Setup message has the Q.931/Bearer
> capability/Information transfer capability set to "Speech" instead of
> "Digital".
> The problem arises in OpalCall::GetMediaFormats() where the media format
> list of the local connection is intersected with the (empty) format list of
> the old h323 connection thus returning an empty list.
>
> The attached patch fixes this issue.
>
> Regards,
> Harald
>
>
> ------------------------------------------------------------------------------
> Dive into the World of Parallel Programming. The Go Parallel Website,
> sponsored by Intel and developed in partnership with Slashdot Media, is
> your
> hub for all things parallel software development, from weekly thought
> leadership blogs to news, videos, case studies, tutorials and more. Take a
> look and join the conversation now. http://goparallel.sourceforge.net/
> _______________________________________________
> Opalvoip-devel mailing list
> Opa...@li...
> https://lists.sourceforge.net/lists/listinfo/opalvoip-devel
>
>