Join the best erotica focused adult social network now
Login

Help Needed From Networking Professional!

last reply
12 replies
2.4k views
0 watchers
0 likes
Liz
Scarlet Seductress
Are there any computer networking professionals on Lush?

I have an issue with a Draytek router which I can’t work out.

Just replaced an old, ISP-supplied router with a brand new Draytek Vigor 2865ac. Unfortunately, since replacing it I have been unable to get my SNOM 320 VoIP phone to provision. I use a web VoIP service rather than a local PBX.

It worked absolutely fine on the old router with no config at all (and still does if I swap it back), but not on this new one.

- The phone is set to DHCP and does get assigned an IP by the Draytek when it boots up.

- I can see the phone’s IP in the router’s DHCP and ARP tables.

- For some reason, I am unable to load the phone’s web interface if I browse to its IP address. I also cannot ping the phone’s IP from either my PC on the same network or directly from the router’s web interface.

The fact that the phone is assigned an IP yet cannot be pinged seems like the standout fact. Obviously, there is some sort of configuration issue preventing web traffic to and from the phone.

Other info: I have the Application Layer Gateway (ALG) disabled on the advice of many online VoIP guides, and have set up a rule opening the requisite SIP and RTP ports in the firewall but that hasn’t worked. Both the router and phone are both running the latest firmware versions.

Does anyone have any ideas? I’m fresh out.

Thank you!

Liz
WannabeWordsmith
Writius Eroticus
Weird indeed. You seem to have troubleshot (troubleshooted?) everything I'd have tried.

The only possible reasons I can think of for a network-enabled device on DHCP being inaccessible is because the router is supplying an IP address to either the phone or your PC that are on different subnets/VLANs. Quite why a router would do that out of the box is unclear but maybe it sees the two devices as different classifications and 'conveniently' subnets them for you?

Bottom line as you know: if your VoIP phone and PC are assigned the same subnet it should be pingable and web-accessible on port 80.

Random long shots, none of which I expect to bear fruit:

* Does the phone config software work over port 80 or a custom port? Can the web interface port be changed? I guess if you can't access it, then that's going to be tough!
* Is that port being blocked for whatever reason by your PC's local firewall? (the Windows firewall is a pain in the arse in this regard. Sometimes it even swallows pings for no reason).
* Is the gateway IP on the phone being overridden somehow? Perhaps it's still picking up the old gateway IP from the previous router (or it's been set at some point) and the lease on the new one isn't being released/renewed properly.
* Can you directly connect your PC to the phone in any way using a crossover cable and static IPs? At least that should allow you to get at it. If that works, try using the MAC Binding feature of the router to temporarily deliver the same pair of static IPs to both devices. If it works on static IPs then there's some crazy DHCP issue at play.

I notice that the 'Vac' model of that router has dedicated VoIP functionality so all I can think of is that they're doing some device-level filtering in the 'ac' model to convince you to use their own VoIP provisioning. Sneaky if so.

Please browse my digital bookshelf. In this collection, you can find 116 full stories, 10 micro-stories, and 2 poems with the following features:


* 29 Editor's Picks, 75 Recommended Reads.
* 15 competition podium places, 11 other times in the top ten.
* 21 collaborations.
* A whole heap of often filthy, tense, hot sex.
Jen
Charming as fuck
Just a reminder that English is the accepted standard language on Lush
kistinspencil
Voyeur @ f/64
Quote by Jen
Just a reminder that English is the accepted standard language on Lush


sprite
Her Royal Spriteness
did you try unplugging it and then plugging it back in again after 10 seconds?

You can’t truly call yourself peaceful unless you are capable of violence. If you’re not capable of violence, you’re not peaceful. You’re harmless.
noll
"insensitive prick!" – Danielle Algo
Quote by nicola


LOL, Sprite's post made me think about that exact same scene too. I actually wanted to post it, but decided not to. Good to see you decided otherwise, as it's a great scene.


===  Not ALL LIVES MATTER until BLACK LIVES MATTER  ===
Liz
Scarlet Seductress
Quote by WannabeWordsmith
Weird indeed. You seem to have troubleshot (troubleshooted?) everything I'd have tried.

The only possible reasons I can think of for a network-enabled device on DHCP being inaccessible is because the router is supplying an IP address to either the phone or your PC that are on different subnets/VLANs. Quite why a router would do that out of the box is unclear but maybe it sees the two devices as different classifications and 'conveniently' subnets them for you?

Bottom line as you know: if your VoIP phone and PC are assigned the same subnet it should be pingable and web-accessible on port 80.

Random long shots, none of which I expect to bear fruit:

* Does the phone config software work over port 80 or a custom port? Can the web interface port be changed? I guess if you can't access it, then that's going to be tough!
* Is that port being blocked for whatever reason by your PC's local firewall? (the Windows firewall is a pain in the arse in this regard. Sometimes it even swallows pings for no reason).
* Is the gateway IP on the phone being overridden somehow? Perhaps it's still picking up the old gateway IP from the previous router (or it's been set at some point) and the lease on the new one isn't being released/renewed properly.
* Can you directly connect your PC to the phone in any way using a crossover cable and static IPs? At least that should allow you to get at it. If that works, try using the MAC Binding feature of the router to temporarily deliver the same pair of static IPs to both devices. If it works on static IPs then there's some crazy DHCP issue at play.

I notice that the 'Vac' model of that router has dedicated VoIP functionality so all I can think of is that they're doing some device-level filtering in the 'ac' model to convince you to use their own VoIP provisioning. Sneaky if so.


Thank you for taking the time to respond, WW. I just remembered that I hadn't checked in on this thread since I posted it which was rude of me.

- Phone and PC are on the same subnet.
- The phone's web interface does use on port 80. I don't believe there is an option to set a custom port number.
- No PC firewall issues - the phone is accessible fine using other routers.
- Phone menu shows the correct gateway IP. Have tried several factory resets and it's still not accessible.
- Have tried binding the device IPs to the MAC addresses in the router but that didn't make any difference.
- All of the ALG and VoIP features of the router have been disabled but still nothing.

I had a friend of mine popped over who had a couple of other Draytek Vigor models handy (2862 and 2620). We tried them both with no ADSL connection and the phone worked fine. We could access the web interface with no problem.

It seems to just be this one router model which is causing a problem.

My next job is to play around with Wireshark, recording packet capture on the phone's IP as it boots up and comparing it with a working router.
WannabeWordsmith
Writius Eroticus
Quote by Liz
My next job is to play around with Wireshark


Hardcore! I tried packet sniffing when I was trying to reverse engineer a WiFi extender that was EOL'd by the company and needed a web portal for configuration that they shut off. Hope you have more luck than I did.

It really does sound as if they've deliberately nobbled VoIP on that model doesn't it? Annoying.

Please browse my digital bookshelf. In this collection, you can find 116 full stories, 10 micro-stories, and 2 poems with the following features:


* 29 Editor's Picks, 75 Recommended Reads.
* 15 competition podium places, 11 other times in the top ten.
* 21 collaborations.
* A whole heap of often filthy, tense, hot sex.
Jen
Charming as fuck
Jesus H Christ, you two. You know what nerd talk does to me! I have no idea what the bleep you're on about, but feel free to get naked and keep talking.
Unknown User
Call a professional or take it to the Geek Squad at Best Buy?
kistinspencil
Voyeur @ f/64
Quote by Jen
Jesus H Christ, you two. You know what nerd talk does to me! I have no idea what the bleep you're on about, but feel free to get naked and keep talking.



Ah, Jen? Can I have that top, if you're through with it? No, no. Just as it is, please...