hi all,
*section 5 UAC Behavior (RFC 3841)*
"If the UAC wants to determine whether *servers along the path*
understand the header fields described in this specification(rfc 3841
,caller preference)."
As per 3841 the caller preference header processing is done only at the
proxy,which is the
see RFC3455 http://www.ietf.org/rfc/rfc3455.txt section 4.5.2.3 Examples of
Usage message F2 (P-Charging-Function-Addresses)
Not recommended though - it violates RFC3261
Regards,
Jeroen
Nap wrote:
> Is there a precedence somewhere of a SIP header with a multivalued
> parameter (not header).
>
Is there a precedence somewhere of a SIP header with a multivalued
parameter (not header).
An example could be -
Some-Header: Value;p1=pvalue1;p1=pvalue2;p1=pvalue3 etc [Note name of
param is p1 only]
Alternatively I could think of -
Some-Header: Value;p1=pvalue1|pvalue2|pvlaue3 with a specia
The Pingtel public server does it.
See http://interop.pingtel.com/
___
Sip-implementors mailing list
Sip-implementors@cs.columbia.edu
https://lists.cs.columbia.edu/cucslists/listinfo/sip-implementors
>
> 1. How could be differented SIP softphone and IP phone.
>
A "softphone" generally refers to a software-based VoIP endpoint that runs,
for example, on a PC. A "SIP softphone" is simply a softphone that uses SIP
as its signaling protocol.
An "IP phone" generally refers to a hardware-based VoIP
Hello friends,
I have doubts about the SIP section:
1. How could be differented SIP softphone and IP phone.
2.When we configure SIP client as behind NAT setup, in which SIP section
describe the 'type of NAT' in SIP messages.
Could you please explain me in detailed manner.
Thanks & Regards,
Bin:
RFC 3863 describes application/pidf.
- Somesh
Bin Chen <[EMAIL PROTECTED]> wrote: I found the xml in the presence notify as
following:
entity="sip:[EMAIL PROTECTED]:5060">
open
sip:[EMAIL PROTECTED]:5060
online
What is the tuple id from? Or is it a don't care value? Wh
