By the way, is "voip.ikt-bs.de" configured as sip domain in sipx, or domain alias? (Registration "to domain alias" will work, but mwi subscription "to domain alias" will not). Nikolay.
_____ From: [email protected] [mailto:[email protected]] On Behalf Of David Becker Sent: Tuesday, October 19, 2010 3:51 PM To: [email protected] Subject: Re: [sipx-users] Help with SUBSCRIBE for MWI That is not under my control but both the phones and the server seem to attach the port number to their uris. REGISTER commands with the port number in the uri succeed. What does differ between the OpenStage's failed SUBSCRIBE and a Snom's successful one is that the OpenStage lists its contact address twice and includes the display name. Removing the display name makes it send the extension number instead. It could also be that it sends the credentials incorrectly in some way though it can register properly. Am 19.10.2010 10:06, schrieb Nikolay Kondratyev: David, i took a look at your trace. Openstage sends the following Authorization header Authorization: Digest username="200",realm="voip.ikt-bs.de",nonce="6c3df3c358dec988cc2725fea8844db f4ca5b588",uri="sip:[email protected]:5060;transport=udp" <mailto:sip:[email protected]:5060;transport=udp> ,response="c11b4111b4f8dfbb752983fbe3d9fe47",qop=auth,cnonce="3d31837c",nc=0 0000001 I suspect that a problem is that there is port number in the uri parameter. Here is the authorization header of a successfull subscribe (from x-lite): Authorization: Digest username="2800",realm="sip.nstel.ru",nonce="6a4ea57246bb60e653510ec7f321912f 4cbd4dc8",uri="sip:[email protected]" <mailto:sip:[email protected]> ,response="dfdc8d99337b807553260255832dd606",cnonce="568f0db0a071551d80a0f4d 3e3904cf1",nc=00000001,qop=auth,algorithm=MD5 So i think it's worth trying to get rid of a port number in the uri parameter in the authorization header. It may happen that if you just will not specify port 5060 in the openstage configuration it will work better... Rgds, Nikolay. _____ From: [email protected] [mailto:[email protected]] On Behalf Of David Becker Sent: Tuesday, October 19, 2010 11:18 AM To: Discussion list for users of sipXecs software Subject: Re: [sipx-users] Help with SUBSCRIBE for MWI Can I piggyback onto this thread? I've got the same problem with an OpenStage phone, the phone sends a SUBSCRIBE, gets an UNAUTHORIZED back and then sends another SUBSCRIBE with credentials attached which also get an UNAUTHORIZED response. I've attached a capture file of that transaction. If it's really about timing then I don't think I can do anything, the only setting regarding MWI the phone has is the server hostname. Am 19.10.2010 05:34, schrieb Tony Graziano: Actually, if the ATA subscribes to RLS it will get an unauthorized if it continues to try in too short of an interval. There are a lot of reasons it can get an “unauthorized” due to simple “punctuality” issues. You are not describing what it is trying to subscribe “to”, and could provide the log snippet as an example. The device could be subscribing to register thje line to the proxy, or to RLS for presence. It could simply be that it is trying too frequently on the MWI seting. Verify the setting on the device directly: Under Voice -> Regional MWI Dial Tone: 3...@-19,4...@-19;2(.1/.1/1+2);10(*/0/1+2) (default) VMWI Refresh Intvl: 30 (defaults to 0) Under Voice -> Line 1 MWI Serv: yes VMWI Serv: yes Under Voice -> User 1 Message Waiting: no (if yes, then message lamp is constantly flashing, message or not) And restart the device. From: [email protected] [mailto:[email protected]] On Behalf Of Jeff Gilmore Sent: Monday, October 18, 2010 9:18 PM To: Discussion list for users of sipXecs software Subject: Re: [sipx-users] Help with SUBSCRIBE for MWI The problem is, I need an ATA and not just SIP phones, because my customers are households with lots of existing analog phones and analog jacks wired to every room. I have not heard of any better brand of customer-premise-type ATA... In any case, my first challenge is in seeing why Sipx returns "Unauthorized" from a SUBSCRIBE. Shouldn't the reason appear in some log somewhere? If so, where? If I had a Polycom phone and it gave me a SUBSCRIBE error, where would you direct me to look to troubleshoot it? Jeff On Oct 18, 2010, at 1:33 PM, Todd Hodgen wrote: I have to agree. I ordered one once, it’s around here somewhere, in my junk pile. Maybe they work for some, but geez, what a lot of work for little or nothing. They are low cost, but the cost in your time to get them to the level of others is immense. From: [email protected] [mailto:[email protected]] On Behalf Of Michael Picher Sent: Monday, October 18, 2010 10:26 AM To: Discussion list for users of sipXecs software Subject: Re: [sipx-users] Help with SUBSCRIBE for MWI I run for cover from anything with model number starting with SPA... On Mon, Oct 18, 2010 at 1:19 PM, Jeff Gilmore <[email protected]> wrote: 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/ -- There are 10 kinds of people in this world, those who understand binary and those who don't. [email protected] blog: http://www.sipxecs.info call: sip:[email protected] <mailto:sip%[email protected]> _______________________________________________ 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/
