Home » Forums » Community Edition » Open Discussion

Snom SIP phone behind a Linksys WRT

HDS
Posts: 3
 Member Since:
2010-05-20
Submitted by HDS on Thu, 05/20/2010 - 9:22am.

Hi Everyone

I'm new to the forum and need some expert advice..

I have a LinksysWRT in my testlab and have an issue that i need assistance with.

(LAN--A)
I have an Trixbox PABX that is on the network. IP (10.11.200.1/255.255.0.0)
I have a Internet gateway on the network. IP (10.11.100.1/255.255.0.0)

I have a LinksysWRT on the network with the WAN port IP (10.11.30.1/255.255.0.0/10.11.100.1) plugged into (LAN--A) and one of the four ethernet ports of the WRT plugged into (LAN--B)

(LAN--B)
I have one PC that gets it's IP from the WRT through DHCP. IP (192.168.1.2/255.255.255.0)
I have one Snom300 phone with a Static IP that is set up to register with the Trixbox on (LAN--A) IP (10.11.1.135/255.255.0.0)

As you can imagine, once everyting is set up, the pc on (LAN--B) can connect to the internet, but the phone cant register with the Trixbox on (LAN--A)

Is there a way to enable the phone to register with the Trixbox although it is behind the WRT because it cant be done with the default firmware? Maybe with DD-WRT?

Thank you
And i apologize if none of this makes any sense.. (If you follow the steps and draw a picture it might help..)

‹ Asterisk and the loss of Internet Which 2.8 version should I install? ›


Astrosmurfer
Posts: 643
 Member Since:
2009-12-28
Two things are needed here.
Thu, 05/20/2010 - 1:05pm

Two things are needed here.

The default configuration of the Linksys WRT device should allow the phones on 192.168.1.0/24 to work. To resolve your issue, I would attempt the following steps.

First, place the Snom phone on the 10.11.0.0/16 subnet and get it working "locally". Then I would move the Snom to the 192.168.1.0/24 network and enable NAT on the extension. I would then expect it to work. But, if it failed, I would then try forwarding UDP ports 10000 - 20000 on the WRT to the Snom.



HDS
Posts: 3
 Member Since:
2010-05-20
No Luck
Fri, 05/21/2010 - 1:01am

Hey Astrosmurfer

Thanks for you advice, i had high hopes that it would solve the issue but it didn't work.
The phone work fine when connected to the local (LAN--A) network but even with NAT enabled on the extension it doesn't work behind the WRT.

Should i be able to ping the SNOM phone with IP (10.11.1.135/255.255.0.0) when it is behind the WRT? I can obviously ping it when it is local.

Also, i cant forward the UDP ports on the WRT to the Snom because the only IP range i can forward it to is 192.168.1.X.
As you know the phone is set to static (10.11.1.135/255.255.0.0).

Any ideas?



nttranbao
Posts: 189
 Member Since:
2008-02-16
There is no way for SNOM
Fri, 05/21/2010 - 2:29am

Yes as I imagine, there is no way for SNOM with current setup to connect to Trixbox. You put SNOM in subnet B (192.168.1.0) and assign IP of 10.11.1.135???. Wrong configuration. The IP phone can not even see/reach the WRT!

Solution: assign SNOM an IP of subnet B, i.e. 192.168.1.55/24, with Default gateway of WRT IP (192.168.1.1, I guess). Or easier, have SNOM lease dynamic IP from WRT.

And normally no need to open port on WRT pointing to SNOM.
-----------------
IT/VOIP consultancy, VOIP eStore, Support Forum
Bao Nguyen IT Co., Ltd.
http://www.baonguyen.vn
WE MAKE IT

--

----------------------
IT/VOIP consultancy, VOIP eStore, Support Forum
Bao Nguyen IT Co., Ltd.
http://www.baonguyen.vn
WE MAKE IT



nttranbao
Posts: 189
 Member Since:
2008-02-16
you can make all current
Fri, 05/21/2010 - 2:24am

Moreover, you can make all current devices into one single subnet and worry none about routing, Nat, Port forward....

The below instruction will help remove lan B, and join all its devices into lan A.
1. Disable DHCP on WRT
2. Unplug the cable connecting to WAN port on WRT -> plug it to one of WRT's 4 ethernet ports
3. Now renew the IP on both PCs and SNOM. They should receive IPs of 10.11.x.y

--------------------------
IT/VOIP consultancy, VOIP eStore, Support Forum
Bao Nguyen IT Co., Ltd.
http://www.baonguyen.vn
WE MAKE IT

--

----------------------
IT/VOIP consultancy, VOIP eStore, Support Forum
Bao Nguyen IT Co., Ltd.
http://www.baonguyen.vn
WE MAKE IT



HDS
Posts: 3
 Member Since:
2010-05-20
No solution
Fri, 05/21/2010 - 6:24am

Hi nttranbao

The configuration that you are proposing will not work for me.
That is the easy way out, yes I agree but i don't think you understand exactly what i want to achieve..

The reason for my current setup is as follows:

-I want the PC on (LAN--B) to be able to connect to the internet using the WRT as it's gateway and getting a different IP from the WRT (192.168.1.X).
This is currently working perfectly.

I dont want the PC on (LAN--B) to be able to access the (LAN--A) network, they are from different company's and i don't want them to see each others files.
That's why I cant put everything on one network.

The trixbox is on (LAN--A) and the Snom phone in behind the WRT on (LAN--B).
Surely there must be a way to configure the router (maybe with different firmware) to register with the trixbox. Is there no way to route through the WAN port?

Imagine i am a service provider, i have 5 clients with 5 WRT's with PC's behind those WRT's.
I have one internet gateway and one PBX.

I don't want the different clients to see each others files, but i want them to use the same PBX for calls and the same gateway for internet.
They can all use the same gateway (that part is sorted) but the phone issue is a problem..



SkykingOH
Posts: 9541
 Member Since:
2007-12-17
I can't imagine you are a
Fri, 05/21/2010 - 10:21am

I can't imagine you are a service provider as a they would have engineers that understand routing and switching.

Now that I am done busting chops, some questions.

All these customers are in the same building and sharing one Internet drain? This is a key point.

If this assumption is true you need to create a DMZ. NAT needs to be off on all of the customer routers and the perimeter router that connects to the Internet needs to perform NAT and be aware of all the customer subnets via a summarized router that includes them, IE: 192.168.0.0/16 would give you 254 customer LANS.

The DD-WRT is fine as the customer router, you need to have a router with a larger feature set to handle issues such as this at the core.

I am a service provider, when we light a building we put in a layer 3 switch that can form the gateway for each customer network. That way the only customer equipment is a layer 2 switch.

--

Scott

aka "Skyking"



Astrosmurfer
Posts: 643
 Member Since:
2009-12-28
I'm not sure I understand
Tue, 05/25/2010 - 5:29am

I'm not sure I understand what you did exactly. Did you move the phone to the 192.168.1.0/24 subnet without changing its address? The phone still has the 10.11.1.135 address while connected to the 192.168.1.0/24 network? That will not work.

When you move the phone to the 192.168.1.0/24 network you must change the address on the phone to a valid address on that subnet.

You will not be able to ping from the 10.11.0.0/16 network to the 192.168.1.0/24 network. But, you should be able to ping from the 192.168.1.0/24 network to the 10.11.0.0/16 network.



Comment viewing options

Select your preferred way to display the comments and click "Save settings" to activate your changes.