| |
| 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 |
Mapping SPA942 Extensions to SPA9000 LinesTechnical support, how-to guides, troubleshooting, and general assistance for the Linksys Voice System (LVS) family of products. |
| | LinkBack | Thread Tools | Rate Thread | Display Modes |
| |||
| Hello all- I went with Race for our company's VoIP provider. My current setup on the SPA9000 is as follows: Line 1: Race Account 1 Line 2: Race Account 2 Line 3: <empty> Line 4: SPA400 All of the above lines are registering fine without any problems. The problem I'm having now is how to set up these 3 lines on a SPA942. Here is what I would like ideally: Extension 1: Race Account 1 Extension 2: Race Account 2 Extension 3: <disabled> Extension 4: Local Calls (SPA400) I tried to set this up, but no matter what extension I pick from the phone, it is always using Race Account 1. I'm not sure if this is a proxy problem or if I have the lines setup wrong on the phone... Currently, the extensions are setup with a proxy address of the SPA9000 on port 6060. Then I have the display name, user id and password setup in there. I also have the SIP ports matching to those on the SPA9000. Is there a different step I need to do so that when I press extension 2 or 4 on my phone for it to use the different line on the SPA9000? Also, I would like voicemail to work with just the SPA400 on all these lines. I should just be able to put the VM server address for the SPA400 in each of the extension tabs, right? And finally, any suggestions on how I should setup outbound callings? For instance, should I set it up so that if Race 1 is busy, the extension on the phone shows it is busy (so others know), or is there a way for it to automatically go to the next available line? Thanks in advance for your help! Pat Edit - I would like to do this without putting the specific account information into each extension tab. I want to use the SPA9000 as a proxy for this. This way, I can limit my firewall port openings. Edit - Gopt the voicemail to work properly. Currently trying to configure the phones so that if I dial *9 it will route to Line 4. I think my dialing plan is ok (*9911S0)|(*9xxxx.), but i'm not sure about my routing rule. I have (<*9:L4>xxxx.)|(<:L1,2,3>xxxx.) I can dial normal and it works (going to Lines 1-3) but when I do *9, I get a fast busy signal. Any thoughts? Last edited by khumprp : April 25th, 2008 at 07:26 PM. |
| |||
| As a general rule, stay away from using similar prefixes than the one used internally. The SPA line uses * + 2 digit codes for features ... e.g. *93 for deactivating cfwd no answer. So, this conflicts with your desired trunk selection prefix. I'm using ** + x for trunk selection in my setup.. this doesn't conflict with the PBX that also uses * codes for certain features. I used to be using # as trunk seizure prefix. For the nitty gritty on setting up trunk seizure prefixes,try a search in this subforum and limit your search to posts by me.. you'll find a detailed explanation on how to set it up. And just off the top of my head: <*9:L4>xxxx. Will not work. The call routing rules don't allow for replacement patterns... every entry has to start with <: ... you can only have something on the right hand side of the double point. So, you need to strip away the trunk seizure prefix in the line dialplan.
__________________ There are two essential pieces to tracking down a problem with your VoIP equipment:
|
| |||
| Thank, Humba. I'll setup my system so that no prefix is needed for the standard SIP, and ** will be used for the SPA400 on Line 4. I can strip away the **9 no problem in the dialplan, but then how does it know to route to line 4? do I put that in the dialplan like (<**9:>xxxxxxxS0).... I guess I'm not clear on mapping back to a separate line. I'll take a look at your older posts and see what I can find. Thanks again! Pat |
| Thread Tools | |
| Display Modes | Rate This Thread |
| |
| | ||||
| Thread | Thread Starter | Forum | Replies | Last Post |
| Shared lines appearance - SPA942 | biknit | Linksys SPA9000/SPA400 Support Forum | 18 | July 4th, 2008 08:17 PM |
| How to make Spa942 to fwd all 4 lines to cell through line1? | jarodcn | Linksys (Sipura) VoIP Support Forum | 1 | November 22nd, 2007 08:47 PM |
| Routing SPA400 PSTN lines to different extensions | sfice | Linksys SPA9000/SPA400 Support Forum | 2 | July 5th, 2007 08:53 AM |
| SPA942 Voicemail Forwarding (w/shared extensions) | mew20 | Linksys SPA9000/SPA400 Support Forum | 16 | February 12th, 2007 12:51 PM |
| SPA942 Shared Lines | graydian | Linksys SPA9000/SPA400 Support Forum | 1 | December 30th, 2006 01:22 AM |