[OpenSIPS-Users] Dialog module and uac_auth

[Bogdan-Andrei Iancu]

Hi Brian,

The limitation is still true - even with the dialog support, the dialog 
can be monitored, but not changed - changing the CSEQ will affect the 
dialog for its whole lifetime , requiring opensips to constantly update 
the cseq in all sequential requests....this is more than the dialog 
module was designed for :)

Regards,
Bogdan

opensipslist at encambio.com wrote:
> Hello list,
>
> A while ago it was clear that uac_auth is of limited utility,
> due to the SIP RFC which requires that each message has a unique
> cseq. Calling uac_auth from failure_route produced a new INVITE
> with a proxy-auth header that didn't have a new cseq however.
>
> Since the dialog module appeared, I'm wondering how if scripts
> can be tweaked to use uac_auth in a SIP RFC compliant way.
>
> ...or is it still true that doing uac_auth() in failure_route fills
> in the proxy-auth header of a INVITE message that has already
> expired its cseq (no longer valid in the dialog)?
>
> How can uac_auth be used with INVITE messages in a SIP RFC compliant
> way?
>
> Regards,
> Brian
>
> _______________________________________________
> Users mailing list
> Users at lists.opensips.org
> http://lists.opensips.org/cgi-bin/mailman/listinfo/users
>
>   


-- 
Bogdan-Andrei Iancu
www.voice-system.ro