openser: P-Asserted-Identity Parsing

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Hi,

I'm playing around with RFC 3325 and P-Asserted-Identity
(PAI)
Header-Field. I found that openser 1.2.x doen't support PAI
parsing, so
that I don't have a fast way to access user and domain part
of PAI.

Is this planned for openser in the near future?

regards
helmut

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.5 (MingW32)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org


iD8DBQFHH17e4tZeNddg3dwRAuTZAJwLJ3KbZ12OkZIenfEZ/ASl9dDQ6wCe
OX3P
BwSeJXOF9EOej9HD6tDpa6A=
=3WRV
-----END PGP SIGNATURE-----

_______________________________________________
Users mailing list
Usersopenser.org
htt
p://openser.org/cgi-bin/mailman/listinfo/users

Hi!

You could copy the PAI body into an AVP and then use pseudo
variable 
transformations to parse the URI.

uups - i just found that there is already a PV:
ht
tp://www.openser.org/dokuwiki/doku.php/pseudovariables:1.2.x
#uri_in_sip_request_s_p-asserted-identity_header

But I do not know if this works with multiple PAI headers
too.

regards
klaus

Helmut Kuper schrieb:
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
> 
> Hi,
> 
> I'm playing around with RFC 3325 and
P-Asserted-Identity (PAI)
> Header-Field. I found that openser 1.2.x doen't support
PAI parsing, so
> that I don't have a fast way to access user and domain
part of PAI.
> 
> Is this planned for openser in the near future?
> 
> regards
> helmut
> 
> -----BEGIN PGP SIGNATURE-----
> Version: GnuPG v1.4.5 (MingW32)
> Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

> 
>
iD8DBQFHH17e4tZeNddg3dwRAuTZAJwLJ3KbZ12OkZIenfEZ/ASl9dDQ6wCe
OX3P
> BwSeJXOF9EOej9HD6tDpa6A=
> =3WRV
> -----END PGP SIGNATURE-----
> 
> _______________________________________________
> Users mailing list
> Usersopenser.org
> htt
p://openser.org/cgi-bin/mailman/listinfo/users

_______________________________________________
Users mailing list
Usersopenser.org
htt
p://openser.org/cgi-bin/mailman/listinfo/users

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Hi,

thx 4 ur answere. I found that $ai PV already. I guess AVP
trans. is not
as food as extending _xl_table resp. items.c and parse_pai
files.


Maybe anyone did that already?

regards
helmut




Klaus Darilion schrieb:
> Hi!
> 
> You could copy the PAI body into an AVP and then use
pseudo variable
> transformations to parse the URI.
> 
> uups - i just found that there is already a PV:
> ht
tp://www.openser.org/dokuwiki/doku.php/pseudovariables:1.2.x
#uri_in_sip_request_s_p-asserted-identity_header
> 
> 
> But I do not know if this works with multiple PAI
headers too.
> 
> regards
> klaus
> 
> Helmut Kuper schrieb:
> Hi,
> 
> I'm playing around with RFC 3325 and
P-Asserted-Identity (PAI)
> Header-Field. I found that openser 1.2.x doen't support
PAI parsing, so
> that I don't have a fast way to access user and domain
part of PAI.
> 
> Is this planned for openser in the near future?
> 
> regards
> helmut
> 
>>
_______________________________________________
Users mailing list
Usersopenser.org
htt
p://openser.org/cgi-bin/mailman/listinfo/users

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.5 (MingW32)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org


iD8DBQFHH2dX4tZeNddg3dwRAkVxAJ0bg+5f5j3SB4JLiNXeSlKaZ5LMlgCf
Zezx
nCLovbVm7KiyfFajYZTBzks=
=t2j2
-----END PGP SIGNATURE-----

_______________________________________________
Users mailing list
Usersopenser.org
htt
p://openser.org/cgi-bin/mailman/listinfo/users

Helmut Kuper writes:

 > Is this planned for openser in the near future?

check out trunk (= 1.3).  if i remember correctly, i added
p-a-i parsing
to it.

-- juha

_______________________________________________
Users mailing list
Usersopenser.org
htt
p://openser.org/cgi-bin/mailman/listinfo/users