| |
| News & Reviews |
Welcome to the Voxilla VoIP Forum.
Voxilla has been a trusted source for accurate, up-to-date information on the IP Communications industry since 2002. A dedicated staff of reporters and engineers produce feature articles and product reviews to keep industry watchers abreast of the people, companies, and trends driving a fast moving market.
You are currently viewing our boards as a guest which gives you limited access to view most discussions and access our other features. By joining our free community you will have access to post topics, communicate privately with other members (PM), respond to polls, upload content and access many other special features. Registration is fast, simple and absolutely free so please, join our community today!
If you have any problems with the registration process or your account login, please contact contact us.
Voxilla VoIP Forum |
Using IconnectHere on SPA3000 "gateway" entry?Questions, concerns, comments, tehnical support, how-to guides, troubleshooting, general assistance, and discussion about iConnectHere (ICH). |
| | LinkBack | Thread Tools | Rate Thread | Display Modes |
| ||||
| Anyone got IconnectHere working (for outbound only) as one of the 4 "gateway" providers of a SPA3000? No big deal if I can't get it working, as the promo account has under $3 in it. But just for grins, I decided to try out my free IconnectHere account, that came with my SPA3000. Now naturally, the instructions called for using the Wizard to configure things, and just as naturally the wizard's settings won't work without overwriting the providers I already have programmed into my SPA-3000 (I've already got FWD as the main "Line 1", and both DialPad.com and Teliax.com as "gateway" providers). So I figured I would just manually setup IconnectHere as "gateway 3", right? Only trouble is it doesn't seem to be working (I just get a fast busy when I try to dial). However, I know the (promo) account is good (and I have the correct 8 digit account number AND 4 digit password), both because I can log into the web portal with that info AND because I can call out from FWD (using the **334 gateway to IconnectHere) with that info. And I copied the GW3 provider "dial plan" pattern directly from my GW2 pattern (only changing the gateway used, and the digit to select the provider), so I don't think it's the dial plan either. But I still get a "fast busy" when I try to use it directly. Here are the SPA3000 settings that are going nowhere: Gateway 3: my_8_digit_account@natrelay.deltathree.com GW3 Auth ID: my_8_digit_account GW3 NAT Mapping Enable: yes GW3 Password: my_4_digit_password Dial Plan pattern (dial via "# 7 number_to_dial #"): <#7:>[x*].<#:>S0 <:@GW3> BTW: These are the same sorts of settings (obviously with different account numbers) that work fine with both my "gateway 1" provider (DialPad.com), and my "gateway 2" provider (Teliax.com). But for some reason I'm not getting anywhere when I try this with IconnectHere and "gateway 3". Anyone know of a setting I'm missing, or have wrong (for this provider)? |
| |||
| Hi, I have the same settings as yours except for the dial string. My dial string for gateway 2 is <#2,:>xx.<:@gw2> However voice quality is highly choppy in a call, almost unintelligible. Could this be a codec problem. Is there a way the preferred codec can be forced using the dialstring for the outbound gateway on the SPA 3K. |
| | |
![]() |
| |||
| Dracofelis, i have the same problem, but i still having the same fast busy tone can you send tell me how the correct configuration parameters for Line 1 with FWD (FREE WORLD DIAL UP) for inbound calls and Deltathree account as Gateway 1 for outbound calls, i will appreciate very much your cooperation with this issues i am having. regards Jaco Quote:
|
| ||||
| Quote:
http://www.broadbandreports.com/forum/remark,14179920 NOTE: I have discovered that sometimes the Sipura just refuses to have settings "take" until you "power cycle" the adapter. So you might also try unplugging the adapter, waiting a few seconds (to make sure the adapter is fully "powered down"), plugging it back in, and again waiting a few seconds (for the adapter to finish "registering"). |
| |||
| Jaco, I have FWD setup as my LINE1 (for incoming calls via ipkall), and use ICH os GW1 and another account from ICH on GW2 for outgoing calls. I have this setup for over 2 months now and going great. |
| |||
| Quote:
|
| Thread Tools | |
| Display Modes | Rate This Thread |
| |
| | ||||
| Thread | Thread Starter | Forum | Replies | Last Post |
| Problem Solved (SPA3000 "fast busy" with <:@gw | DracoFelis | Linksys (Sipura) VoIP Support Forum | 7 | September 15th, 2006 11:25 AM |
| SPA3000: Voip to PSTN issue with "#" for PIN auth | jdeelizalde | Linksys (Sipura) VoIP Support Forum | 9 | July 31st, 2006 05:48 AM |
| SPA3000 "restrict source ip" purpose and function | j_friedrich | Linksys (Sipura) VoIP Support Forum | 0 | November 23rd, 2005 11:46 PM |
| Sipura fixed the "Gateway Provider" not working pr | PhoneBoy | Linksys (Sipura) VoIP Support Forum | 13 | November 30th, 2004 11:34 AM |
| SPA3000 Getting "VoIP Dialing Timeout" on PSTN ca | sagitel | Linksys (Sipura) VoIP Support Forum | 11 | November 20th, 2004 06:18 PM |