Quote:
Originally Posted by xvaiox
The up to four Gateway VOIP Providers that the adapter supports for outbound calling. I understand that you say it does not register with that provider. However is there a place for the user name and password to use the provider for outbound calling?
|
Yes. The 4 "gateways" let you set userID, password, and proxy. However, all other settings inherit the base "Line 1" provider settings.
In particular, you better be using the "STUN" method of getting past a NAT router if you want to use the "gateways", because if/when you use an optional "Outbound Proxy" with "Line 1" the gateways get that same "Outbound Proxy" (effectively making the gateways useless in that case).
BTW: The (non-obvious) syntax for using the "gateways" is:
"Gateway x:" gets
userid@proxy
"GWx Auth ID:" gets
userid
"GWx NAT Mapping Enable:"
yes
"GWx Password:" gets your account
password
NOTE: Most providers will work OK (for outbound calling) on an SPA-3000/3102 "gateway" (after you put the proper provider info into the gateway, and modify your "dial plan" to be able to optionally dial out via that gateway). However, a small fraction of providers will not accept the gateway's method of sending the userid/password at the time of the call, and therefore will not work on a "gateway". Just letting you know, in case you happen to run across such a provider, and wonder what is going on.
Quote:
Originally Posted by xvaiox
The features that the adapter comes with like Call Waiting, Cancel Call Waiting, Call Waiting Caller ID Detection (Bellcore Type 1)
Caller ID with Name/Number (Multi-national Variants)
Caller ID Blocking
Call Forwarding to PSTN or VoIP Service: No answer, Busy, All
Do Not Disturb
Call Transfer
Three-way Conference Calling with Local Mixing
Message Waiting Indication - Visual and Tone Based
Call Return
Call Back on Busy
Call Blocking with Toll Restriction
just to name a few, will work with what every VSP I put in like Voxalot as long as the features are availible from the VSP correct?
|
Some of those features are actually local to the adapter. And any feature that is fully local to the adapter should work with any VoIP provider you connect with (as it's actually your adapter that is doing the feature in that case, not the VoIP provider).
For example, 3-way calling is really just the ability of the adapter to make two VoIP calls and bridge them. As long as you have enough bandwidth for both calls, and are either using a VoIP provider that allows two calls "at the same time" or are using a different VoIP provider for each call, this feature will work no matter what provider you are using. Likewise, *69 (return previous call) by default (unless you override this behavior in your adapter setup) will just try to place a call to whatever number last showed up on callerID. Again, no provider support is needed, as that logic is fully within the adapter itself.
For the features that aren't local, I would assume they should work through VoXaLot. But the only way to tell for sure is to try and see.
Quote:
Originally Posted by xvaiox
I never like the linksys routers, but you think this is good?
|
These adapters weren't originally designed by LinkSys. They were designed by Sipura, a company that LinkSys later bought out...
That said, some of the earlier LinkSys routers actually had pretty good router hardware in them (although later version of the supposedly same router dumbed down the hardware), it was the router firmware that was iffy. That's why many of us actually still have LinkSys routers, we just no longer have stock LinkSys firmware in them. For example, my router has the open source
http://www.dd-wrt.com firmware in it (making it a much better router than it ever was with LinkSys code in it)...