hi,
Outbound Proxy: A proxy that receives requests from a client, even
though it may not be the server resolved by the Request-URI.
Typically, a UA is manually configured with an outbound proxy,
or can learn about one through auto-configuration protocols.
SIP proxy servers face the public Inter
Hi,
RFC2617 defines the following rule to extract header values for
calculating response:
===
The notation unq(X) means the value of the quoted-string X without the
surrounding quotes.
===
and later e.g.:
===
request-digest = <"> < KD ( H(A1), unq(nonce-value)
El Sábado, 11 de Julio de 2009, Bossiel thioriguel escribió:
> Here is an elegant way to store avatars (used in GSMA RCS) using XCAP -->
> http://www.openmobilealliance.org/technical/release_program/docs/CopyrightC
>lick.aspx?pck=PresenceSIMPLE&file=V2_0-20081223-C/OMA-TS-Presence_SIMPLE_Con
>tent_
> What are the differences between a SIP Proxy and an OUTBOUND SIP Proxy ?
See rfc3261 section 6.
___
Sip-implementors mailing list
Sip-implementors@lists.cs.columbia.edu
https://lists.cs.columbia.edu/cucslists/listinfo/sip-implementors
Dear all,
What are the differences between a SIP Proxy and an OUTBOUND SIP Proxy ?
Thanks
BR,
Manoj
___
Sip-implementors mailing list
Sip-implementors@lists.cs.columbia.edu
https://lists.cs.columbia.edu/cucslists/listinfo/sip-implementors
Might be useful to look already in the revised SDP Offer/Answer protocol
(which extends RFC 3264):
SDP Capability Negotiation (204109 bytes)
http://www.ietf.org/internet-drafts/draft-ietf-mmusic-sdp-capability-neg
otiation-10.txt
SDP media capabilities Negotiation (99351 bytes)
http://www.ietf.
The offer/answer stuff is unique to the dialog; thus an INVITE's offer can have
an answer for each dialog if forking occurs.
If user A's phone doesn't support interactions with a forking proxy (or
unwilling to honor it), it can release the calls per RFC 3261. The originator
does not send 487 t
Hi All,
For CRBT or Announcement scenario we are seeing the behaviour as below :
User A sends an initial offer in the INVITE message. The proxy finds that the
terminating sip user agent B
has CRBT set on it. So the proxy forks the INVITE to both the music server and
the user B. We receive 1
Hello all,
I am using my sip server with Microsoft-exchange server.
But my calls are not getting through
As i have configured all the required settings at both the ends.
Also I am able to ping both of my systems from one-another.
But when my calls are going to SIP server to MS-exchange it
> Is there any priority/order being mentioned about the handling
> of Supported/Unsupported header, Say if both header contains
> the same item, then should the feature be enables or disabled?
As with many abnormal situations, nothing is documented concerning it. You can
act however you wish.
Hi Alex,
According to RFC 3261:
To= ( "To" / "t" ) HCOLON ( name-addr
/ addr-spec ) *( SEMI to-param )
name-addr = [ display-name ] LAQUOT addr-spec RAQUOT
addr-spec = SIP-URI / SIPS-URI / absoluteURI
display-name = *(token LWS)/ quoted-string
to-param = t
Hi All,
Is there any priority/order being mentioned about the handling of
Supported/Unsupported header, Say if both header contains the same item,
then should the feature be enables or disabled?
Girish T
HUAWEI TECHNOLOGIES CO.,LTD. huawei_logo
Tel: 9739593216
Iñaki Baz Castillo wrote:
> El Martes, 14 de Julio de 2009, Alex Balashov escribió:
>> Greetings,
>>
>> Let's say I have a To header that looks something like this:
>>
>>To: ;
>>
>> Is the trailing semicolon valid despite no header parameters following
>> it? How should this be handled by a UA
El Martes, 14 de Julio de 2009, Alex Balashov escribió:
> Greetings,
>
> Let's say I have a To header that looks something like this:
>
>To: ;
>
> Is the trailing semicolon valid despite no header parameters following
> it? How should this be handled by a UAS?
My 100% SIP strict parser says t
14 matches
Mail list logo
