<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
<meta content="text/html;charset=ISO-8859-1" http-equiv="Content-Type">
</head>
<body bgcolor="#ffffff" text="#000000">
Olle E. Johansson wrote:
<blockquote cite="mid42DBA1A9.6080608@edvina.net" type="cite">
<pre wrap="">Kevin P. Fleming wrote:
</pre>
<blockquote type="cite">
<pre wrap="">Olle E. Johansson wrote:
</pre>
<blockquote type="cite">
<pre wrap="">I would say that the core problem is that we send NOTIFY messages
WITHOUT a preceeding SUBSCRIBE for notifications, so there's no
transaction to match. The NOTIFY has nothing to do with the actuall call
to voicemail, but should be related to a subscription... Well, it works
anyway with a lot of phones and ignoring it is ok and propably a correct
way of handling it.
</pre>
</blockquote>
<pre wrap="">
Agreed, although we will need to always continue to support the 'push'
method of MWI as well, since most phones do seem to support it properly.
</pre>
</blockquote>
<pre wrap=""><!---->
Agreed. Most of these phones do not subscribe anyway, so there would be
no way to notify them without breaking the standard. Think they also
missed this part of the RFCs :-)
What we need to do, and it's on my to-fix-list for chan_sip, is to make
sure that phones that actually do subscribe get NOTIFY messages with a
reference to the SUBSCRIBE (Call-ID) and that we expire the subscriptions.
/O
</pre>
</blockquote>
Thanks guys, I wrote a quick patch to prevent a tag from being attached
to a MWI NOTIFY that solved my problem in my specific case. <br>
<br>
-Chris<br>
</body>
</html>