[asterisk-dev] poke retries

[Dmitry Andrianov]

Hello.

I'm thinking about modifying chan_iax2.c to allow N (2 or 3) unreplied
pokes before reporting peer as unreachable. Are there any objections
against such an approach?

 

The problem I'm trying to solve if constant flooding of console with
output like:

 

[Oct  3 00:25:57] NOTICE[2659]: chan_iax2.c:8467 __iax2_poke_noanswer:
Peer '1002' is now UNREACHABLE! Time: 62

[Oct  3 00:26:27] NOTICE[2655]: chan_iax2.c:7578 socket_process: Peer
'1002' is now REACHABLE! Time: 52

[Oct  3 00:27:31] NOTICE[2656]: chan_iax2.c:8467 __iax2_poke_noanswer:
Peer '1002' is now UNREACHABLE! Time: 52

[Oct  3 00:28:01] NOTICE[2655]: chan_iax2.c:7578 socket_process: Peer
'1002' is now REACHABLE! Time: 51

[Oct  3 00:29:05] NOTICE[2656]: chan_iax2.c:8467 __iax2_poke_noanswer:
Peer '1002' is now UNREACHABLE! Time: 51

[Oct  3 00:29:35] NOTICE[2658]: chan_iax2.c:7578 socket_process: Peer
'1002' is now REACHABLE! Time: 55

[Oct  3 00:30:39] NOTICE[2653]: chan_iax2.c:8467 __iax2_poke_noanswer:
Peer '1002' is now UNREACHABLE! Time: 55

[Oct  3 00:31:09] NOTICE[2655]: chan_iax2.c:7578 socket_process: Peer
'1002' is now REACHABLE! Time: 58

[Oct  3 00:32:13] NOTICE[2656]: chan_iax2.c:8467 __iax2_poke_noanswer:
Peer '1002' is now UNREACHABLE! Time: 58

[Oct  3 00:32:43] NOTICE[2662]: chan_iax2.c:7578 socket_process: Peer
'1002' is now REACHABLE! Time: 61

[Oct  3 00:33:47] NOTICE[2658]: chan_iax2.c:8467 __iax2_poke_noanswer:
Peer '1002' is now UNREACHABLE! Time: 61

[Oct  3 00:35:37] NOTICE[2660]: chan_iax2.c:7578 socket_process: Peer
'1002' is now REACHABLE! Time: 53

[Oct  3 00:36:41] NOTICE[2659]: chan_iax2.c:8467 __iax2_poke_noanswer:
Peer '1002' is now UNREACHABLE! Time: 53

[Oct  3 00:37:11] NOTICE[2660]: chan_iax2.c:7578 socket_process: Peer
'1002' is now REACHABLE! Time: 52

[Oct  3 00:38:15] NOTICE[2659]: chan_iax2.c:8467 __iax2_poke_noanswer:
Peer '1002' is now UNREACHABLE! Time: 52

[Oct  3 00:38:45] NOTICE[2656]: chan_iax2.c:7578 socket_process: Peer
'1002' is now REACHABLE! Time: 55

[Oct  3 00:39:49] NOTICE[2661]: chan_iax2.c:8467 __iax2_poke_noanswer:
Peer '1002' is now UNREACHABLE! Time: 55

[Oct  3 00:40:19] NOTICE[2655]: chan_iax2.c:7578 socket_process: Peer
'1002' is now REACHABLE! Time: 56

[Oct  3 00:41:23] NOTICE[2655]: chan_iax2.c:8467 __iax2_poke_noanswer:
Peer '1002' is now UNREACHABLE! Time: 56

[Oct  3 00:41:53] NOTICE[2653]: chan_iax2.c:7578 socket_process: Peer
'1002' is now REACHABLE! Time: 56

 

 

I have IAX2 clients connecting over VPN and there is a packet loss about
7% for them so some packets are actually lost. I suppose that as soon as
single poke packet is lost, asterisk reports unreachable peer. Although
just a single additional poke would reveal the fact that peer is alive.

 

Regards,

Dmitry Andrianov

-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.digium.com/pipermail/asterisk-dev/attachments/20071003/6868c202/attachment-0001.htm