[ previous ] [ next ] [ threads ]
 To :  Marian Podgoreanu <marian@v...>
 From :  Bohdan Shubenok <confucij@g...>
 Subject :  Re: [yate] IAX2 issue with repeated remoteCallNo
 Date :  Wed, 31 May 2017 16:40:42 +0300
Hi,

You may have a look on this commit
https://gitlab.com/flamesgroup/yate/commit/635c64ae5fec4bd92cdb5b182e1bc77899a745e1
We already trying to fix this.

2017-05-31 15:08 GMT+03:00 Marian Podgoreanu :

> Hi,
>
> This will be fixed as soon as possible.
>
> You may try, if allowed by your setup, to configure multiple iax listeners
> and use them for different remote IPs you are using.
> See http://docs.yate.ro/wiki/IAX
>
> Marian
>
>
> On 05/30/2017 04:08 PM, Bohdan Shubenok wrote:
>
>> Hi, all!
>>
>> I suddenly came across on a thing that I can consider a bug.  I have
>> YATE configured as softswitch sending calls between two independent
>> IAX2 peers and sometimes it happens that both clients return the same
>> remoteCallNomber which drives YATE crazy. In attached log file you can
>> find two calls with local:remote 20461:5565 and 20486:5565. And the
>> problem is on a NEW for second call 20486:5565 YATE sends ACK to first
>> call 20461:5565. Peer then resends ACCEPT and YATE again sends ACK to
>> the wrong peer.
>> Is it a bug and if yes how can I avoid it?
>>
>>  Thank in advance!
>>
>



We already trying to fix this.

2017-05-31 15:08 GMT+03:00 Marian Podgoreanu <marian@v...>:
Hi,

This will be fixed as soon as possible.

You may try, if allowed by your setup, to configure multiple iax listeners and use them for different remote IPs you are using.
See http://docs.yate.ro/wiki/IAX

Marian


On 05/30/2017 04:08 PM, Bohdan Shubenok wrote:
Hi, all!

I suddenly came across on a thing that I can consider a bug.  I have
YATE configured as softswitch sending calls between two independent
IAX2 peers and sometimes it happens that both clients return the same
remoteCallNomber which drives YATE crazy. In attached log file you can
find two calls with local:remote 20461:5565 and 20486:5565. And the
problem is on a NEW for second call 20486:5565 YATE sends ACK to first
call 20461:5565. Peer then resends ACCEPT and YATE again sends ACK to
the wrong peer.
Is it a bug and if yes how can I avoid it?

 Thank in advance!