SOLVED!  There is nothing like giving up to make a solution appear.

After some more digging, I found that the field in the SPA configuration 
labeled "Voice Mail Server" does not want just a server name, but rather a 
"u...@server" string.  This can be done in the profile by entering the literal 
string "$u...@$proxy", which invokes the appropriate local macros on the SPA 
device.

Therefore, if we make the following changes to the profiles for the SPA2102, 
MWI seems to work:

1. Section: Control_Timer_Values__sec_, field VMWI Refresh Intvl set to 30
2. Section Line / Proxy and Registration, field Voice Mail Server set to 
$u...@$proxy
3. Section Line / Supplementary Service Settings field Message Waiting set to 
enabled

Unfortunately, the Voice Mail Server value does not seem to carry forward from 
the Sipx phone group settings to be the default for each phone instance (a 
bug?), so this value seems to require that it be set manually for each phone.  
The other values seem to default correctly from the phone group.

I'll test this some more and, if it holds, I'll enter a JIRA, and can update 
the SPA page in the Wiki.

Jeff

On Oct 19, 2010, at 3:22 PM, Jeff Gilmore wrote:

> Thanks for digging around Tony.  You always go above and beyond the call of 
> duty!
> 
> I don't see anything useful in the sipstatus log.  I see that my From tag is 
> identical, as Dale suggests, and it still doesn't work.  I'm ready to give up.
> 
> Jeff
> 
> 
> On Oct 19, 2010, at 9:45 AM, Tony Graziano wrote:
> 
>> I have looked thoroughly through a lot of other forums where this adapter is 
>> used with many different providers. It obviously doesn't play well with MWI 
>> at all.
>> 
>> I only surmise that the previous provider had a special configuration to 
>> support the nuance of this device.
>> 
>> After looking at the packets and logs (note: you still have not provided a 
>> proper siptrace) my conclusion is if you remove all the voicemail from an 
>> account, restart he device and it does not recognize MWI after leaving the 
>> account a VM, then like a lot of providers, simply suggest replacing the 
>> device.
>> 
>> MANY of the voip providers forums I have scoured suggested the same thing,
>> 
>> I don't know who added support for the device originally,  or whether it has 
>> ever worked properly, but it does seem plagued.
>> 
>> On Tue, Oct 19, 2010 at 9:23 AM, Jeff Gilmore <[email protected]> wrote:
>> Thanks for the helpful inputs.
>> 
>> Here is a ZIP containing a section of TCPDump from an initial registration 
>> and subscribe after a device restart, plus the sections of sipxProxy and 
>> SipRegistrar that match it.
>> 
>> 
>> 
>> 
>> Tony, I tried your suggestion to change the subscribe interval to something 
>> higher than zero, and that did not seem to help (other settings were already 
>> matched to your suggestion).
>> 
>> To clarify, I am trying to get the ATA device to detect when a user has new 
>> voicemail, so it can play a "stutter" dial tone when the user picks up their 
>> phone, indicating that messages are present.  This is the equivalent of the 
>> "message waiting" light on a desk phone.
>> 
>> I know this feature CAN work, because I have had residential SIP service 
>> from other vendors using these SPA ATA devices, where the feature worked.
>> 
>> Jeff
>> 
>> 
>> On Oct 19, 2010, at 4:15 AM, Nikolay Kondratyev wrote:
>> 
>> > Jeff,
>> > At least message trace is needed to try to help you.
>> > Either post siptrace xml file
>> > (http://wiki.sipfoundry.org/display/xecsuserV4r2/Display+SIP+message+flow+us
>> > ing+Sipviewer) or tcpdump capture.
>> > In both cases filter a trace by callid.
>> > Rgds,
>> > Nikolay.
>> >
>> >> -----Original Message-----
>> >> From: [email protected]
>> >> [mailto:[email protected]] On Behalf Of
>> >> Jeff Gilmore
>> >> Sent: Monday, October 18, 2010 9:20 PM
>> >> To: Discussion list for users of sipXecs software
>> >> Subject: Re: [sipx-users] Help with SUBSCRIBE for MWI
>> >>
>> >> No takers yet, eh?  Bummer.
>> >>
>> >> Can anyone at least tell me which log would show the results
>> >> of subscription requests.  I see them in the sipxproxy log,
>> >> but they never appear in sipxregistrar.   Where would they go
>> >> after the proxy see them?
>> >>
>> >> Thanks!
>> >>
>> >> Jeff
>> >> On Oct 18, 2010, at 10:37 AM, Jeff Gilmore wrote:
>> >>
>> >>> I have been trying for some time to get MWI (message
>> >> waiting indicator) working for my Linksys SPA2102 ATA
>> >> devices.  The units register successfully, then send send out
>> >> what look like valid SUBSCRIBE requests to sipx, but these
>> >> always come back 401 Unauthorized.
>> >>>
>> >>> I have a set of packet captures of the registration and
>> >> subscription, with matching sipproxy and sip registrar logs.
>> >>>
>> >>> Would anyone be willing to take a look at these and see if
>> >> you can spot what might be going wrong? If so, I'll send the
>> >> ZIP file privately to you.
>> >>>
>> >>> Thanks,
>> >>>
>> >>> Jeff
>> >>> _______________________________________________
>> >>> sipx-users mailing list
>> >>> [email protected]
>> >>> List Archive: http://list.sipfoundry.org/archive/sipx-users/
>> >>
>> >> _______________________________________________
>> >> sipx-users mailing list
>> >> [email protected]
>> >> List Archive: http://list.sipfoundry.org/archive/sipx-users/
>> >
>> > _______________________________________________
>> > sipx-users mailing list
>> > [email protected]
>> > List Archive: http://list.sipfoundry.org/archive/sipx-users/
>> 
>> 
>> _______________________________________________
>> sipx-users mailing list
>> [email protected]
>> List Archive: http://list.sipfoundry.org/archive/sipx-users/
>> 
>> 
>> 
>> -- 
>> ======================
>> Tony Graziano, Manager
>> Telephone: 434.984.8430
>> sip: [email protected]
>> Fax: 434.326.5325
>> 
>> Email: [email protected]
>> 
>> LAN/Telephony/Security and Control Systems Helpdesk:
>> Telephone: 434.984.8426
>> sip: [email protected]
>> 
>> Helpdesk Contract Customers:
>> http://support.myitdepartment.net
>> 
>> _______________________________________________
>> sipx-users mailing list
>> [email protected]
>> List Archive: http://list.sipfoundry.org/archive/sipx-users/
> 
> _______________________________________________
> sipx-users mailing list
> [email protected]
> List Archive: http://list.sipfoundry.org/archive/sipx-users/

_______________________________________________
sipx-users mailing list
[email protected]
List Archive: http://list.sipfoundry.org/archive/sipx-users/

Reply via email to