[mew20]

Hey guys; New to this tech area and have a question / comments. Wondering if someone can confirm my findings and answer some of my quandaries.. THANK YOU in advance..

Equip: spa9000v1 / spa400 / spa942 - all at latest firmware levels.

Voice-mail for single non-shared extensions works fine. All equipment exhibiting no SIP registration issues. Incoming call routing and (so far) all else appears to be working. I still have a couple steps to go, but, that's for another day..

Trying to figure out how to set up the shared call appearance / Shared Ext functionality so the I can have two or more spa942 phones sharing an extension AND forwarding calls to voicemail upon no answer or line busy..

I notice on the spa942 that the User Tab (web interface) contains dedicated settings for Ext 1. This appears to mean that there is no User Tab functionality for Ext 2-4. This also (appears) to mean that no calls to Ext 2-4 can be redirected to voicemail on the 942. I guess this could make sense if you make the assumption that the owner of the phone and the associated voicemail box is usually Ext 1. It would be great if I was wrong about this..

Here's what's happening (simplified for clarity). Maybe this is just the characteristic of the spa phone system - not sure..

Phone A
Line 1 / Ext 100

Phone B
Line 1 / Ext 101
Line 2 / Ext 100

1 - if the EXT 1 extension number (100) is NOT shared with any other phone the Voicemail forward works.

2 - if the Ext 1 extension (100) number IS shared, the Voicemail forward does NOT work. Phone A (with the VM forward programmed in) rings for 20 seconds (default) then stops ringing. However, no voicemail forward happens and line 2 / Ext 100 of phone B keeps ringing until it times out (not to sure where this is set) and drops the call - sometimes with a busy signal.

My question is; Can I configure the system so that Ext 100 is shared by phone A / phone B AND have the voice-mail forward function correctly??

Thank you so much..

-Michael

[humba3]

I've done a little experiment a few days ago with shared lines and mailboxes. I have one system-wide shared line, which has a mailbox. It is line 2 on all multi-line phones. So as you pointed out, there's no way to set the forward via web interface. However, I programmed a special DP with a <92:vm>S0 element.. that means calling 92 will call the VM drop-off. While this is useless to call the voicemail (I have another substition for that too: <91:vmm>S0 - vmm is the vm pickup extension), it is very useful to redirect extensions to voicemail from the phone. To redirect any phone (not only the SPA92x/94x series), you are SOL. But with that DP element, suddenly you can program a callforward (via *xx code), then forward to extension 92, which is internally translated to the vm dropoff number.. and voila, you have your phone redirected to voicemail.
Now with a multline phone, you first have to select the line you want to redirect by pressing the appropriate line button (in my case line 2), then press the callforward button, then typing 92.. and now the second extension is forwarded to voicemail. Then, calling the shared extension from any phone will return in the call being forwarded to voicemail immediately.

What I have not tried is forwarding extension 80 of multiple phones concurrently, or a delayed forward.. I only tried with an immediate forward and the "do not disturb" functionality (which by the way is rather stupid that this forwards to voicemail.. DND should return a prompt " the caller at extension X does not wish to be disturbed" and not forward the call to voicemail).

If I can't get something to work, I usually turn on traces to see what is going on.. I suggest you try that too if you can't make any progress.. see what the SPA9000 does with the call to Line 1 on Phone A.. it may effectively be a software issue as the SPA9000 imho should drop INVITE except the one that has been answered.. and if an INVITE is redirected (be it to voicemail or another extension) and is then answered, the same thing should imho happen.
Also, ensure that you force the media proxy and voicemail proxy on the SPA9000.. the SPA9000 does very weird things when forwarding calls to voicemail.. it's not the same at all as forwarding a call to another system extension (and nobody can give me a reason why it's done like that). That may be something for you to test out in fact... program a cfwdnoanswer on phone A and point it to another extension (I hope you have a third phone.. if not, try a softphone like phonerlite).. then see if that third extension rings after the no answer timeout, and check what happens if the call is answered on the third extension. If that does work, it's a clear indication that the problem stems from the weird way Linksys handles forwards to voicemail.

[mew20]

Thank you so much for the detailed reply. I'll give the dial plan modifications a try..

BTW: Regarding the spa9000/spa400 regsitration issues etc... i've made the following changes..

Spa9K Line page linked to the spa400
Register Expires: 30
Mailbox Subscribe Expires: 30
VMSP Bridge: All+Self

Spa9K SIP page
Set Forced Media Proxy: Y

[mew20]

<<(I have another substition for that too: <91:vmm>S0 - vmm is the vm pickup extension), it is very useful to redirect extensions to voicemail from the phone).>>

BTW: I forgot to mention - regarding the vmm forward by extension.... If i configure the Ext 2 setting with the normal vmm parameters (Ext 2 Page: Mailbox ID: 1101 <spa configured line><Ext #> / Voice Mail Server: <spa9K IP:6060> - for message notification) for the shared extension, i can pick up voice-mail messages normally by pressing the Line-2 button then pressing the envelope button on the phone. If i'm understanding you correctly, this should negate the need for the <91:vmm>S0 dial plan element... Since vmm is a “keyed Linksys” option, I’m guessing this will only work on Linksys phones..

Just a thought.... Thanks again..

[humba3]

Yeah, the 91 extension isn't really needed for SPA9[2,4]x phones.. but I created it in the hope to give voicemail access to my FXS ports (it's not working as expected though, since the SPA9000 forgets to send the mailbox ID in the INVITE.. I've yet to check if they fixed that in the 5.x firmware).
Where did you get

Since vmm is a “keyed Linksys” option

from? It is actually true, it's a special extension that cannot be dialled from non SPA9xx phones but where did you see that mentioned?.. the SPA9000 completely messes up such URI dialling from non SPA phones.. it tries to put the URI through the numerical dialplan, fails and aborts the call, resulting in non SPA9xx phones not being able to use voicemail.

[mew20]

Regarding the FXS ports: NICE... This product line needs lots or retrofitting. Hoping in time some of this stuff will get addressed.. Guess it depends on pressure from the public.

Regarding the term "Keyed Linksys" option: I pulled that from the name of a firmware option that must be turned on for any of the proprietary vmm (etc..) functionality to work.

On the 942 / SIP Tab / Bottom of page (Firmware: 5.1.5)

Linksys Key System: Yes

[Silent_Dog]

I am wondering if any of you have worked a way out to deposit voicemail for SLA? In fact, ",cfwd=vm????" + "Cfwd No Ans" has always worked for SLA. I need the voicemail to work with SLA in conjunction with aa.

How do you do the trace? I have looked through all settings for SPA9000 and SPA742 to no avail.

[Silent_Dog]

Originally Posted by Silent_Dog

How do you do the trace? I have looked through all settings for SPA9000 and SPA742 to no avail.

Ok, worked this out. I need to set up a syslog server.

[amnet]

Hi mew20

Did you have any luck sorting this out?

I have a spa9000, spa400 and 6 users sharing 1 spa962. Only the first user on ext1 has unanswered call directed to voicemail. They other 5 users calls just ring for a while and are then drop

Cheers
Doug

[nickazphx]

Originally Posted by Silent_Dog

In fact, ",cfwd=vm????" + "Cfwd No Ans" has always worked for SLA.

I have tried various configurations of this with no luck. Can you share your working SLA/VM configuration?