IPOMakingMeInsane
Technical User
Does anyone in this forum know if Avaya will in the future support P-asserted-Identity or Remote-party-ID on the IPO?
Tek-Tips is the largest IT community on the Internet today!
Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!
-
Congratulations Chriss Miller on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!
SIP (P-Asserted-Identity or Remote-Party-ID)
- Thread starter IPOMakingMeInsane
- Start date
- Status
IPOfficeIreland
Technical User
it already does for outgoing and incoming but the provider needs to also support this, which most don't.
- Thread starter
- #3
IPOMakingMeInsane
Technical User
It does?
I have checked the RFCs that are supported by the IP Office and it does not mention RFC 3325. Remote-Party-ID never made it to a RFC(draft-ietf-sip-privacy-05.txt) and I only know of it as some ITSPs support it in favour over P-AI.
Unless you are running a different version to 4.1(9) I can't see any fields on the IPO to configure the P-AI or Remote-Party-ID headers for the invite sip message from an IPO.
The list that I have on supported RFCs are as below:
Rec. E.164 [2] - ITU-T Recommendation E.164: The international public telecommunication numbering plan
RFC 2833 [7] - RTP Payload for DTMF Digits, Telephony Tones and Telephony Signals
RFC 3261 [8] - SIP: Session Initiation Protocol
RFC 3263 [10] - Session Initiation Protocol (SIP): Locating SIP Servers
RFC 3264 [11] - An Offer/Answer Model with Session Description Protocol (SDP)
RFC 3323 [14] - A Privacy Mechanism for the Session Initiation Protocol (SIP)
RFC 3489 [18] - STUN - Simple Traversal of User Datagram Protocol (UDP) Through Network Address Translators (NATs)
RFC 3824 [24] - Using E.164 numbers with the Session Initiation Protocol (SIP)
I have checked the RFCs that are supported by the IP Office and it does not mention RFC 3325. Remote-Party-ID never made it to a RFC(draft-ietf-sip-privacy-05.txt) and I only know of it as some ITSPs support it in favour over P-AI.
Unless you are running a different version to 4.1(9) I can't see any fields on the IPO to configure the P-AI or Remote-Party-ID headers for the invite sip message from an IPO.
The list that I have on supported RFCs are as below:
Rec. E.164 [2] - ITU-T Recommendation E.164: The international public telecommunication numbering plan
RFC 2833 [7] - RTP Payload for DTMF Digits, Telephony Tones and Telephony Signals
RFC 3261 [8] - SIP: Session Initiation Protocol
RFC 3263 [10] - Session Initiation Protocol (SIP): Locating SIP Servers
RFC 3264 [11] - An Offer/Answer Model with Session Description Protocol (SDP)
RFC 3323 [14] - A Privacy Mechanism for the Session Initiation Protocol (SIP)
RFC 3489 [18] - STUN - Simple Traversal of User Datagram Protocol (UDP) Through Network Address Translators (NATs)
RFC 3824 [24] - Using E.164 numbers with the Session Initiation Protocol (SIP)
- Status
Similar threads
- Locked
- Question
