Anyone here managed to get VOIP working on the Z100G?

I have been trying to get my Broadvoice account connect to my Asterisk box for the last week with no luck. I have been in contact with support on this since last week and so far we got nowhere.

I have a rule with any service from Broadvoice proxy ip to my Asterisk box IP.

To rule out Broadvoice as the culprit I have tried swapping the Z100G with my old Linksys and the line registered in about two seconds.
I also set up a new account with VoiceStick for testing purposes and it fails too on the Z100G while registers correctly on the old Linksys.

Hopefully someone here got further than I did and could land some advice.

I really love this product and would hate to go back to my old Linksys!

quote:

Originally posted by Issacsim:
Anyone here managed to get VOIP working on the Z100G?

I have been trying to get my Broadvoice account connect to my Asterisk box for the last week with no luck. I have been in contact with support on this since last week and so far we got nowhere.

I have a rule with any service from Broadvoice proxy ip to my Asterisk box IP.

To rule out Broadvoice as the culprit I have tried swapping the Z100G with my old Linksys and the line registered in about two seconds.
I also set up a new account with VoiceStick for testing purposes and it fails too on the Z100G while registers correctly on the old Linksys.

Hopefully someone here got further than I did and could land some advice.

I really love this product and would hate to go back to my old Linksys!

I have not set up VOIP, to say nothing about your specific one, but here is my two cents worth anyway.

- Make sure that you can ping your VOIP device on the IP address you gave it.

- Make sure the VOIP device has a static IP and set up a "Network Object" for it. You can also do this through the Z100G in the Network Object you set up for the device.

- Find out what ports the device needs - both ways - and set up rule(s) that allows all traffic on those ports both ways between the Netowrk object on the LAN and the Internet (WAN). You may need multiple rules if there are multiple ports. If the device is promiscuous in its use of ports, you may have to allow all ports going out.

- Set the rule(s) to log accepted connections so that you have an idea of which rules are working and those that are not.

- Refresh the logging page as you make the attempt.

KBR,

Thanks for the reply,

1. I can ping fine.
2. I do have it as a "Network Object"
3. I have two rules with "Any Service" going both ways.
4. I do have the rule set to log accepted connections but it would only show one entry even though the server keeps on trying constantly to register. I did run the packet sniffer and there is traffic on the WAN port going t the correct IP, but none of it shows in the log.

I use Vonage via a Linksys box they supplied about 2 years ago. I configured the Z100G so the Vonage box is an "Exposed Host", and it works just fine. I have no idea what the Z100G may be doing for an Exposed Host. Does anyone know ?

Exposed host does not get any protection from the appliance.

I have vonage and it works well. I have the linksys router supplied listed as a H.323 server under the z100g SECURITY/SERVERS. I point it to 192.168.10.2 and on the linksys itself I gave the WAN (Internet side) the STATIC IP of 10.168.10.2. Works well.

I am using an Asterisk server (trixbox.org). Broadvoice been working fine with my config for more then two years. Will not work behind the Z100G.

Support have great and tried many thing, none seem to help.

Tried the linksys again and the line is working fine again.

I am not giving up yet...

The quick and dirty fix is to shove the voice over ip box to the other side of the wall, using exposed host.. Id really like to see better configuation for voip/qos perhaps STUN support. Should suggest it in the suggestions forum

We have tried it as an exposed host, did not help.

I realize this is an old thread ;-)
But were any conclusions reached here?
I am surprised that setting the device as an exposed host (while not perhaps the most elegant solution) did not fix things up....

Thanks,
Jim

Please the following
under smart defense,
make sure that in the tree you have the oprion for voip and under SIP that
SIP Protocol Handler - disabled
RFC non-compliant messages - none
please update this forum

sagy

Sagy:

Thanks for the note!

The router has the current firmware V7.5.48x and with security set at MEDIUM the Vonage VoIP adapter seems to work fine with no adjustments needed.

(it is just the phone adapter - no router or other equipment built into it)

This was kind of a shock to me, but I figured I would install the Z100G and see what happened and well.... it works with no apparent need for modifications ... or maybe the "need" will not show up until later ... I was able to call in and out ...

Thanks,
Jim

Jim,

Vonage adapter and other ATA's are using stun servers to transverse the firewall and will work out of the box with almost any firewall.

Sagy,
I have tried the new SIP Protocol Handler with both enabled and disabled and RFC non-compliant messages = none. Did not resolve my problem.

I unplugged the Z100G and tried both my linksys and pfSense boxes, and with both the line came on within a few seconds and I was able make and receive calls.

When using an ATA similar to the one used by Vonage I can make calls, but for now Asterisk and the Z100G still don't like each other :-(.

Issac:

Thanks ... I guess I got off easy ... that's a nice change for me ;-)

I had forgot about STUN but just went back and re-read the RFC pretty clever stuff!

Next I'm going to work converting my home line to Vonage... the savings seem worthwhile.

Thanks,
Jim