[shimaspa]

Hi, being my first post, I have to say what a great piece of equipment I think the SPA 3000 is. Without a doubt, this site is the best resource I have found for working through all the permutations of the thing. Kudos to everyone involve here in making this such a valuable site.

okee, the problem:
I can get everything working on line 1 no worries, but I want to have 2 different DIDs, both of which I want to ring my home phone (I have no requirement for VOIP to PSTN gateways)... it seems to me that it must be possible somehow, but I have tried everything I can think of...
Essentially my thinking is that if I can receive calls via the provider registered on the PSTN line that will forward out the FXO port to the landline (either by pin number or CID recognition), then there must be a way to just have that answerable by my phone (just like a call coming in from VOIP on Line 1). I keep thinking if I somehow forward it to it's own loopback address or something... (I couldn't get that to work either)

I really haven't got a good handle on the way the thing works... I'm kind of confused by the whole "PSTN Line" section of the Sipura setup....
Bah lol sometimes I think I'm getting the hang of it, but I can't get that 2nd DID to ring in...

I'm running 3.1.10(GWd) by the way.
So lol , anyone got a configuration that works for this? Am I missing something obvious (wouldn't be the first time *grin*)?
If anyone wants any specifics of my settings at present, just ask, and I will tell you what I can lol.

[DracoFelis]

Short version:

1) If both VoIP providers require you to "register" to receive inbound VoIP calls, you are SOL.

2) If one provider allows you to forward calls to a "SIP URI" (VoIP address) for free, and the other provider accepts inbound calls from SIP URI's, than it is easy. In that case, you forward one provider's inbound calls to the other provider (and have the SPA3000 "register" with that provider you are forwarding to). Both calls will then "ring" (one directly, and the other via the forwarding).

3) If one provider allows forwarding, but the other provider doesn't accept inbound SIP URI calls, you can try the approach shown in this Wiki post. This is a PITA to setup initially, but works very well once you get everything set up:
http://faq.sipbroker.com/tiki-index....%20or%20Sipura

[shimaspa]

Thankyou very much for your response Dracofelis. I do recall actually trying that direct inbound call trick a couple of weeks ago when I first started playing with VOIP... I had trouble then, but I should try it again now that I have a slightly better understanding. I think part of the issue is that I am in Australia, and many of the providers are REALLY poor at even knowing what they allow and don't... documenting that on a decent website is a whole 'nother issue *chuckle*.

[shimaspa]

haha I'm actually getting somewhere. I took option 3 :P (it was really the only option lol) I was stumped for a while because my FWD doesn't seem to forward the call. It works fine from sipbroker and ipkall. Hunted round on the http://www.freeworlddialup.com/community/forum/ (FWD forums), and (surprise surprise) found this post http://www.freeworlddialup.com/commu...pic.php?t=3568 from you Dracofelis :P ...
Anywho, as no-one ever really responded with anything definitive about it, I figure I'll wait and see whether the FWD number eventually forwards. At least it is working fine with ipkall and sipbroker, so I'm reasonably happy.
There is something really sweet about the ipkall coming straight into my ip address. (and I've set up all the E164 and sipbroker stuff too, so there seem to be plenty of options to make the FWD work somehow). I have it set to the sipbroker alias at the moment, coz I know it works from there, and I'll just be patient and wait a couple of days :P
Thanks again for your help df

[DracoFelis]

Originally Posted by shimaspa

\It works fine from sipbroker and ipkall. Hunted round on the http://www.freeworlddialup.com/community/forum/ (FWD forums), and (surprise surprise) found this post http://www.freeworlddialup.com/commu...pic.php?t=3568 from you Dracofelis :P ...

Check out my note at the end of the Wiki here:
http://faq.sipbroker.com/tiki-index....%20or%20Sipura

Specifically look at the note about DNS SRV records vs DNS "A" records. no-ip.com generates "A" records, which FWD seems to have a problem with. FWD seems to require the "SRV" records, which no-ip doesn't supply. So instead I setup a SIP Broker "alias" (that goes directly to my adapter), and pointed FWD to SIP Broker's proxy as my "work around" (as the SIP Broker proxy has both "A" and "SRV" records).

i.e. instead of trying to forward FWD to my VoIP adapter directly (as works with IPKall), I instead setup SIP Broker to forward directly to my adapter, and then forwarded FWD to "SIP Broker". This is one more step "indirect", but it does mean that inbound FWD calls now get to me properly (i.e. FWD => sip:*011xxxxxxx@sipbroker.com => xxxxxxx@yyyyyyy.no-ip.zzz ). Also, don't forget that FWD expects the word "sip:" at the front of the string, or the forward won't work!

NOTE: FWD seems to have a big problem with the updates to the web site not quickly changing the forwarding on their service. So it is common to have to wait a few DAYS for the forwarding to "kick in". And if it doesn't kick in within about a week's time, you may need some tech help from someone at FWD to look at things. But "the good news" is that the forwarding (at FWD) works well when you do eventually get it set up correctly on the FWD end...

[shimaspa]

Cool, I had read that bit about the DNS "A" and "SRV" records. I kind of suspected from inference that FWD was one that had an issue with the "A"s. I have set mine up exactly as you have suggested (ie: FWD => sip:*011xxxxxxx@sipbroker.com => xxxxxxx@yyyyyyy.no-ip.zzz ) and as soon as the forwarding kicks in from FWD it will all work beautifully.

Also, don't forget that FWD expects the word "sip:" at the front of the string, or the forward won't work!

They have actually set it up now to not accept the change without the sip: at the front of the string.
(funny because as an error checking process, once you have checked to see whether someone's URI starts with that string, and determined that it doesn't, you might as well just put it there for them and continue *chuckle*)

Not that I really understand the full process of DNS look ups (particularly as it relates to voip), but I suspect that having a fixed IP as the URI to forward to, should work from FWD too. Logic suggests that using an IP address negates much of the lookup process. I will wait until I have it working with the sipbroker trick first, and then try it, as I have a fixed IP. The less legs on the journey the better of course lol.