hi all, Please, what is the role of Remote-Party-ID header? thanks
ALAEDDINE abbech ha scritto:
hi all, Please, what is the role of Remote-Party-ID header? thanks
The remote-party-ID is the phone number of the calling party, you know, Caller-ID, there are other ways to implement it, but I don't remember them at the moment.
Users mailing list Users@lists.kamailio.org http://lists.kamailio.org/cgi-bin/mailman/listinfo/users
2008/10/31 Nick Warr techno@mobilia.it:
ALAEDDINE abbech ha scritto:
hi all, Please, what is the role of Remote-Party-ID header? thanks
The remote-party-ID is the phone number of the calling party, you know, Caller-ID, there are other ways to implement it, but I don't remember them at the moment.
RPID is an expired draft, but widely used since Cisco systems (and others) make use of it. But the today official estandar is P-Asserted-Identity (PAI) header.
- RPID draft: http://tools.ietf.org/html/draft-ietf-sip-privacy - PAI RFC: http://tools.ietf.org/html/rfc3325
Iñaki Baz Castillo writes:
But the today official estandar is P-Asserted-Identity (PAI) header.
- RPID draft: http://tools.ietf.org/html/draft-ietf-sip-privacy
- PAI RFC: http://tools.ietf.org/html/rfc3325
plus Privacy header, since pai alone cannot replace rpid.
-- juha
El Viernes, 31 de Octubre de 2008, Juha Heinanen escribió:
Iñaki Baz Castillo writes:
But the today official estandar is P-Asserted-Identity (PAI) header.
- RPID draft: http://tools.ietf.org/html/draft-ietf-sip-privacy
- PAI RFC: http://tools.ietf.org/html/rfc3325
plus Privacy header, since pai alone cannot replace rpid.
True, but Privacy header is also defined in RFC 3325 (and also P-Preferred-Identity).
Regards.
thanks, i will use the RFC 3325 but i don't know a soft phone supported this RFC. please if you know one give me its name ou a link to download it. Else, who know the NDI and the NDS , how can i implement this type of number with openser using RFC 3325
--- En date de : Sam 1.11.08, Iñaki Baz Castillo ibc@aliax.net a écrit : De: Iñaki Baz Castillo ibc@aliax.net Objet: Re: [Kamailio-Users] Remote-Party-ID header À: users@lists.kamailio.org Date: Samedi 1 Novembre 2008, 12h31
El Viernes, 31 de Octubre de 2008, Juha Heinanen escribió:
Iñaki Baz Castillo writes:
But the today official estandar is P-Asserted-Identity (PAI) header.
- RPID draft: http://tools.ietf.org/html/draft-ietf-sip-privacy
- PAI RFC: http://tools.ietf.org/html/rfc3325
plus Privacy header, since pai alone cannot replace rpid.
True, but Privacy header is also defined in RFC 3325 (and also P-Preferred-Identity).
Regards.
El Lunes, 3 de Noviembre de 2008, ALAEDDINE abbech escribió:
thanks, i will use the RFC 3325 but i don't know a soft phone supported this RFC.
You should read that RFC since it doesn't involve final phones but proxies and gateways.
please if you know one give me its name ou a link to download it.
The tipicall scenario is:
- A phone sends an INVITE. The "From" is "bob". - The proxy authenticates the INVITE. - Before forwarding the INVITE to the PSTN gateway, the proxy adds a P-Asserted-Identity header containing the asserted identity, that could be a PSTN number as callerID or any other username, examples: - P-Asserted-Identity: sip:+12345678@domain.org - P-Asserted-Identity: tel:+12345678 - P-Asserted-Identity: sip:bob.home@domain.org - When any other node in the network that trusts this proxy receives this INVITE from it, it trusts the PAI header and uses it as a callerid.
thanks, I readed the RFC 3325 before sending my mail, but now my problem is to implement this RFC with the use of NDI and the NDS. Who know how put the NDI and the NDS in the header P-Asserted-Identity and P-Preferred-Identity?
--- En date de : Lun 3.11.08, Iñaki Baz Castillo ibc@aliax.net a écrit : De: Iñaki Baz Castillo ibc@aliax.net Objet: Re: [Kamailio-Users] Remote-Party-ID header À: users@lists.kamailio.org Date: Lundi 3 Novembre 2008, 12h22
El Lunes, 3 de Noviembre de 2008, ALAEDDINE abbech escribió:
thanks, i will use the RFC 3325 but i don't know a soft phone supported this
RFC.
You should read that RFC since it doesn't involve final phones but proxies and gateways.
please if you know one give me its name ou a link to download it.
The tipicall scenario is:
- A phone sends an INVITE. The "From" is "bob". - The proxy authenticates the INVITE. - Before forwarding the INVITE to the PSTN gateway, the proxy adds a P-Asserted-Identity header containing the asserted identity, that could be a PSTN number as callerID or any other username, examples: - P-Asserted-Identity: sip:+12345678@domain.org - P-Asserted-Identity: tel:+12345678 - P-Asserted-Identity: sip:bob.home@domain.org - When any other node in the network that trusts this proxy receives this INVITE from it, it trusts the PAI header and uses it as a callerid.
El Lunes, 3 de Noviembre de 2008, ALAEDDINE abbech escribió:
thanks, I readed the RFC 3325 before sending my mail, but now my problem is to implement this RFC with the use of NDI and the NDS. Who know how put the NDI and the NDS in the header P-Asserted-Identity and P-Preferred-Identity?
Ok, what is NDI and NDS?
NDI:Numéro de Désignation d’Installation, is the number identifier the link with France telecom NDS:Numéro de Désignation Secondaire, is the number identifier the user agent.
--- En date de : Lun 3.11.08, Iñaki Baz Castillo ibc@aliax.net a écrit : De: Iñaki Baz Castillo ibc@aliax.net Objet: Re: [Kamailio-Users] Remote-Party-ID header À: users@lists.kamailio.org Date: Lundi 3 Novembre 2008, 14h45
El Lunes, 3 de Noviembre de 2008, ALAEDDINE abbech escribió:
thanks, I readed the RFC 3325 before sending my mail, but now my problem is to implement this RFC with the use of NDI and the NDS. Who know how put the NDI and the NDS in the header P-Asserted-Identity and
P-Preferred-Identity?
Ok, what is NDI and NDS?
El Lunes, 3 de Noviembre de 2008, ALAEDDINE abbech escribió:
NDI:Numéro de Désignation d’Installation, is the number identifier the link with France telecom NDS:Numéro de Désignation Secondaire, is the number identifier the user agent.
No idea of how to represent these fields intoa PAI header. The main question is: how does your PSTN gateways require this PAI header?
thanks all, But this is my major problem.i don't know the requirement of the PSTN gateways.I search if one between the users list do a direct connection with FRANCE TELECOM.
--- En date de : Lun 3.11.08, Iñaki Baz Castillo ibc@aliax.net a écrit : De: Iñaki Baz Castillo ibc@aliax.net Objet: Re: [Kamailio-Users] Remote-Party-ID header À: users@lists.kamailio.org Date: Lundi 3 Novembre 2008, 18h34
El Lunes, 3 de Noviembre de 2008, ALAEDDINE abbech escribió:
NDI:Numéro de Désignation d’Installation, is the number identifier the
link
with France telecom NDS:Numéro de Désignation Secondaire, is the number identifier the user agent.
No idea of how to represent these fields intoa PAI header. The main question is: how does your PSTN gateways require this PAI header?
On Mon, 2008-11-03 at 14:45 +0100, Iñaki Baz Castillo wrote:
El Lunes, 3 de Noviembre de 2008, ALAEDDINE abbech escribió:
thanks, I readed the RFC 3325 before sending my mail, but now my problem is to implement this RFC with the use of NDI and the NDS. Who know how put the NDI and the NDS in the header P-Asserted-Identity and P-Preferred-Identity?
Ok, what is NDI and NDS?
In some countries, France included, you do not have just an ANI associated with a POTS line. You have one "head of installation" number, that is specific to the global setup of a telco customer, and then specific ANIs for each endpoints. This is a problem in several protocols, because usually only one field exists.
Also, in SS7 peering with PTTs in some europpean countries, you need both numbers because only one of them is authoritative for identifying the line (then "installation ANI"), as the other one can be user-specified.
Think of it as a billing identity and a caller-id.
Jérôme Martin | LongPhone Responsable Architecture Réseau 122, rue la Boetie | 75008 Paris Tel : +33 (0)1 56 26 28 44 Fax : +33 (0)1 56 26 28 45 Mail : jmartin@longphone.fr Web : www.longphone.com
-
ALAEDDINE abbech -
Iñaki Baz Castillo -
Jerome Martin -
jh＠tutpro.com -
Nick Warr