On Mon, 2009-11-09 at 12:39 -0500, Carolyn Beeton wrote: > In the traces attached to http://track.sipfoundry.org/browse/XX-6955, > the reported issue is that, in response to a > SUBSCRIBE(message-summary), the NOTIFY is being sent to the wrong > place. > > I see in sipXpublisher/src/statusserver/MwiPlugin.cpp a TODO in the > code to respond to a SUBSCRIBE with a NOTIFY only to the subscribing > phone (the failure to do this is what is shown in the second pcap in > the issue). I think the first pcap might be explained because > sipXpublisher/src/statusserver/Notifier.cpp sends a NOTIFY to all > unexpired subscriptions; but this SUBSCRIBE had Expires=0 and so > wouldn't qualify.
> Does anyone know why the status server does not use the standard > SipPublishContentMgr to publish content, and let the SubscribeServer > handle the NOTIFY responses? It doesn't use the new infrastructure because it long predates the creation of that infrastructure. > Does it make sense to try to fix the bug in MwiPlugin.cpp and > Notifier.cpp, or to switch them to use the SipPublishContentMgr? Your call. Why is the phone sending a SUBSCRIBE with Expires: 0 in the first place? It looks suspiciously like using SUBSCRIBE as a polling mechanism, which is not only not very timely but would create a very large load... _______________________________________________ sipx-dev mailing list [email protected] List Archive: http://list.sipfoundry.org/archive/sipx-dev Unsubscribe: http://list.sipfoundry.org/mailman/listinfo/sipx-dev sipXecs IP PBX -- http://www.sipfoundry.org/
