Dial-up over Windows 10 to the Avaya 1

[Mike94]

Hello All,

I am facing an issue on Windows 10 when I’m trying to Dial-Up to the remote Avaya site. It’s look like they are two part of this problem.

1. I’m connecting to the PC in my office via Team Viewer and then from this PC I’m using the Dial-up to remotely access the Avaya IP Office at my customer site.

As soon as I establish the Dial-Up connection this PC is loosing access to the Internet and obviously disconnects me from the Team Viewer session. After this the PC still has access to the LAN, but not to the Internet. I would like to add, that previously on the Windows 7, this problem didn’t exist.

2. When I’m physically in the office without using the Team Viewer, once I am connected to the site via Dial-Up, I can’t see the Avaya IP office on the IP Office Manager.

I am using the AVM Fritz! Card USB v2.1 to establish my Dial-Up connection.

Looking forward for any ideas,

Thanks,

Mike

 

[derfloh]

For problem 1 disable "create default route" ( or similar) within the IP settings of the dialin connection.

Dir problem 2... Not sure tbh. Perhaps try to connect to the IP of the other LAN interface of IPO.

IP Office remote service

https://www.fwilke.com/home

Fixed price SIP trunk configuration:

https://www.fwilke.com/en/ip-office-sip-trunk-en/

CLI based cale blocking:

https://blog.fwilke.com/ip-office-block-calls-from-specific-cli/

SCN fallback over PSTN:

https://blog.fwilke.com/ip-office-scn-fallback/

 

[Mike94]

If I disable option Use the Default Gateway on the Dial-Up connection setup I am not losing the Internet connection during the session, but I still can’t see the IP Office.

 

[TomMills]

Do you have an IP Office in your office? Use that to create the connection rather than the modem.

APSS/ACIS/ACSS-SME
not arrogant, just succinct.

 

[ogTOKYO]

you're connection is defaulting to the current uplink, it's an IP route issue, not an Avaya issue. You might encounter the similar problem connecting your phone to a dial-in VPN, then you realize your DNS and public access to the net is down.

______________________
|........................................|
|.....i.eat.bunny.children......|
|______________________|
(\__/) ||
(•Y•). ||
/ < )<||

 

[Mike94]

you're connection is defaulting to the current uplink, it's an IP route issue, not an Avaya issue. You might encounter the similar problem connecting your phone to a dial-in VPN, then you realize your DNS and public access to the net is down.

I was wondering if this was not related to the routing table issue. Could you give me any idea how I should configure my routing table ? I would like to add, that on the Windows 7 I am still kicking off from my office Internet, but I can successfully send the Broadcast message and find the Avaya - without any additional configuration, which doesn't work like this on Windows 10.

 

[budbyrd]

We used dial-up for a very short time with a few of our customers that didn't have voicemail servers. We stopped using it after having the connection drop during a config upload that crashed the system. Forcing us to send a tech on site that we couldn't bill. Since that time we have been using low cost mini PCs for remote access. Much better solution in the long run.

Dermis and feline can be divorced by manifold methods.*
*(Disclaimer for all advise given)--'Version Dependent'