[binro]

My company has just given me an SPA-2100 which I am currently regarding with grave suspicion. My current LAN set-up is I have a D-Link ADSL wireless modem/router which has address 192.168.1.1. Connected to that in the router DMZ is my desktop/server which is configured as 192.168.1.2. There are also a couple of notebooks which connect via wireless. The server has various well known ports open to the internet. I do not use DHCP since the hosts communicate with each other via IP addresses defined in /etc/hosts (these are, of course, all Linux boxes ).

It seems I must connect the SPA to the D-Link and the server to the SPA. After this the config becomes misty to me. The ADSL connection is PPPoE which is currently defined (userid/password) in the D-Link, but know I must do this in the SPA? The SPA has a pre-configured address of 192.168.0.1, in which case, what is now the gateway address for the server? Is the SPA box somehow 'transparent' to the server. Will the server still be in the DMZ and visible to the internet? It seems to me most of the answers are "no". Can I perhaps still connect the server directly to the D-Link and connect to the SPA as another LAN host?

Any advice will be much appreciated!

[hwittenb]

I would try to give it a static ip address and attach it to your DLink modem/router.

http://www.sipura.com/Documents/SPA2...plement1.1.pdf

[binro]

Thanks for the link. Are you suggesting I connect the PC (server) to the SPA and give it a static IP and gateway address and then reconnect the PC directly to the D-Link?

[hwittenb]

Originally Posted by binro

Thanks for the link. Are you suggesting I connect the PC (server) to the SPA and give it a static IP and gateway address and then reconnect the PC directly to the D-Link?

Perhaps you can't make it work, but I was suggesting that you don't use the SPA as a router, just attach it to the DLink along with everything else. Maybe you need a switch to do this.

[binro]

Originally Posted by hwittenb

Perhaps you can't make it work, but I was suggesting that you don't use the SPA as a router, just attach it to the DLink along with everything else. Maybe you need a switch to do this.

I'll give it a try tomorrow. It's certainly the best (easiest) solution for me.

[binro]

I think the confusion in the doco for me is that it assumes the ADSL modem and the router are separate devices and the SPA can sit in between them, whereas in my new D-Link DSL-G604T they are integrated.

So I connected a laptop to the SPA LAN port and got the menu pages. I configured the WAN as static IP on my LAN with the usual netmask, gateway, DNS stuff. So now the SPA is active on the LAN like any other host, the only thing is it will not register. If I set "Make Call Without Reg" I get a dialling tone, so the hardware seems good. I discovered the syslog/debug settings and set it up to route logging to my main server. (This required an upgrade to the 3.3.6 firmware to work.) When I reboot at debug level 3 I do not get very much output:

Nov  9 18:07:58 sipura system request reboot
Nov  9 18:07:58 sipura fu:1:3fdf, 0038 043c 0445 0001
Nov  9 18:07:58 sipura fu:1:4036, 03e4 05b0 0001
Nov  9 18:08:01 sipura System started: ip@192.168.1.20, reboot reason:H30300010
Nov  9 18:08:01 sipura System started: ip@192.168.1.20, reboot reason:H30300010
Nov  9 18:08:01 sipura 	subnet mask:	255.255.255.0
Nov  9 18:08:01 sipura 	gateway ip:	192.168.1.1
Nov  9 18:08:01 sipura 	dns servers(2):	
Nov  9 18:08:01 sipura 203.146.0.20 
Nov  9 18:08:01 sipura 203.146.0.30 
Nov  9 18:08:01 sipura 
Nov  9 18:08:11 sipura IDBG: st-0
Nov  9 18:08:12 sipura fs:10427:10500:65536
Nov  9 18:08:12 sipura fls:af:1:0:0
Nov  9 18:08:12 sipura fbr:1:3000:3000:14036:0004:0005:3.3.6
Nov  9 18:08:12 sipura fhs:01:0:0001:upg:app:0:3.2.2(g)
Nov  9 18:08:12 sipura fhs:02:0:0002:upg:app:1:3.2.2(g)
Nov  9 18:08:12 sipura fhs:03:0:0003:upg:app:2:3.2.2(g)
Nov  9 18:08:12 sipura fhs:04:0:0004:upg:app:0:3.3.6
Nov  9 18:08:12 sipura fhs:05:0:0005:upg:app:1:3.3.6
Nov  9 18:08:12 sipura fhs:06:0:0006:upg:app:2:3.3.6
Nov  9 18:08:12 sipura fu:1:405d, 0003 0001

Anyone know what is (not) going on?

TIA

[hwittenb]

If you have access to the Admin - Advanced login Line tabs, there is also a SIP Debug Option: setting on the line tabs that you should set to full. With that you should see register attempts if you have the credentials set and have register YES set. If you have NAT Keep Alive set to yes you will also see Notify activity.

The best reference document for the SIP settings is located on the Sipura web page: http://www.sipura.com/Documents/Sipu...uidev2.0.9.pdf

There is also some good documentation here:
ProVu Communications: Product Support

[binro]

Thanks very much for the tips, I'll get tracing.

[binro]

Ok, one major problem solved. After scanning suggested configs on the Sipura site I realised that the idiot in my company who had "preconfigured" the SPA had forgotten to set the proxy address! A minor point but it makes all the difference. Now the SPA registers and I can make outbound calls. With incoming calls, the telephone rings but there is no voice.

The advice is to open port 5060 on the firewall. My router does not have an active firewall because that's on the main server, which is in the DMZ and thus receives all incoming new sessions. So I added rules to the server's firewall to pre-route connections on port 5060 to LAN address 192.168.1.20, which is the SPA. This does not make any difference. There are strange suggestions from colleagues to open ports 10000:30000 but this seems insane. However, in the Sipura set-up Application menu I see references to system reserved ports 50000+10000 with a range of 256. What are the significance of these? Should they be forwarded?

TIA

[binro]

Ok, I searched this forum and found the solution. Apparently by default the unit uses ports 5060:5061 and 16384:16482. When I forwarded these from my router to the SPA, inbound calls started working. I guess the advice to open 10000-30000 will have the same effect but seems a little extreme to me!