I have been noticing a lot of SUBSCRIBE messages in my logs and have cleaned up a lot by making changes to client configurations.
However, I notice a residual set of SUBSCRIBEs that are sent by the sipxRLS service to each extension that is enabled for voicemail (even ones with no phone attached). I traced one that went to one of my ATA devices, and it came back "501 not implemented". I can share a full trace if needed, but here is the contents of the initial message from sipxRLS: Time: 2011-10-27T19:44:29.767894Z Frame: 1 /tmp/trace.RVW22988/_.sipXproxy.trace.xml:10569477 /tmp/trace.RVW22988/_.sipxrls.trace.xml:2601809 Source: voip.zz.com-sipxrls Dest: choicevoip.ev.ithaca.ny.us-SipXProxy SUBSCRIBE sip:[email protected];sipx-noroute=VoiceMail;sipx-userforward=false SIP/2.0 From: <sip:[email protected]:41601>;tag=lYWuCf To: <sip:[email protected];sipx-noroute=VoiceMail;sipx-userforward=false> Call-Id: WDL0fEBADS9701 Cseq: 1 SUBSCRIBE Contact: <sip:192.168.88.2:41601;transport=udp> Event: dialog Accept: application/dialog-info+xml Expires: 2757 Date: Thu, 27 Oct 2011 19:44:29 GMT Max-Forwards: 20 User-Agent: sipXecs/4.4.0 sipXecs/rls (Linux) Accept-Language: en Via: SIP/2.0/UDP 192.168.88.2:41601;branch=z9hG4bK-XX-c76aUaWYHsKTUYpp4J6sU2cCyQ Content-Length: 0 I wonder what purpose these serve and if they are necessary? Thanks, Jeff _______________________________________________ sipx-users mailing list [email protected] List Archive: http://list.sipfoundry.org/archive/sipx-users/
