SIP peer lagged and then unreachable intermittently

General Help
1

I have a Sangoma Vega50 FXO gateway that is trunked into a current version freepbx VM running on a windows 2016 hyper-v. This VM is a restore of a freepbx physical server that i was using. The physical server had no problems communicating with the Vega. The VM on the other hand gets intermittently disconnected from the gateway. Asterisk CLI shows the following>>

[2017-04-02 18:16:06] NOTICE[1913]: chan_sip.c:24457 handle_response_peerpoke: Peer ‘vega-in’ is now Lagged. (2004ms / 2000ms)
[2017-04-02 18:16:16] NOTICE[1913]: chan_sip.c:24457 handle_response_peerpoke: Peer ‘vega-in’ is now Reachable. (5ms / 2000ms)
[2017-04-02 18:19:18] NOTICE[1913]: chan_sip.c:29976 sip_poke_noanswer: Peer ‘vega-out’ is now UNREACHABLE! Last qualify: 4
[2017-04-02 18:19:19] NOTICE[1913]: chan_sip.c:24457 handle_response_peerpoke: Peer ‘vega-in’ is now Lagged. (3005ms / 2000ms)
[2017-04-02 18:19:28] NOTICE[1913]: chan_sip.c:24457 handle_response_peerpoke: Peer ‘vega-out’ is now Reachable. (4ms / 2000ms)
[2017-04-02 18:19:55] NOTICE[1913]: chan_sip.c:24457 handle_response_peerpoke: Peer ‘vega-in’ is now Reachable. (5ms / 2000ms)
[2017-04-02 18:21:32] NOTICE[1913]: chan_sip.c:29976 sip_poke_noanswer: Peer ‘vega-out’ is now UNREACHABLE! Last qualify: 4
[2017-04-02 18:21:42] NOTICE[1913]: chan_sip.c:24457 handle_response_peerpoke: Peer ‘vega-out’ is now Reachable. (6ms / 2000ms)
[2017-04-02 18:22:46] NOTICE[1913]: chan_sip.c:29976 sip_poke_noanswer: Peer ‘vega-out’ is now UNREACHABLE! Last qualify: 6
[2017-04-02 18:22:57] NOTICE[1913]: chan_sip.c:24457 handle_response_peerpoke: Peer ‘vega-out’ is now Reachable. (1006ms / 2000ms)
[2017-04-02 18:23:59] NOTICE[1913]: chan_sip.c:24457 handle_response_peerpoke: Peer ‘vega-in’ is now Lagged. (2004ms / 2000ms)
[2017-04-02 18:24:00] NOTICE[1913]: chan_sip.c:24457 handle_response_peerpoke: Peer ‘vega-out’ is now Lagged. (3004ms / 2000ms)
[2017-04-02 18:24:11] NOTICE[1913]: chan_sip.c:24457 handle_response_peerpoke: Peer ‘vega-out’ is now Reachable. (1005ms / 2000ms)
[2017-04-02 18:24:13] NOTICE[1913]: chan_sip.c:29976 sip_poke_noanswer: Peer ‘vega-in’ is now UNREACHABLE! Last qualify: 2004
[2017-04-02 18:24:23] NOTICE[1913]: chan_sip.c:24457 handle_response_peerpoke: Peer ‘vega-in’ is now Reachable. (4ms / 2000ms)
[2017-04-02 18:28:25] NOTICE[1913]: chan_sip.c:24457 handle_response_peerpoke: Peer ‘vega-in’ is now Lagged. (2005ms / 2000ms)
[2017-04-02 18:28:35] NOTICE[1913]: chan_sip.c:24457 handle_response_peerpoke: Peer ‘vega-in’ is now Reachable. (5ms / 2000ms)
[2017-04-02 18:29:38] NOTICE[1913]: chan_sip.c:24457 handle_response_peerpoke: Peer ‘vega-in’ is now Lagged. (3004ms / 2000ms)
[2017-04-02 18:30:24] NOTICE[1913]: chan_sip.c:24457 handle_response_peerpoke: Peer ‘vega-in’ is now Reachable. (4ms / 2000ms)
[2017-04-02 18:31:14] NOTICE[1913]: chan_sip.c:24457 handle_response_peerpoke: Peer ‘vega-out’ is now Lagged. (2005ms / 2000ms)
[2017-04-02 18:31:24] NOTICE[1913]: chan_sip.c:24457 handle_response_peerpoke: Peer ‘vega-out’ is now Reachable. (4ms / 2000ms)
[2017-04-02 18:32:26] NOTICE[1913]: chan_sip.c:24457 handle_response_peerpoke: Peer ‘vega-in’ is now Lagged. (2006ms / 2000ms)
[2017-04-02 18:32:36] NOTICE[1913]: chan_sip.c:24457 handle_response_peerpoke: Peer ‘vega-in’ is now Reachable. (4ms / 2000ms)
[2017-04-02 18:36:40] NOTICE[1913]: chan_sip.c:29976 sip_poke_noanswer: Peer ‘vega-in’ is now UNREACHABLE! Last qualify: 5
[2017-04-02 18:37:06] NOTICE[1913]: chan_sip.c:29976 sip_poke_noanswer: Peer ‘vega-in’ is now UNREACHABLE! Last qualify: 2004
[2017-04-02 18:37:16] NOTICE[1913]: chan_sip.c:24457 handle_response_peerpoke: Peer ‘vega-in’ is now Reachable. (4ms / 2000ms)
[2017-04-02 18:43:22] NOTICE[1913]: chan_sip.c:29976 sip_poke_noanswer: Peer ‘vega-in’ is now UNREACHABLE! Last qualify: 1004
[2017-04-02 18:43:32] NOTICE[1913]: chan_sip.c:24457 handle_response_peerpoke: Peer ‘vega-in’ is now Reachable. (4ms / 2000ms)

i can run an uninterrupted and rather stable ping to both machines from a third witness. I found posts regarding similar problems but none seemed to apply to my setup.

Any ideas?

2

I had similar problems with a Hyper-V Server 2012R2 instance. I never did make it work. I moved the VM to a Hyper-V Server 2012 instance and the problems went away.

I never tried adding Microsofts updated VM drivers, instead of the default repo VM drivers.

3

It had crossed my mind that there is a VM driver incompatibility but the ping test got me skeptical of this theory. I migrated the VM to a 2008R2 hyper-v and it all worked like a charm.
Thank you!