I;m not entirely sure, but consume_credentials might take care of this..
Heh, or just get rid of the grandstreams! ick! ;) -Brett
---------- Original Message ---------------------------------- From: Federico Giannici giannici@neomedia.it Date: Sat, 05 Nov 2005 16:50:29 +0100
I have found that some UAs (e.g Grandstream's ones) send the Proxy-Authorization header even in ACKs messages.
As we don't explicitly try to authenticate ACKs, we cannot use the consume_credentials() function. In fact, it seems that we have to call proxy_authorize() before we can use the consume_credentials(). But it's contrary to RFC to call proxy_authorize() for ACKs and CANCELs methods!
So, how can we prevent the Proxy-Authorization information to be forwarded to subsequent hops?
Thanks.
-- ___________________________________________________ __ |- giannici@neomedia.it |ederico Giannici http://www.neomedia.it ___________________________________________________
Serusers mailing list serusers@lists.iptel.org http://lists.iptel.org/mailman/listinfo/serusers
brett-ser-list wrote:
I;m not entirely sure, but consume_credentials might take care of this..
No, it deletes only "used" credentials.
Anyway, I solved simply removing the Proxy-Authorization header fileds with a simple replace() function from every ACK, CANCEL and BYE messages (they shouldn't have it, anyway).
Bye.
---------- Original Message ---------------------------------- From: Federico Giannici giannici@neomedia.it Date: Sat, 05 Nov 2005 16:50:29 +0100
I have found that some UAs (e.g Grandstream's ones) send the Proxy-Authorization header even in ACKs messages.
As we don't explicitly try to authenticate ACKs, we cannot use the consume_credentials() function. In fact, it seems that we have to call proxy_authorize() before we can use the consume_credentials(). But it's contrary to RFC to call proxy_authorize() for ACKs and CANCELs methods!
So, how can we prevent the Proxy-Authorization information to be forwarded to subsequent hops?
Thanks.
hi wouldn't it be simpler to use remove_hf("..");
-A
* Federico Giannici giannici@neomedia.it [051105 19:07]:
brett-ser-list wrote:
I;m not entirely sure, but consume_credentials might take care of this..
No, it deletes only "used" credentials.
Anyway, I solved simply removing the Proxy-Authorization header fileds with a simple replace() function from every ACK, CANCEL and BYE messages (they shouldn't have it, anyway).
Bye.
---------- Original Message ---------------------------------- From: Federico Giannici giannici@neomedia.it Date: Sat, 05 Nov 2005 16:50:29 +0100
I have found that some UAs (e.g Grandstream's ones) send the Proxy-Authorization header even in ACKs messages.
As we don't explicitly try to authenticate ACKs, we cannot use the consume_credentials() function. In fact, it seems that we have to call proxy_authorize() before we can use the consume_credentials(). But it's contrary to RFC to call proxy_authorize() for ACKs and CANCELs methods!
So, how can we prevent the Proxy-Authorization information to be forwarded to subsequent hops?
Thanks.
-- ___________________________________________________ __ |- giannici@neomedia.it |ederico Giannici http://www.neomedia.it ___________________________________________________
Serusers mailing list serusers@lists.iptel.org http://lists.iptel.org/mailman/listinfo/serusers
-
Atle Samuelsen -
brett-ser-list -
Federico Giannici