republican-creole
Search:  

 
 
   All ForumsHot TopicsGallery






how-to block ads


 
Forums » VOIP etc » Voice Over IP - VOIP » VOIP Tech Chat » [Equipment] Useful Sipura tricks...
Share Topic:
RSS topic:
toggle:
flat / full
normal / watch
Posting:
Post a:
Post a:
[General] PAP2 v2 and syslog »
« [VoiceStick] SIP Ports  

DracoFelis
Premium
join:2003-06-15

Re: [Equipment] Useful Sipura tricks...

Here's a couple more that I was able to figure out today. I was experimenting to see if there was some way I could forward incoming calls on my SPA-2000 "Line 1" (FWD), automatically to "Line 2" (my DialPad.com line). I wanted to do this, so that I didn't need to have a phone hooked up to the Line1 port of the SPA, in order to receive FWD calls (remember, I can already DIAL FWD calls from "Line 2", that "trick" is shown in a previous note in this thread).

Call one line of the SPA from the other line:
This is not especially useful (more of a "parlor trick"), but it was a good "learning experience" in trying to get "forwarding" to work. Believe it or not, the SPA-2000 can directly call one line from the other (by using the internal "loop back" IP address)! Here's how:

First make sure that each "Line" on the SPA is setup with a unique SIP port, and a unique userid (i.e. make the settings for these two values different for each line). You will also need to set "Make call without reg: Yes" on the calling line, and "Ans Call Without Reg: Yes" on the line receiving. And you will also have to make sure that the lines have at least one CODEC in common (it might as well be "G711u", since the "call" is "internal" to the SPA). Finally, you will have to setup a "dial plan" to call the other line, at "userid@127.0.0.1:sip_port".

For example, if the other line is on SIP port 5063, and is userid "testing", than you can call that line (from the other one) by pressing #1 if you have the following as part of your "dial plan":
<#1:> S0 <:testing@127.0.0.1:5063>

And now (drum roll), how to forward all inbound calls to the OTHER line:
This is VERY USEFUL, because it either lets you have a TWO VoIP accounts that both "ring" the same phone, OR lets you use one account for all incoming, and a 2nd account for all outgoing (by putting the "phone" on the line with the outgoing VoIP service, and then forwarding all incoming calls on that other VoIP line to that one)!

NOTE: This theory was tested earlier this evening, by forwarding my SPA-2000's "Line 1" (setup for FWD) to "Line 2" (setup for DialPad.com), and then calling my FWD number from Packet8. After I finally got all the pieces in place, my "Line 2" was happy to "ring", and when I picked up that phone 2-way talking worked fine! So this appears to work (at least for me). But naturally YMMV.

Here are the needed pieces:

1) As in the previous "trick", you need unique SIP ports and unique userids for the two lines. NOTE: It's quite OK to use whatever "userid" the provider on that line supplied (for logging into their SIP proxy). You don't need the UserId set to any specific value, just something unique!

2) Again, the line you are forwarding from will need "Make call without reg: Yes", and the line you want to forward to will need "Ans Call Without Reg: Yes".

3) If you are behind a router (I am), you will need to forward the SIP port of the line you want to ring (the line you are forwarding to) to the SPA. This is probably much easier if you program the SPA for a "static LAN IP" (instead of using DHCP).

4) Your external address will need to either be "static", _OR_ you will need to use a dynamic DNS service (btw: I'm happy with the free dynamic DNS service from »www.no-ip.com ). This is necessary, as you will need to always know the internet address of your SPA-2000 (not the LAN address, the "external address") for forwarding to work.

5) Turn on "Cfwd All Serv: yes" on the line you are forwarding "from" (i.e. if you want calls to the VoIP on "Line 1" to ring "Line 2", than you set this on "Line 1").

6) Go over to the "user" tab for the line you are forwarding from, and setup the "Cfwd All Dest:" field as "userid@external_address:sip_port". For example, if your dynamic DNS entry is "dummy.no-ip.com", your target line's userid is "testing", and the target line's SIP port is 5063, than you would want to "Cfwd All Dest:" to "testing@dummy.no-ip.com:5063".

NOTE: I was NOT successful in getting the loopback address (127.0.0.1) working for call forwarding (even though it worked for calling one line from the other, above). I had to use the "external address" for the SPA, to get forwarding to work (even between one line and the other on the same Sipura adapter)!

7) Test the setup. The easiest way is to get a friend to call the VoIP number you are forwarding from, and see if the forwarded to line "rings". In my case, I verified the setup by using my Packet8 account (and the Packet8 to FWD gateway) to call my FWD line (line 1 of my SPA-2000), and have the DialPad.com line (Line 2) ring! I then picked up the phones, and verified that two-way talking was working. Success!!!

BTW: So far there has only been one other poster in this thread. I'm sure the two of us can't be the only ones trying to figure out what our Sipura adapters are capable of! So please join in and post your "tricks". I'd hate to have this thread degenerate into just DracoFelis' book of Sipura tricks....
tlpintpe

join:2002-09-13
Spicewood, TX

Re: [Equipment] Useful Sipura tricks...

I have my 3000 using voxee on line 1. I used the voxilla.com SPA 3000 wizard to configure the spa, leaving their dialplan unchanged.

When I try to add the "tricks" to force dialing toll free numbers over the FWD method, the dialplan is truncated and nothing then works.

Is there are 255 character limit per dial plan?

Can I move the voxee line to the PSTN Voip line and thus have access to lots more dial plan lines?

DracoFelis
Premium
join:2003-06-15


1 edit

Re: [Equipment] Useful Sipura tricks...

said by tlpintpe See Profile:

Is there are 255 character limit per dial plan?
I'm wondering if it is your browser doing the truncation on the fields, as my current "Dial Plan" is already well over 255 chars. And from the Sipura SPA-3000 manual, we have this comment:

Notes:  - The dial plan length limit for <Dial Plan 1> through <Dial Plan 8>
is 511 characters. This is less than that for the <Dial Plan> under [Line 1],
which is 2047 characters.
tlpintpe

join:2002-09-13
Spicewood, TX

Re: [Equipment] Useful Sipura tricks...

said by DracoFelis See Profile:

said by tlpintpe See Profile:

Is there are 255 character limit per dial plan?
I'm wondering if it is your browser doing the truncation on the fields, as my current "Dial Plan" is already well over 255 chars. And from the Sipura SPA-3000 manual, we have this comment:

Notes: - The dial plan length limit for through is 511 characters. This is less than that for the under [Line 1], which is 2047 characters.
I am using Firefox on Linux, but I'll give it a go with Konqourer and see if that helps.

DracoFelis
Premium
join:2003-06-15

Re: [Equipment] Useful Sipura tricks...

said by tlpintpe See Profile:

I am using Firefox on Linux, but I'll give it a go with Konqourer and see if that helps.
That's odd then, because I do my dial plans with FireFox on Windows (and FF usually behaves pretty much the same cross-platform). Since I'm not getting Dial Plan truncations, I don't know why you would. As I said, odd...
tlpintpe

join:2002-09-13
Spicewood, TX

said by DracoFelis See Profile:

said by tlpintpe See Profile:

Is there are 255 character limit per dial plan?
I'm wondering if it is your browser doing the truncation on the fields, as my current "Dial Plan" is already well over 255 chars. And from the Sipura SPA-3000 manual, we have this comment:

Notes:  - The dial plan length limit for <Dial Plan 1> through <Dial Plan 8>
is 511 characters. This is less than that for the <Dial Plan> under [Line 1],
which is 2047 characters.
I finally got it.

I think it was me trying to just cut and paste from your entries (dialing toll free numbers via FWD) that was the culprit. There is a carrage return in there, and when I edited the dial plan in a text editor, and removed the carrage return, then reentered the dial plan, all worked as it should.

Thanks for the great tips!

DracoFelis
Premium
join:2003-06-15


1 edit

Re: [Equipment] Useful Sipura tricks...

said by tlpintpe See Profile:

I think it was me trying to just cut and paste from your entries (dialing toll free numbers via FWD) that was the culprit. There is a carrage return in there, and when I edited the dial plan in a text editor, and removed the carrage return, then reentered the dial plan, all worked as it should.
Yep. A "dial plan" for a Sipura should all be on one line. Please ignore any extra "line breaks" in the examples. They are simply because BBR doesn't support 2K long text lines (without wrapping), whereas the Sipura dial plan does...

While we are on the subject of "dial plans", here are a couple of cute ones. Since SIPphone.com accepts inbound "peering", you can directly call any SIPphone.com account (which all have numbers in the form: 1 747 xxx-xxxx) by adding the following to your Dial Plan (before your normal LD pattern):
1 747 xxx xxxx <:@proxy01.sipphone.com>
And potentially even more interesting, is that you can use the "phone conferencing" ability of SIPphone (even if you don't have a SIPphone account), by adding the following to your Dial Plan (again before your normal LD pattern):
1 222 xxx xxxx <:@proxy01.sipphone.com>
p2pvoice

join:2003-10-28
Dover, NH

Re: [Equipment] Useful Sipura tricks...

DracoFelis:

I have SPA1001 with two virtual lines. Line 1 is set up for "home" and Line 2 is set up for "business" with a different ringtone. Each line is an extension on my Asterisk server. So, by using a single phone, I can tell from the ringtone, whether an incoming call is a "home" call or a "business" call. I use primarily Line 1 for outgoing calls using Asterisk's outbound routing.

Here is the "trick: I need to implement:

My business number is an IPKall number, which "points" to my "business" extension on my Asterisk server.

My home number is "ported" to an ITSP and it "points" my "home" extension.

This ITSP is fully 911 compliant; however, I use this ITSP for incoming calls only (don't use this ITSP for outgoing calls). Since this ITSP is fully 911 compliant, I would like only the 911 call to go through this ITSP instead of the other ITSPs configured in my Asterisk's outbound routing.

Will this "trick" (inspired by your SIPPhone post) work?

911

I don't know where to put UN/PW?

BTW, my Asterisk server is registered to My911ITSP.com

Thanks

p2pvoice

join:2003-10-28
Dover, NH

Re: [Equipment] Useful Sipura tricks...

In my previuos post, "cut and paste" didn't work properly.
Here is the corrected section:

Will this "trick" (inspired by your SIPPhone post) work?

911 S0 <:@My911ITSP.com>

I don't know where to put UN/PW?

Thanks

DracoFelis
Premium
join:2003-06-15

Re: [Equipment] Useful Sipura tricks...

said by p2pvoice See Profile :

Will this "trick" (inspired by your SIPPhone post) work?

911 S0 <:@My911ITSP.com>

I don't know where to put UN/PW?
In order to use an alternate (not your "registered") VoIP account for 911 (only), you would need one of the following options:

A) Have a VoIP provider that doesn't require you to supply a userid/password. This is highly unlikely for 911, as how would that provider be able to identify you to the 911 folks if you don't log in.

B) Or arrange to have the userid and password for "My911ITSP.com" be the same as the userid/password that you are using for the VoIP provider on the line. This may be possible, if "My911ITSP.com" allows you to pick your userid and password. In that case, just make sure you pick the same userid/password as your main VoIP provider is using (for that line), and when when you redirect to "My911ITSP.com" (using your above dial plan trick) it will properly authenticate, because redirecting to an alternate proxy will still use the registered VoIP's userid and password.

C) Or if you have an SPA-3000 (but not the other model Sipuras), you could put "My911ITSP.com" onto a "gateway" slot, and then modify your dial plan to dial via that gateway. For example, if the login credentials for "My911ITSP.com" were on "gateway 4", you could force all 911 calls out via that provider by using:
911 S0 <:@GW1>

Warning:
I do NOT have a VoIP company with true 911, and I wouldn't want to test this even if I did. So while all this should work "in theory", it has not been tested by me...
rizzo2dial
Premium
join:2004-08-05


2 edits
said by p2pvoice See Profile :

DracoFelis:

I have SPA1001 with two virtual lines. Line 1 is set up for "home" and Line 2 is set up for "business" with a different ringtone. Each line is an extension on my Asterisk server. So, by using a single phone, I can tell from the ringtone, whether an incoming call is a "home" call or a "business" call. I use primarily Line 1 for outgoing calls using Asterisk's outbound routing.

Here is the "trick: I need to implement:

My business number is an IPKall number, which "points" to my "business" extension on my Asterisk server.

My home number is "ported" to an ITSP and it "points" my "home" extension.

This ITSP is fully 911 compliant; however, I use this ITSP for incoming calls only (don't use this ITSP for outgoing calls). Since this ITSP is fully 911 compliant, I would like only the 911 call to go through this ITSP instead of the other ITSPs configured in my Asterisk's outbound routing.

Will this "trick" (inspired by your SIPPhone post) work?

911

I don't know where to put UN/PW?

BTW, my Asterisk server is registered to My911ITSP.com

Thanks
I have a need to do a similar thing; however, I don't have an Asterisk server involved. The setup I'm working with is as follows:

Equipment: PAP2 (running SPA1001 3.1.8 firmware)
LINE1: Outgoing VoIP line (from a provider w/o any 911/E911 support)
LINE2: Incoming VoIP line (from a provider w/ unlimited incoming, metered outgoing, but w/ true E911 support)

Normally calls are to go out on LINE1; however, for 911 calls, they MUST go out on LINE2. I've been playing around w/ this all day and have thus far come up w/ a tolerable (athough not ideal) solution. To describe the solution, I'll replace "911" with "555" (so that you can configure the solution and see how it works):

1) In the SPA1001's PHONE tab, configure the "Line 2 Select Code" to be "555" instead of "#"

2) In the LINE1 tab, add the following to the beginning of the Dialing Plan: "555S0|" (this will ensure that 555 gets detected immediately on the LINE1 side)

3) On the LINE2 tab, set the entire dialing plan to be a HOTLINE:
(S1 <:18005551212>)
The above will automatically dial 1-800-555-1212 after 1 second of LINE2 dial-tone. (Once you're ready to configure this "for real," replace "18005551212" with "911").

The "S1" condition above is why this solution is not fool proof. A true "HOTLINE" dialing plan starts with "S0" (for 0 second pause); however, when the adapter's default line (for dialing out) is LINE1, and when switching over to LINE2 (via "555" or "#" or whatever), the "S0" ZERO SECOND PAUSE doesn't get honored. I don't know why that is, but that's one flaw w/ this implementation.

Another flaw is that this implementation doesn't allow LINE2 to be used as a backup VoIP provider for other outgoing calls (unless you add more to the LINE2 dialing plan and can dial your other # within 1 second).

I'm hopeful a better solution can be reached; however, I haven't been successful in otherwise getting a LINE1 dialing plan instruction to dial out on LINE2.

Rizzo

DracoFelis
Premium
join:2003-06-15


1 edit

Re: [Equipment] Useful Sipura tricks...

said by rizzo2dial See Profile :

Another flaw is that this implementation doesn't allow LINE2 to be used as a backup VoIP provider for other outgoing calls (unless you add more to the LINE2 dialing plan and can dial your other # within 1 second).

I'm hopeful a better solution can be reached; however, I haven't been successful in otherwise getting a LINE1 dialing plan instruction to dial out on LINE2.
I know you can reach a better solution with an SPA-3000. Because with an SPA-3000, you just put your 911 provider on one of the 4 "gateway" slots, and then just tell your dial plan to use the "gateway" for 911 dialing.

Edit: If you do have an SPA-3000, check out a previous "trick" I posted in this (long) thread, on how to use the four SPA-3000 "gateway" slots to store (and use) the login credentials of additional outbound only VoIP providers!

But I don't know if there is a better solution for E911 on an SPA-1001. Your solution (for the SPA-1001) was IMHO very clever, and thanks for posting!

BTW:
Don't forget that if you are willing to give up E911, and do simple "speed dialing" (without the enhanced location info sent to your emergency center), you can replace a dialed 911 with a quick "speed dial" to whatever is a proper "emergency number" for your area, simply by playing with your "dial plan". And that "trick" (already posted in a previous message in this thread) works in most LinkSys/Sipura adapters, simply by modifying your "dial plan"!

For example, if you check with your local emergency services, and find that a local emergency number is "1-555-555-1234" (that is a bogus number, use a number appropriate for your area), you can add this little pattern to the front of your dial plan (again, modified to use your real "emergency number", not the bogus 1-555-555-1234) to trap for a user dialing 911, and instead "speed dial" your local emergency number:
<911:15555551234>S0

Edit:
Of course, the above "trick" assumes that you can acquire a real number to dial in the case of an emergency (and some areas only allow "911", without having a "real number" that also reaches the emergency center). And it also assumes that you have a VoIP provider on your adapter that lets you dial that number (i.e. for most VoIP companies, that number will probably dial as a normal "long distance call"). And even with the above limits, you still won't get the enhanced "location info" that "real 911" will give you (so you will have to let the person on the other end of the line know where you are located, when you talk to them).

But at least that (speed dial type 911) "trick" does let someone dial 911 on your phone, and reach real "emergency personal" appropriate for your area! And unlike the other "tricks", that approach does NOT require you to have a VoIP account that has "real 911" enabled on it (because you are essentially having the LinkSys/Sipura itself convert 911 into a normal long distance call to an appropriate pre-chosen "emergency number" of your choice)!
rizzo2dial
Premium
join:2004-08-05

Re: [Equipment] Useful Sipura tricks...

said by DracoFelis See Profile :

I know you can reach a better solution with an SPA-3000. Because with an SPA-3000, you just put your 911 provider on one of the 4 "gateway" slots, and then just tell your dial plan to use the "gateway" for 911 dialing.
I agree that an SPA-3000 would work perfectly.

said by DracoFelis See Profile :

Edit: If you do have an SPA-3000, check out a previous "trick" I posted in this (long) thread, on how to use the four SPA-3000 "gateway" slots to store (and use) the login credentials of additional outbound only VoIP providers!
For the situation I'm working w/ at the moment, an SPA-3000 is not available.

said by DracoFelis See Profile :

BTW:
Don't forget that if you are willing to give up E911, and do simple "speed dialing" (without the enhanced location info sent to your emergency center), you can replace a dialed 911 with a quick "speed dial" to whatever is a proper "emergency number" for your area, simply by playing with your "dial plan". And that "trick" (already posted in a previous message in this thread) works in most LinkSys/Sipura adapters, simply by modifying your "dial plan"!
Speaking of SPEED DIALING, the USER1 tab "Speed Dial [2-9]" entires actually support dialing out on the opposite line of the SPA-1001. For example, if the "Line 2 Select" key is left as the default value of "#" and a "SPEED DIAL x" entry on LINE1 gets configured as "#18005551212", it will dial "18005551212" on LINE2 (w/ a LINE2 dial-tone being heard for a split-second).

Unfortunately this same behavior doesn't occur when configuring it in a DIAL PLAN speed dial (as suggested in the quote below). It also doesn't work when convertijng a DIAL PLAN speed dial entry into a USER TAB speed dial entry:
<911:2#>S0
Converts DIAL PLAN speed dial "911" to USER TAB "Speed Dial 2." While dialing "2#" directly allows dialing out on LINE2 (if configured to do so), dialing "911" (where it gets converted to "2#") doesn't work.

said by DracoFelis See Profile :

For example, if you check with your local emergency services, and find that a local emergency number is "1-555-555-1234" (that is a bogus number, use a number appropriate for your area), you can add this little pattern to the front of your dial plan (again, modified to use your real "emergency number", not the bogus 1-555-555-1234) to trap for a user dialing 911, and instead "speed dial" your local emergency number:
<911:15555551234>S0
Since E911 is available on the VoIP provider on LINE2 (normally used for incoming calls only), the solution above is precisely one of the things trying to be avoided.

Rizzo
rizzo2dial
Premium
join:2004-08-05


2 edits

Re: [Equipment] Useful Sipura tricks...

said by rizzo2dial See Profile :

Speaking of SPEED DIALING, the USER1 tab "Speed Dial [2-9]" entires actually support dialing out on the opposite line of the SPA-1001. For example, if the "Line 2 Select" key is left as the default value of "#" and a "SPEED DIAL x" entry on LINE1 gets configured as "#18005551212", it will dial "18005551212" on LINE2 (w/ a LINE2 dial-tone being heard for a split-second).

Unfortunately this same behavior doesn't occur when configuring it in a DIAL PLAN speed dial (as suggested in the quote below). It also doesn't work when convertijng a DIAL PLAN speed dial entry into a USER TAB speed dial entry:
<911:2#>S0
Converts DIAL PLAN speed dial "911" to USER TAB "Speed Dial 2." While dialing "2#" directly allows dialing out on LINE2 (if configured to do so), dialing "911" (where it gets converted to "2#") doesn't work.
I just figured out how to get a DIAL PLAN speed dial entry (like the one above) to successfully dial a USER TAB speed dial entry! In the DIAL PLAN SPEED DIAL entry, don't end the USER TAB SPEED DIAL entry w/ a '#' (pound) symbol.

Here's how to configure LINE1 of the SPA-1001 to dial "911" on LINE2:

1) In the "Phone" tab, set the "Line 2 Select Code" to be the default value of "#"

2) In the "User 1" TAB, configure a "Speed Dial [2-9]" entry of your choice as "#911" (for dialing "911" on LINE2).

3) Assuming you configured entry "Speed Dial 2" in the previous step, insert into the beginning of the LINE1 Dialing plan the following:
<911:2>S0|
If you configured a different "Speed Dial [2-9]" entry, replace the ":2" above with ":x"
(where x is the configured "Speed Dial [2-9]" entry #).

When dialing 911, you'll hear a LINE2 dialtone for a split second followed by the true 911 call on LINE2.

Even if you dial any digits after 911 on LINE1 (i.e. 9111, 91111, 911111, etc.), they'll be ignored (which is precisely what you want for 911 purposes).

With this solution, you retain full LINE2 functionality should you want/need to manually dial out on that line.

Rizzo

DracoFelis
Premium
join:2003-06-15

Re: [Equipment] Useful Sipura tricks...

said by rizzo2dial See Profile :

Here's how to configure LINE1 of the SPA-1001 to dial "911" on LINE2:

1) In the "Phone" tab, set the "Line 2 Select Code" to be the default value of "#"

2) In the "User 1" TAB, configure a "Speed Dial [2-9]" entry of your choice as "#911" (for dialing "911" on LINE2).

3) Assuming you configured entry "Speed Dial 2" in the previous step, insert into the beginning of the LINE1 Dialing plan the following:
<911:2>S0|
If you configured a different "Speed Dial [2-9]" entry, replace the ":2" above with ":x"
(where x is the configured "Speed Dial [2-9]" entry #).
Hey, cool!

Your "trick" is a very clever way to easily add "line 2" dialing (including 911 dialing, where the VoIP provider with 911 is on "line 2") to an SPA-1001's "dial plan" on an SPA-1001.

But even more than that, your "trick" lets you use a "speed dial" slot wherever you want in a LinkSys/Sipura "dial plan" (instead of having to access the "speed dial" by the single digit corresponding to that speed dial slot)! I never knew you could use a "speed dial" slot like that!

And the really "cool" thing about your "trick", is that it is not just SPA-1001 specific. While it is true that only the SPA-1001 allows you to access "line 2" via a "speed dial", the "trick" of accessing a speed dial in your "dial plan" seems to work on other Sipura adapters as well. Specifically, when I put the following pattern into my dial plan of my Sipura SPA-3000 (to test accessing speed dials from the dial plan), I was correctly connected to the location of my "speed dial 2" when I dialed "12" on the phone:
<12:2>S0

Hmmm... Let's see...
This could end up being really handy, if I ever want to translate several different call numbers to the same target location, without having to change the dial plan each time I want to redirect them. Instead, I just point all those targets to a single "speed dial" slot, and update the "speed dial" if/when I want to point them all somewhere else. And this should also help keep down the length of my "dial plan" (by putting some of the logic in a "speed dial" or three), and Sipura dial plans do have a maximum number of characters they will accept. And...
rizzo2dial
Premium
join:2004-08-05

said by rizzo2dial See Profile :

Here's how to configure LINE1 of the SPA-1001 to dial "911" on LINE2:

1) In the "Phone" tab, set the "Line 2 Select Code" to be the default value of "#"

2) In the "User 1" TAB, configure a "Speed Dial [2-9]" entry of your choice as "#911" (for dialing "911" on LINE2).

3) Assuming you configured entry "Speed Dial 2" in the previous step, insert into the beginning of the LINE1 Dialing plan the following:
<911:2>S0|
If you configured a different "Speed Dial [2-9]" entry, replace the ":2" above with ":x"
(where x is the configured "Speed Dial [2-9]" entry #).

When dialing 911, you'll hear a LINE2 dialtone for a split second followed by the true 911 call on LINE2.

Even if you dial any digits after 911 on LINE1 (i.e. 9111, 91111, 911111, etc.), they'll be ignored (which is precisely what you want for 911 purposes).

With this solution, you retain full LINE2 functionality should you want/need to manually dial out on that line.

Rizzo
It dawned on me that w/ the solution above, if somebody were to inadvertently dial "2#" on their phone, it would connect them to 911. This could result in an unexpected/unwanted visit from the local police department.

Here's your choice of modified LINE1 dialing plans prefixes to continue to allow "911" to dial SPEED DIAL ENTRY #2 (in the USER1 tab) while preventing the directly dialed "2#" SPEED DIAL ENTRY from calling 911:

Option #1: Directly dialing "2#" results in a FAST BUSY SIGNAL
<911:2>S0|<2#:>S0|

Option #2: Directly dialing "2#" gives the LINE2 DIAL-TONE
<911:2>S0|<2#:#>S0|

Option #3: Directly dialing "2#" dials a phone number of your choice
<911:2>S0|<2#:xxxxxxxxxxx>S0|
Replace 'xxxxxxxxxxx' w/ the phone number of your choice.

Personally I like Option #2, although Option #3 lets you convert "2#" back into a psuedo-Speed Dial Entry for NON-911 purposes (while allowing the REAL Speed Dial Entry to call 911 on LINE2).

Rizzo
igi

join:2002-04-21
Oceanport, NJ

Hi DracoFelis,

Thanks a lot for your master tricks. I have a question about latency though in your Line 2/Line 1 forwarding: have you checked if this increases latency/delay when you call another FWD user?

I'm interested in using the same trick, but I wouldn't want to add more delay to what I already have, since some of my FWD calls are literally to the other side of the world. If the IP forwarding is done all internal inside the SPA, then I don't see why this would add delay, but with the external IP address trick, are you now opening another routing through the internet?

Thanks,

I.

DracoFelis
Premium
join:2003-06-15

Re: [Equipment] Useful Sipura tricks...

said by igi See Profile:

I have a question about latency though in your Line 2/Line 1 forwarding: have you checked if this increases latency/delay when you call another FWD user?
No, I have not checked. However, based upon some posts over on Voxilla.com (since the time I came up with that "trick"), it appears that Sipura adapters do NOT do forwarding "internally", but instead send a SIP "reinvite" message back to the calling SIP device. Essentially, the Sipura sends a message back to the original SIP provider, telling that provider to send the SIP traffic to an alternate destination.

As a result, the predicted behavior of my forwarding "trick" is this:

1) Since the Sipura essentially tells the sending provider to redirect the traffic, any provider that ignores such redirect messages will likely not work with this forwarding trick (and in fact, at least one person who tried my forwarding trick with a commercial VoIP provider appeared to fail for this reason). Thankfully FWD does pay attention to "reinvite" messages, so this trick can work with inbound FWD calls (which happens to be also what I originally tested it on).

2) Since the SIP messages aren't really "forwarded", but instead the original caller is told (by the SIP reinvite message) to try sending the call elsewhere, you shouldn't have any more "latency" then if the user had called that other port directly.

3) This also explains why you have to use the EXTERNAL (internet, NOT LAN) address of your Sipura, and why you have to forward the SIP ports on your router to your Sipura (for this trick to work). Simply put, it appears that the "SIP reinvite" message (that your Sipura gives out as a result of the "forward" setup) tells the remote SIP device how to call the other port of your Sipura directly "peer to peer".

4) If I'm correct in what is going on, that would also explain how to directly call a Sipura "peer to peer" without any "service provider" (even FWD) at all! Anyone with a Sipura want to help test this theory out? Can another user on the internet directly "ring our phone" by calling the same URI that we have in our "forwarding" trick? I bet the answer is "yes", but I would like to test this theory out first, before saying for sure that it will work!
gnexus

join:2005-06-24


1 edit

Re: [Equipment] Useful Sipura tricks...

said by DracoFelis See Profile:

4) If I'm correct in what is going on, that would also explain how to directly call a Sipura "peer to peer" without any "service provider" (even FWD) at all! Anyone with a Sipura want to help test this theory out? Can another user on the internet directly "ring our phone" by calling the same URI that we have in our "forwarding" trick? I bet the answer is "yes", but I would like to test this theory out first, before saying for sure that it will work!
Yes! You are correct Draco. It does work! (of course it does, SIP is P2P so it has to. . .unless there's a Sipura prob. with P2P) You beat me to the next "trick".
I was going to post it, but then I had problems:

I had it working after trying your trick! Now it doesn't however. . . The voice is audible inbound only and I'm trying to troubleshoot. That's why I'm back here at BBR. . .searching through old posts on NAT traversal.

You would think it's, and somehow it probably is, a NAT traversal problem. It is a strange one, however, because it was working before, and occasionally has since, after settings changes. Then it stops, however. I even tried setting the SPA as DMZ. That still only had it working for a single call. Due to that I'm starting to think that my SPA is screwed up because of that, and intermittent outbound dropouts (every 10s or so) on my regular VoIP provider (and all the other free VoIP services, too). I even tried resetting the SPA with no improvement. . .

Since it is likely a NAT traversal problem, I am (impatiently) awaiting the next DD-WRT beta. It has a SER built in which will eliminate NAT traversal problems and the use of the STUN gun.

Edit: Still no luck. . .One way audio, fleeting two way audio. I did find out something interesting in the SIP logs, however:
SIPphone server response:
Server: Sip EXpress router (0.8.12-tcp_nonb (i386/linux))
That means the SIPphone proxy server is using the same code as the SER being added to DD-WRT!

DKreil

@surfer.at

This is fantastic and exactly what I'd need!!

Is there any form of documentation of call plan syntax around or did you learn all that from the published examples & trial and error? I have paged through the Users' guide but it seems more like a list of features available for provisioning by VoIP providers.

I have tried to learn from your examples but I cannot get the call forwarding to work on my SPA-2100. I have tested the following forwarding destinations, but all without success (forwarding from line 1 to line 2):
- localhost & port
4832525@127.0.0.1:5061
- SIP account at provider (sipgate, Austria):
4832525@sipgate.at
- external IP & port
4832525@voice.kreil.net:5061
When I call the number from on my mobile, after a delay, I get "number error do you wish to retry", while when calling with a softphone (x-lite), the forward is simply ignored (!), and I get passed through to the account's voicemail after a while.

What else could I try?

Is it likely that it's a difference between the SPA2100 and the 3000? Is it worth going for the 3000 instead?
I opted for the 2100 because I could place it infront of my router, hence avoiding some QoS issues. If I got the 3000, I'd have to put it behind my router and I have no idea whether that supports QoS VoIP prioritization (it's an USR8054).

Lastly, I have tried to follow the discussion about using Gateway Accounts on the forum but am not quite sure of the latest: Is there now a way one can use Gateway Accounts or information in the calling plan to switch providers which
- require a password
- have a different user ID?
In my case, I need an account in the UK and one in Austria, currently using sipgate (sort of).

I'd be grateful for your thoughts!

In return, I'm afraid I don't have any tricks yet on the configuration side that I could share. I could only tell you about the joys of bridging different analogue phone cabling standards (different in all the countries my life has touched: US, UK, Germany, Austria) but I doubt you want to hear that

With many thanks again for your help
and best regards,

David.

DracoFelis
Premium
join:2003-06-15

Re: [Equipment] Useful Sipura tricks...

said by DKreil:

Is there any form of documentation of call plan syntax around or did you learn all that from the published examples & trial and error? I have paged through the Users' guide but it seems more like a list of features available for provisioning by VoIP providers.
The user guide leaves a lot to be desired, but it is still a good reference. For "dial plan" help, pay very careful attention to the "Appendix 1" (the last 3 or 4 pages of the PDF containing the user guide). Try to read them carefully, as the majority of the dial plan syntax is actually documented there! Beyond that, ask over on the Voxilla.com Sipura forum, as there are a LOT of knowledgeable people willing to help "the lost" with setting up a dial plan to do something specific.

NOTE: Many of my dial plan "tricks" came from simply reading the user manual, trying to really understand what it MEANS (instead of just glossing over it), and then simply "thinking outside the box" as to what I could make the Sipura do with that syntax. I then just "ran the experiment" to see if I could actually carry out what my hypothesis said I should be able to do (in most cases yes, but not all the time).

said by DKreil:

I have tried to learn from your examples but I cannot get the call forwarding to work on my SPA-2100.
As has been mentioned in this thread, I discovered AFTER first posting that "trick" that it doesn't work for all users or all VoIP providers. So YMMV with that forwarding trick. That said:

said by DKreil:

- localhost & port
4832525@127.0.0.1:5061
This may work for an INTERNAL call within your LAN. But it will NOT work for "forwarding".

Apparently, the Sipura forwarding works by telling the calling party to redirect their call elsewhere. Not only does this mean that the "elsewhere" has to be seeable from outside your LAN, but it also means that if your incoming VoIP provider refuses the "redirect", the call won't forward! Some VoIP providers will ALWAYS refuse the redirect, so "call forwarding" with a Sipura appears to be a YMMV thing.

said by DKreil:

- SIP account at provider (sipgate, Austria):
4832525@sipgate.at
This one should work if BOTH of the following are true:

1) Anyone off the net can call your phone by calling the SIP URI "4832525@sipgate.at", even if/when they don't have an account with "sipgate.at". If this isn't the case, the forwarding will fail, because you have just forwarded to a destination that doesn't accept the call.

and 2) The VoIP provider you are registered with on the line you are forwarding from supports the "SIP reinvite" (call redirect) message. If not, call forwarding will never work from that line, as the Sipura doesn't appear to actually do the forwarding (instead it tells the calling SIP party/device to call somewhere else, and not all SIP providers/devices will follow that redirect message)!

said by DKreil:

- external IP & port
4832525@voice.kreil.net:5061
The external IP and port seems to work only if all of the following are true:

1) That really is the line's userid, external IP, and port. Pay special attention to make sure that the (dynamic) DNS really points to your external IP.

2) Make sure you didn't forget to forward the SIP port (in your case UDP 5061) on your router to your Sipura. While you normally don't have to do "port forwarding" when you have a line "registered", in the case of direct IP calling (and this trick is essentially doing a call forward directly to the other side of your Sipura), you do need the port "forwarded" at your router, or the call likely won't ring!

3) You remembered to set "Ans Call Without Reg: yes" on the line receiving the forwarded call.

and finally 4) And even if/when you do all the above, it may still not work, because forwarding is still dependent upon the calling VoIP provider/device listening to the Sipura when it tells it to "go somewhere else". And some VoIP providers routinely ignore such "SIP reinvite" messages!

said by DKreil:

Is it likely that it's a difference between the SPA2100 and the 3000? Is it worth going for the 3000 instead?
"Forwarding" a VoIP call seems to be "hit or miss" with pretty much any Sipura (since the Sipura doesn't itself do the forwarding, and not all calling parties cooperate with the forwarding).

However, the SPA-3000 does give you some options that the other Sipura models don't. But those extra features may or may not help you, depending upon exactly what you are trying to accomplish.

IMHO here are the places the SPA-3000 seems to do better in:

1) The SPA-3000 makes it pretty easy to have one main inbound/outbound VoIP provider, and up to 4 additional "outbound call only" providers ON THE SAME PHONE. This gives you a lot of flexibility in setting up where the call goes when you call different numbers (whereas most of the Sipura models only have one VoIP provider per line, although many of the Sipuras have "2 lines", whereas the SPA-3000 really only has one). FWIW: This is the main reason I went with the SPA-3000. This feature alone, makes "mix and match" (such as having one VoIP provider for inbound calls, and another provider for outbound calls) many times easier than the other Sipura models!

2) The SPA-3000 has a "Line" jack, that lets you hook up a real phone line to the unit (and then also access that "phone line" from the phone hooked up to the Sipura). While I haven't yet experimented with this myself, many other people have apparently got this working. And this feature does allow the SPA-3000 to combine the best of VoIP with features of an existing "phone line", as if they were one combined service. And remember, the "phone line" could be a VoIP adapter from another company (to allow you to combine BYOD VoIP with some provider's "locked down service"), if so desired.

3) And if you are really into a painful setup, the true "power users" use the "Line" jack with the "VoIP to/from PSTN" "gateway" features of the SPA-3000. This allows the unique "hop on and hop off" tricks of the SPA-3000 (which I haven't even attempted to setup yet, btw). For example, how about calling your Sipura from work (or a cell phone), entering a "PIN code", and getting dial tone AS IF you made the call from home? With the proper SPA-3000 setup, you can do it! Likewise, with the proper SPA-3000 setup in another country, you can call VoIP to the other Sipura, enter a PIN code, and then dial out on their local phone line! Again, only the SPA-3000 (of the various Sipura models) is setup to do this sort of "hop on hop off" tricks, but the possibilities are VERY POWERFUL. Just keep in mind that those setups are also not trivial to get right (as some of the posts over in the Voxilla.com Sipura forum clearly indicate).

said by DKreil:

Lastly, I have tried to follow the discussion about using Gateway Accounts on the forum but am not quite sure of the latest: Is there now a way one can use Gateway Accounts or information in the calling plan to switch providers which
- require a password
- have a different user ID?
Yes. And that is one of the key features of the 4 "gateway" provider slots! But this is an SPA-3000 only feature, so it won't work on your SPA-2100.

To use the "gateway" slots, enter things like this:

"Gateway x: " gets "userid@sip_proxy" (i.e. your user account at your provider).

"GWx Auth ID: " gets your account "userid" (yes, I know it's silly to have it here AND in the "Gateway x" field, but that's how Sipura made it work...

"GWx NAT Mapping Enable: yes" (assuming you are behind NAT, which most of us are).

"GWx Password: " is your SIP password with that provider (obviously).

Once you have the above info entered into a gateway, it's then just a matter of setting up your "dial plan" to allow you to dial out via that gateway entry. For example, I have included the following pattern in my dial plan, to auto-route normal USA calls via my "gateway 1" provider (in my case DialPad.com):
1[2-9]xx[2-9]xxxxxxS0 <:@GW1> 
The important thing to remember with the "gateway" fields (besides the fact that they are an SPA-3000 only feature), is that it is a 2-part process. You have to setup the "gateway" fields correctly with your SIP/login info, AND you have to modify your "dial plan" so that your Sipura knows what calls to route via that alternate outbound VoIP provider!
kreil

join:2005-08-20
Austria

Re: [Equipment] Useful Sipura tricks...

Dear DracoFelis,

Thank you so much for your fast and friendly reply!

Some thoughts and further questions:

said by DracoFelis See Profile:

For "dial plan" help, pay very careful attention to the "Appendix 1" (the last 3 or 4 pages of the PDF containing the user guide).
Ah, thanks!!

said by DracoFelis See Profile:

said by DKreil:

- SIP account at provider (sipgate, Austria):
4832525@sipgate.at
This one should work if BOTH of the following are true:

1) Anyone off the net can call your phone by calling the SIP URI "4832525@sipgate.at", even if/when they don't have an account with "sipgate.at". If this isn't the case, the forwarding will fail, because you have just forwarded to a destination that doesn't accept the call.
Yes, this is my "external" SIP number, and anyone should be able to call it.

said by DracoFelis See Profile:

2) The VoIP provider you are registered with on the line you are forwarding from supports the "SIP reinvite" (call redirect) message. If not, call forwarding will never work from that line, as the Sipura doesn't appear to actually do the forwarding (instead it tells the calling SIP party/device to call somewhere else, and not all SIP providers/devices will follow that redirect message)!
Oh... I see. This might actually be the problem. I think sipgate used to have a forwarding feature on its website but removed it since. If they are thorough, they would also not reply to SIP reinvite messages
They do have voicemail though, so I wonder whether they do that via a SIP reinvite message or with a different internal method...

Do you know of anyone who got SIP reinvite working with sipgate lately? (In older threads, people just report using the sipgate config feature on the web that was then still available.)

Else, do you perhaps know anyone using a provider offering UK numbers and supporting SIP reinvite?

What I am basically looking for is placing and receiving calls on one phone to and from two different SIP provider accounts.

From what you say, I probably need to swap my SPA2100 for an SPA3000. While at the moment my setup is

Cablemodem
|
SPA2100 (w/NAT) -- phone
|
USR8054 router (w/NAT, again) and WiFi access point
|
PCs

this means

Cablemodem
|
USR8054 router (w/NAT) and WiFi access point
| |
| SPA3000
|
PCs

As the friendly folks from USR have not been able to reply to my repeated enqiries whether their device supports QoS/diffserve, I worry whether in this setup I will have voice over data prioritization. Do you have any experiences regarding this with your own setup/router?

Lastly, I noticed quite strong echo on my calls, despite leaving the default echo cancelling activated. Is there something I can do about this in my setup, or is this a provider issue, a VoIP technology issue, or more likely to come from the non-VoIP leg of the call?

Many thanks again for your kind help!

With best regards,

David.

jeanclaudenow

@sympatico.ca

telephone adapter

I am looking for an ANALOG "telephone adapter" which can permit me to bridge 2 telephones lines. This is adapter/device is suppose to be able to permit a remote user to access the 2nd telephone line from the 1st line. By example, if at my home I have 2 analog telephone lines, while I am out, I am supposed to be able to "dial in" the adapter from one line, and while I am remote, "dial out" using the second line.
Please advise me if you have this product available otherwise please refer me to a place which can provide me such an adapter.
Thanks.
JakesOnline

join:2005-08-05
Huntington Beach, CA

said by DracoFelis See Profile :

And now (drum roll), how to forward all inbound calls to the OTHER line:
This is VERY USEFUL, because it either lets you have a TWO VoIP accounts that both "ring" the same phone, OR lets you use one account for all incoming, and a 2nd account for all outgoing (by putting the "phone" on the line with the outgoing VoIP service, and then forwarding all incoming calls on that other VoIP line to that one)!
I tried to forward incoming FWD calls from line 2 to line 1 which I use for voxee outbound. The calls go directly to the FWD message center.

I tried forwarding to line1id@127.0.0.1:5060, line1@myDynDNSname.com:5060 and line1id@myinternetip:5060.

i'm pretty sure i followed every step.

ports are forwarded properly on the nat as well.

Any ideas?

DracoFelis
Premium
join:2003-06-15

Re: [Equipment] Useful Sipura tricks...

said by JakesOnline See Profile :

I tried forwarding to line1id@127.0.0.1:5060, line1@myDynDNSname.com:5060 and line1id@myinternetip:5060.

i'm pretty sure i followed every step.

ports are forwarded properly on the nat as well.

Any ideas?
Even though I posted that "trick", it appears to be a YMMV thing (works for some, and not for others).

The main trouble with "tricks" like this, is that they have multiple pieces that ALL have to work right to get the trick to work. Get even one minor piece out of place, and they don't work. And worse yet, finding what is wrong, can be a little like "finding a needle in the haystack".

In such a situation, about the best you can do, is try to split up the steps as much as possible, and see if you can get the individual pieces to work. You then "fix the pieces" as you find them, until you have all the individual parts working, and hopefully you can then put the pieces together to get everything to work. But you have a lot better chance of getting things working as desired, if you don't try "debugging the setup" all at once (but instead try to "bite off" smaller chunks, and get each of those smaller chunks working, before moving on).

For example, PM someone with a Sipura elsewhere on the internet (me if you like) the "line1id@myinternetip:5060" info you were using (along with a good time to call), and see if that person can call your Sipura line "peer to peer" (i.e. use that "line1id@myinternetip:5060" info to call your Sipura directly). If that works, you know that 1/2 of the setup needed for the "forwarding trick" (i.e. the ability of the line to "receive the call" from the other line) is working. But even if that "peer to peer call" doesn't work, at least you have narrowed down the problem area, and can then look to get that part of the setup working (before moving on to the other parts of that "trick").
venk25

join:2004-05-12
Nashua, NH
·VoicePulse

Jakes, DracoFelis has posted a possible cause for this problem earlier (on page 3 of this thread). I think it has to do with the Sipura sending a SIP forward/redirect URI (URI of your other line) back to the calling SIP server and the calling server not supporting it. If the caller is calling using a service that allows this (like FWD), the call should be forwarded to your other line.

I haven't tried it and so, haven't seen it work ! Am just saying based on a few of my SIP packet sniffing sessions
aup2

join:2003-06-05

Re: [Equipment] Useful Sipura tricks...

When using the Sipura (e.g., 2100) to do P2P calling without registering with a Proxy, does the unit use the settings for the particular line from which the call is made, even though the line is not registered? I am specifically interested in the preferred codec settings. If this is not the case, is there a way to force this?
Thanks.

DracoFelis
Premium
join:2003-06-15


1 edit

Re: [Equipment] Useful Sipura tricks...

said by aup2 See Profile :

When using the Sipura (e.g., 2100) to do P2P calling without registering with a Proxy, does the unit use the settings for the particular line from which the call is made, even though the line is not registered?
I don't have an SPA-2100, and the manual doesn't say. But in my limited experience/testing of this (on calls between my SPA-2000 and my SPA-3000), the answer appears to be "yes".

For example, even when calling an "unregistered" Sipura line, I still had to properly match the "userID@sipura_address:port" programmed into the target Sipura, in order for the call to go through. Likewise, when I forced a lower bandwidth CODEC on one adapter or another, I could hear the lower quality sound the resulted. So it at least appears that your "line settings" are paid attention to, even if/when you don't have the line "registered" with any VoIP provider. Among other things, this means that you should put in some credentials (including UserID), even if they are "bogus", and will only be used as part of controlling your P2P call setup...

NOTE: If you want to do some P2P VoIP call tests, PM me with your contact info, and a good time to call. If I'm not too busy at the time, I'll be happy to run a few call tests (against my SPA-3000), to see what happens.

NOTE: You appear to be able to get inbound calls BOTH from a "registered" VoIP provider (if you have one), AND an inbound P2P call on the same line (if you set things up properly). This little fact could possibly be useful, in some setups, as a way to let additional "virtual numbers" also ring the same VoIP "phone"!

amdrkenny

@ntl.com

The info on forwarding 1 line to another didn't work for me. I have a WRT54GS router, and I am running DD-WRT (12/16/05 v23 Beta 2 version) with SIPatH. I am able to ring both Line 1 and Line 2 from an outside line (mobile phone), if I don't have call forwarding. But if I try to forward the call as per the instructions, I just get a blank tone. I have tried using the IP of the router (both internal and external), the IP of the SPA2k, and 127.0.0.1.
Bollie Bolst

join:2005-12-21
@dracefelis

Forwarding is working, at least the other phone is ringing.. but I don't hear either myself talk or the other person.. What can be wrong..

I use the Sipura 2002
Lefteris9

join:2005-12-22
Greece

Re: [Equipment] Useful Sipura tricks...

Hi,

As we saw here thanks to DracoFelis, we can forward incoming calls from one line to the other, but how about forwarding outgoing calls?!?

I have a Linksys Pap2 and I'm trying to set up a dial plan which will allow me to place outgoing calls to both lines (Line1 configured to sipdiscount and Line2 configured to a Greek Voip provider).
What I'm basically trying to do is set up the dial plan so that if I dial #9 then the Phone number, the Phone is placed through Line2, while if I disal a number without #9 the Phone is dialed from Line1.

I understand that this is easy to set up in the Sipura 3000 because it supports gateways, but is it possible to add support for this to the Linksys pap2 (i.e. Sipura 2100)?

So far I was not able to do this, so I'm seeking for help....
t_rajan_m

join:2005-12-23
Rochester, NY
Thanks for the forwarding post. This is very useful. I just wanted to know whether this forwarding works in SPA 3000?
Forums » VOIP etc » Voice Over IP - VOIP » VOIP Tech Chat[General] PAP2 v2 and syslog »
« [VoiceStick] SIP Ports  


Wednesday, 25-Nov 12:36:23 Terms of Use | Privacy Policy | Hosting by www.nac.net - DSL,Hosting & Co-lo | feedback | contact
over 10 years online! © 1999-2009 dslreports.com.
page compression OFF
Most commented news this week
· [104] New AT&T Ad Campaign Hits Back At Verizon
· [90] Apple Joins AT&T Verizon Snark Fest
· [85] New Bill Takes Aim At Higher Verizon ETFs
· [41] In-Flight Internet Headed For Bumpy Landing?
· [36] TiVo Sees Record Customer Losses
· [32] Senators Want ACTA Made Public
· [32] Time Warner Cable Fires Broadside At Broadcasters
· [30] Earthlink Suffers From Major E-mail Outage
· [30] AT&T Offers New Prepaid Wireless plans
· [28] Frontier Increases Modem Rental Fee
Most people now reading
· Windows 7 boot manager editing questions [Microsoft Help]
· Telemarketing Hell: Heather's back [Spam, Scam and Phishbusters]
· [Rant] The Weather Channel [Rants, Raves, and Praise]
· Climate Change Scandal Erupts After Email Hack. [Security]
· [Rant] Damn Sermons through my speakers! [Rants, Raves, and Praise]
· 3.x Feral Druid - Bear Tanking Guide [World of Warcraft]
· Mysterious $800 Cash Deposit? [General Questions]
· [WotLK] Account STATUS: Frozen [World of Warcraft]
· [Config] cisco asa 5505 with multiple outside IP addresses [Cisco]
· [ PvE] Items that will just not drop in your raid [World of Warcraft]