- Joined
- Feb 8, 2019
- Messages
- 124
- Reaction score
- 18
site-1 (hyper-v linux VM) and site-2 (computer running linux ISO) 3CX v16.0.0.1581 connected via VPN.
site-1 has a GXW410x at it's location. GXW has two accounts setup. Account-1 setup to register on site-1, but will not register. Account-2 setup to register on site-2 (remote through the VPN) does register. The gxw has a IP address local to site-1.
Packet capture (3cx event log page) at site-2 shows (successful registration)
gxw sends a REGISTER request to mi-3cx
3cx replies with 407 – proxy authentication required
gxw responds with a REGISTER request which includes user-id and password???
3cx replies 200 OK
Packet capture (3cx event log page) at site-1 shows
gxw sends a REGISTER request to mi-3cx
3cx replies with 407 – proxy authentication required
gxw does not respond to the proxy authentication request from 3cx
Approx one minute later the gxw tries to register again. (a retry setting inside gxw is set to 1 minute)
All the while gxw to site-2 is solid green.
Occasionally gxw to site-1 will register, but something goes wrong quickly and 3cx shows registration is dropped.
I have bridge setup between site-1 and site-2 that remain registered. Traffic between the sites is not the problem. Traffic between the site-1 3cx and gxw is the problem. gxw does not have packet capture capability.
Also the inbound voice on PSTN calls thru the gxw is very choppy. The outside caller can hear the inside extension, but the extension has hard time hearing the outside caller. I think this is related to traffic problem. The GXW is known good as it was working without problem until site-1 was upgraded from v15.5 to v16 and moved from windows VM to hyper-v VM. Both sites where upgraded to v16 at same time. Inbound voice was OK until upgrade.
How can I check if or why gxw did not see 407 request?
Any other suggestion would be appreciated.
Thank you,
site-1 has a GXW410x at it's location. GXW has two accounts setup. Account-1 setup to register on site-1, but will not register. Account-2 setup to register on site-2 (remote through the VPN) does register. The gxw has a IP address local to site-1.
Packet capture (3cx event log page) at site-2 shows (successful registration)
gxw sends a REGISTER request to mi-3cx
3cx replies with 407 – proxy authentication required
gxw responds with a REGISTER request which includes user-id and password???
3cx replies 200 OK
Packet capture (3cx event log page) at site-1 shows
gxw sends a REGISTER request to mi-3cx
3cx replies with 407 – proxy authentication required
gxw does not respond to the proxy authentication request from 3cx
Approx one minute later the gxw tries to register again. (a retry setting inside gxw is set to 1 minute)
All the while gxw to site-2 is solid green.
Occasionally gxw to site-1 will register, but something goes wrong quickly and 3cx shows registration is dropped.
I have bridge setup between site-1 and site-2 that remain registered. Traffic between the sites is not the problem. Traffic between the site-1 3cx and gxw is the problem. gxw does not have packet capture capability.
Also the inbound voice on PSTN calls thru the gxw is very choppy. The outside caller can hear the inside extension, but the extension has hard time hearing the outside caller. I think this is related to traffic problem. The GXW is known good as it was working without problem until site-1 was upgraded from v15.5 to v16 and moved from windows VM to hyper-v VM. Both sites where upgraded to v16 at same time. Inbound voice was OK until upgrade.
How can I check if or why gxw did not see 407 request?
Any other suggestion would be appreciated.
Thank you,
