I have never experienced any echo problems with the spa-3102 in that type of scenerio or for that matter cross talk. The only real difference between the spa-3000 and spa-3102 is that the 3102 can act as a router where the spa-3000 is a LAN device. The firmware on these units are more up-to-date than the spa-3000 so that may have something to do it. Hope that helps.

I am getting instructions created as we speak and will update everyone on how to obtain them when available. I will like to note that when these instructions become available, they were tested and proved working with a PSTN landline (NOT using an analog PBX connected to station line) as this is another common application for this device. Like I said I will update everyone when this becomes available.

Thanks,

Chris Heinrich

The two devices talk to each other via IP addresses. It is strongly suggested when using these devices in a point to point (spa-3102 to spa-3102 pure VOIP) and back to back (spa-3102 over VOIP to spa-3102 then out PSTN) that you set each unit’s IP address statically. Using them within a VPN or LAN environment cuts down on NAT issues and one way audio issues, and even placing both units on “public” static IP addresses provided by your ISP is suggested. There is often a charge associated with this however. And you can also use this device as an external FXO gateway to your Asterisk server as well.

Let me see if I can use HTML definitions to insert those special characters.

([3469]11S0<:@gw0>|[2-9]xx[2-9]xxxxxxS0<:@gw0>|1800xxxxxxxS0<:@gw0>|1888xxxxxxxS0<:@gw0>|1877xxxxxxxS0<:@gw0>|1866xxxxxxxS0<:@gw0>|1855xxxxxxxS0<:@gw0>|1xxx[2-9]xxxxxxS0|xxxxxxxxxxxx.)

([3469]11S0|[2-9]xx[2-9]xxxxxxS0|1800xxxxxxxS0|1888xxxxxxxS0|1877xxxxxxxS0|1866xxxxxxxS0|1855xxxxxxxS0|1xxx[2-9]xxxxxxS0|xxxxxxxxxxxx.)

I would imagine these can be placed anywhere worldwide and could then port local PSTN telco lines into my Asterisk PBX server. :o)

Thanks,
Mike