yep, just a bunch of these: " "2009-01-08T01:15:34.914247Z":136271:INCOMING:INFO:ocny-sipx.oc.local:Si pClientTcp-16:B69FCB90:SipStatus:"Read SIP message: ----Remote Host:192.168.3.19---- Port: 44644---- SUBSCRIBE sip:[email protected] SIP/2.0 Record-Route: <sip:192.168.3.19:5060;lr> Via: SIP/2.0/TCP 192.168.3.19;branch=z9hG4bK-sipXecs-6e5e1434db4e263edd1230d4418c825a2fd7 Via: SIP/2.0/UDP 172.20.3.108;branch=z9hG4bK2d77aee4DE9BADF3 From: \"Milosz Meller\" <sip:[email protected]>;tag=BC0A382A-57F1F8F1 To: <sip:[email protected]> Cseq: 2 SUBSCRIBE Call-Id: [email protected] Contact: <sip:[email protected]> Allow: INVITE, ACK, BYE, CANCEL, OPTIONS, INFO, MESSAGE, SUBSCRIBE, NOTIFY, PRACK, UPDATE, REFER Event: message-summary User-Agent: PolycomSoundPointIP-SPIP_550-UA/3.1.1.0137 Accept-Language: en Accept: application/simple-message-summary Authorization: Digest username=\"6044\", realm=\"oc.local\", nonce=\"d6e57c2db02bf5bfda99e29336e5e774496553b6\", uri=\"sip:[email protected]\", response=\"d4eaab5cac75e07cb9f63a323d347fd4\", algorithm=MD5 Max-Forwards: 20 Expires: 3600 Content-Length: 0 Date: Thu, 08 Jan 2009 01:15:34 GMT X-Sipx-Spiral: true Route: <sip:192.168.3.19:5110;transport=tcp;lr>
====================END==================== " "2009-01-08T01:15:34.916154Z":136272:OUTGOING:INFO:ocny-sipx.oc.local:Su bscribeServerThread:B6CFFB90:SipStatus:"SipUserAgent::sendTcp TCP SIP User Agent sent message: ----Remote Host:192.168.3.19---- Port: 5060---- SIP/2.0 401 Unauthorized From: \"Milosz Meller\" <sip:[email protected]>;tag=BC0A382A-57F1F8F1 To: <sip:[email protected]> Call-Id: [email protected] Cseq: 2 SUBSCRIBE Via: SIP/2.0/TCP 192.168.3.19;branch=z9hG4bK-sipXecs-6e5e1434db4e263edd1230d4418c825a2fd7 Via: SIP/2.0/UDP 172.20.3.108;branch=z9hG4bK2d77aee4DE9BADF3 Www-Authenticate: Digest realm=\"oc.local\", nonce=\"d6e57c2db02bf5bfda99e29336e5e774496553b6\" User-Agent: sipXecs/3.10.3 sipXecs/publisher (Linux) Date: Thu, 08 Jan 2009 01:15:34 GMT Allow: INVITE, ACK, CANCEL, BYE, REFER, OPTIONS, NOTIFY, SUBSCRIBE Accept-Language: en Supported: sip-cc-01, timer Content-Length: 0 --------------------END-------------------- " -----Original Message----- From: Scott Lawrence [mailto:[email protected]] Sent: Thursday, January 08, 2009 9:38 AM To: Meller, Milosz Cc: [email protected] Subject: RE: [sipx-users] clearing false mwi? On Wed, 2009-01-07 at 20:56 -0500, Meller, Milosz wrote: > thanks for responding. > > no files in the mailstore. > > determined that mwi is broken on -all- phones. > > looked at a trace and the phones aren't being authorized after their > initial response to the auth challenge. including a sipXproxy.log > snip, if it's not helpful i'll do a full trace later. The place to look is the sipstatus.log - that's the component that's sending that challenge. _______________________________________________ sipx-users mailing list [email protected] List Archive: http://list.sipfoundry.org/archive/sipx-users Unsubscribe: http://list.sipfoundry.org/mailman/listinfo/sipx-users
