Re: SIPit23 Survey Notes
Thomas Froment <[email protected]>
| Newsgroups | gmane.ietf.sip |
|---|---|
| Message-ID | <[email protected]> |
Klaus Darilion wrote: > Hi Robert! > > Robert Sparks schrieb: >> >> 19% supported SIP over IPSec > > What do you mean with "SIP over IPSec"? Every protocol runs over IPSec > as it is transparent to the application. Well, SIP over IPsec is not really "transparent" to the SIP implementation: when you want to send a request over an IPSec SA, you MUST be able to choose what is the source interface / source port and destination interface / destination port. This is not something so easy to implement at SIP transport level. Thomas > >> I asked where people were taking bits from messages to display as >> caller-id. >> There were many different kinds of answers, including >> P-Asserted-Identity if present, then From >> From display name >> username part of From uri >> P-Asserted-Identity only >> Contact uri >> Remote IP address >> P-Asserted-Identity, then Remote-Party-ID, then From >> From, then Remote-Party-ID, then P-Asserted-Identity > > So, if the From header is missing ???, the other headers are used? > > thanks for the summary > Klaus > _______________________________________________ > 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 _______________________________________________ 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