Re: Terminology (was RE: Fwd: I-DACTION:draft-rosenberg-sip-target-uri-delivery-01.txt
"Elwell, John" <[email protected]>
| Newsgroups | gmane.ietf.sip |
|---|---|
| Message-ID | <0D5F89FAC29E2C41B98A6A762007F5D001A27C69@GBNTHT12009MSX.gb002.siemens.net> |
(Old messages stripped to prevent blocking) Hans Erik, The way I interpreted the 01 draft, you would not get the freephone number anyway. If that is a requirement, then I accept my suggestion won't suffice. John ________________________________ From: Hans Erik van Elburg [mailto:[email protected]] Sent: 12 March 2009 12:57 To: Elwell, John Cc: [email protected] Subject: Re: [Sip] Terminology (was RE: Fwd: I-DACTION:draft-rosenberg-sip-target-uri-delivery-01.txt But that does not solve the freephone service use case. Freephone represents a use case where the R-URI is replaced with an AoR of user B - not with the contact of user B. A calls Bfreephonenumber routed the B (AOR) routed to B's contact. The target-uri draft is interested in obtaining: Bfreephonenumber as that is what A used to reach B. So what we like to see that B UA receives is something like H-I: Bfreephone; "istarget",\ B,\ contact-B So you want to get Bfreephonenumber and not B. In certain situations you are also interested in B, I guess that PBX's would interested in that to deliver to the correct user. We could distinguish them like: H-I: Bfreephone; "istarget",\ B,"aor"\ contact-B BR, /Hans Erik van Elburg _______________________________________________ Sip mailing list https://www.ietf.org/mailman/listinfo/sip This list is for NEW development of the core SIP Protocol Use [email protected] for questions on current sip Use [email protected] for new developments on the application of sip