Hmm, my biggest fear is of course selling these to the end user who buys their own UA.. If that happens we can't do much about disabling on the client side. For now I just put in the same as you. Did you just do an if method == NOTIFY? Or did you catch that and also search for the keepalive? Since we won't be using MWI or anything I just did on method notify..
Matt
-----Original Message----- From: Klaus Darilion [mailto:klaus.mailinglists@pernau.at] Sent: Monday, January 10, 2005 4:24 PM To: Matt Schulte Cc: serusers@lists.iptel.org Subject: Re: [Serusers] Sipura NOTIFY
I catch them and answer with "200 OK". Better solution: turn this feature of in the SIPURA devices - from my experiences, keep alive with CRLF also works and does not create so much traffic.
regards, klaus
Matt Schulte wrote:
It seems Sipura's use NOTIFY for their keepalives, since the user in question is registered, I was wondering what others have done out there to ack these messages? It's of course easiest to ignore these but I wanted an alternative. :-)
Matt
Serusers mailing list serusers@lists.iptel.org http://lists.iptel.org/mailman/listinfo/serusers
I'm also looking on the Event: header (not sure - i think it was keepalive)
regards, klaus
Matt Schulte wrote:
Hmm, my biggest fear is of course selling these to the end user who buys their own UA.. If that happens we can't do much about disabling on the client side. For now I just put in the same as you. Did you just do an if method == NOTIFY? Or did you catch that and also search for the keepalive? Since we won't be using MWI or anything I just did on method notify..
Matt
-----Original Message----- From: Klaus Darilion [mailto:klaus.mailinglists@pernau.at] Sent: Monday, January 10, 2005 4:24 PM To: Matt Schulte Cc: serusers@lists.iptel.org Subject: Re: [Serusers] Sipura NOTIFY
I catch them and answer with "200 OK". Better solution: turn this feature of in the SIPURA devices - from my experiences, keep alive with CRLF also works and does not create so much traffic.
regards, klaus
Matt Schulte wrote:
It seems Sipura's use NOTIFY for their keepalives, since the user in question is registered, I was wondering what others have done out there to ack these messages? It's of course easiest to ignore these but I wanted an alternative. :-)
Matt
Serusers mailing list serusers@lists.iptel.org http://lists.iptel.org/mailman/listinfo/serusers
Hi,
You better leave it blank. This will not affect anything. Otherwise, you will always receive 404.
Thomas
On Wed, 2005-01-12 at 07:27, Klaus Darilion wrote:
I'm also looking on the Event: header (not sure - i think it was keepalive)
regards, klaus
Matt Schulte wrote:
Hmm, my biggest fear is of course selling these to the end user who buys their own UA.. If that happens we can't do much about disabling on the client side. For now I just put in the same as you. Did you just do an if method == NOTIFY? Or did you catch that and also search for the keepalive? Since we won't be using MWI or anything I just did on method notify..
Matt
-----Original Message----- From: Klaus Darilion [mailto:klaus.mailinglists@pernau.at] Sent: Monday, January 10, 2005 4:24 PM To: Matt Schulte Cc: serusers@lists.iptel.org Subject: Re: [Serusers] Sipura NOTIFY
I catch them and answer with "200 OK". Better solution: turn this feature of in the SIPURA devices - from my experiences, keep alive with CRLF also works and does not create so much traffic.
regards, klaus
Matt Schulte wrote:
It seems Sipura's use NOTIFY for their keepalives, since the user in question is registered, I was wondering what others have done out there to ack these messages? It's of course easiest to ignore these but I wanted an alternative. :-)
Matt
Serusers mailing list serusers@lists.iptel.org http://lists.iptel.org/mailman/listinfo/serusers
Serusers mailing list serusers@lists.iptel.org http://lists.iptel.org/mailman/listinfo/serusers
Better leave what blank? What do you mean - I can't follow.
regards, klaus
Thomas wrote:
Hi,
You better leave it blank. This will not affect anything. Otherwise, you will always receive 404.
Thomas
On Wed, 2005-01-12 at 07:27, Klaus Darilion wrote:
I'm also looking on the Event: header (not sure - i think it was keepalive)
regards, klaus
Matt Schulte wrote:
Hmm, my biggest fear is of course selling these to the end user who buys their own UA.. If that happens we can't do much about disabling on the client side. For now I just put in the same as you. Did you just do an if method == NOTIFY? Or did you catch that and also search for the keepalive? Since we won't be using MWI or anything I just did on method notify..
Matt
-----Original Message----- From: Klaus Darilion [mailto:klaus.mailinglists@pernau.at] Sent: Monday, January 10, 2005 4:24 PM To: Matt Schulte Cc: serusers@lists.iptel.org Subject: Re: [Serusers] Sipura NOTIFY
I catch them and answer with "200 OK". Better solution: turn this feature of in the SIPURA devices - from my experiences, keep alive with CRLF also works and does not create so much traffic.
regards, klaus
Matt Schulte wrote:
It seems Sipura's use NOTIFY for their keepalives, since the user in question is registered, I was wondering what others have done out there to ack these messages? It's of course easiest to ignore these but I wanted an alternative. :-)
Matt
Serusers mailing list serusers@lists.iptel.org http://lists.iptel.org/mailman/listinfo/serusers
Serusers mailing list serusers@lists.iptel.org http://lists.iptel.org/mailman/listinfo/serusers
-
Klaus Darilion -
Matt Schulte -
Thomas