Here is a brief description on how IPSec sec-agree is used in IMS:
http://betelco.blogspot.com/2008/09/ipsec-using-security-agreement-in-3gpp.html
--- En date de : Mer 5.1.11, Olle E. Johansson a écrit :
De: Olle E. Johansson
Objet: Re: [Sip-implementors] SIP Soft Phone with IPSec Support
À: "
For Android: http://code.google.com/p/imsdroid/
For Windows: http://code.google.com/p/boghe/
--- En date de : Mar 4.1.11, voice freak a écrit :
De: voice freak
Objet: [Sip-implementors] any SIP soft-phone supported with MSRP??
À: Sip-implementors@lists.cs.columbia.edu
Date: Mardi 4 janvier 2011
Hi,
You can also try doubango (http://doubango.org/).
Android demo project: http://code.google.com/p/imsdroid/
iOS demo project: http://code.google.com/p/idoubs/
Regards,
--- En date de : Mer 20.5.09, Mike Coffee a écrit :
De: Mike Coffee
Objet: Re: [Sip-implementors] SIP Stacks
À: "Iñaki Ba
Hi,
You can also try doubango (http://doubango.org/).
Android demo project: http://code.google.com/p/imsdroid/
iOS demo project: http://code.google.com/p/idoubs/
Regards,
--- En date de : Mar 13.7.10, Bogdan-Andrei Iancu a
écrit :
De: Bogdan-Andrei Iancu
Objet: Re: [Sip-implementors] Open So
, Iñaki Baz Castillo a écrit :
De: Iñaki Baz Castillo
Objet: Re: Re : [Sip-implementors] Does SIP/SDP allow one-way RTP?
À: "Bossiel thioriguel"
Cc: sip-implementors@lists.cs.columbia.edu
Date: Vendredi 19 mars 2010, 2h54
2010/3/19 Bossiel thioriguel
>
> Alice MUST add the
Alice MUST add the new "m=video" line below the old "m=" lines in the new Offer
(The order is important). Bob should accept the Offer by sending a SDP response
containing a "m=video" line with a port number equal to zero.
References: RFC 3264 subclause 6 (for the answer with port =zero) and RFC 3
The ABNF you provided is equivalent to:
( "0" ( "." DIGIT{,3} )? ) | ( "1" ( "." "0"{,3} )? ) and this mean that both
"q=0." and "q=1." OK.
--- En date de : Jeu 18.3.10, Brett Tate a écrit :
De: Brett Tate
Objet: Re: [Sip-implementors] Query on qvalue in SIP headers
À: "Brez Borland" , "prash
--- En date de : Jeu 18.3.10, Attila Sipos a
écrit :
De: Attila Sipos
Objet: RE: Re : [Sip-implementors] does sips imply TLS (and TLS alone)?
À: "Bossiel thioriguel" ,
sip-implementors@lists.cs.columbia.edu
Date: Jeudi 18 mars 2010, 11h54
thanks for your response
>>Ne
Neither "transport=tls" nor "sips:" are mandatory when using SIP over TLS
connection.
As per RFC 5630 subclause 3.1.3:
Because a SIPS URI implies that requests sent to the resource
identified by it be sent over each SIP hop over TLS, SIPS URIs are
not suitable for "best-effort TLS": they ar
what are you trying to achieve?
--- En date de : Ven 24.7.09, Iñaki Baz Castillo a écrit :
De: Iñaki Baz Castillo
Objet: Re: [Sip-implementors] Any "standarized" subset of 'pres-rules' document
(RFC 5025) ?
À: sip-implementors@lists.cs.columbia.edu
Date: Vendredi 24 Juillet 2009, 12h24
El Vie
date de : Ven 24.7.09, Avasarala Ranjit-A20990 a
écrit :
De: Avasarala Ranjit-A20990
Objet: RE: [Sip-implementors] Any "standarized" subset of 'pres-rules'document
(RFC 5025) ?
À: "Bossiel thioriguel" ,
sip-implementors@lists.cs.columbia.edu, "Iñaki Baz Castil
nt
(RFC 5025) ?
À: sip-implementors@lists.cs.columbia.edu
Date: Vendredi 24 Juillet 2009, 11h38
El Viernes, 24 de Julio de 2009, Bossiel thioriguel escribió:
> Hi,
>
> You are right but there there are some implementation guidelines.
> The main goal of these specifications is to
Hi,
You are right but there there are some implementation guidelines.
The main goal of these specifications is to ease interoperability.
For example : RCS clients are based on
[OMA-WP-XDM_1_1_Implementation_Guidelines-20081209-A] (among others) which
explain how your XCAP documents MUST be stru
Hi all,
Hi have released the first beta version of libSigComp an open source SigComp
API. This API can be easily integrated in existing SIP/IMS stacks (UE, P-CSCF,
PoC ...) without major changes.
home page: http://code.google.com/p/libsigcomp/
implemented: RFC3320, RFC3485, RFC4077, RFC4464, R
Try xlite
--- En date de : Dim 19.7.09, Pete Kay a écrit :
De: Pete Kay
Objet: [Sip-implementors] SIP Text Message
À: sip-implementors@lists.cs.columbia.edu
Date: Dimanche 19 Juillet 2009, 10h08
Hi,
I am trying to test out SiP MESSAGE, but I am not able to use SIPP to
generate SIP MESSAGE mes
I have never seen such specifications. But If you want to compress your xcap
data I think you should use SigComp (gzip, deflate, lz77 ... for compression
and UDVM for decompression).An Open-Source SigComp Framework (LGPL)
--> http://code.google.com/p/libsigcomp/
--- En date de : Ven 10.7.09, I
Here is an elegant way to store avatars (used in GSMA RCS) using XCAP -->
http://www.openmobilealliance.org/technical/release_program/docs/CopyrightClick.aspx?pck=PresenceSIMPLE&file=V2_0-20081223-C/OMA-TS-Presence_SIMPLE_Content_XDM-V1_0-20081223-C.pdf
known as [OMA Presence SIMPLE Content].
---
Hi all,
I have a question about MSRP client ports binding.
I have two clients used in the IMS context (SIP signaling before setting up
MSRP connections). The first client(UE1) send an INVITE to the second
client(UE2).
a)The UE1 request(SIP INVITE) contains a port number (both in media line and
Hi,
Here you can find good article about service routes in IMS context -->
http://betelco.blogspot.com/2008/11/proxy-and-service-route-discovery-in.html
You can download an IMS Client and make traces to understand how this feature
is used (try Mercuro IMS Client or OpenIC).
--- En date de : Ven
P sdp do not react to 407s, XCAP documents cannot be saved properly, no
visible support for MSRP relay.
Regards,Adrian
On Sep 17, 2008, at 2:47 PM, Bossiel thioriguel wrote:
Last month we have discovered a new IMS client that fully support MSRP for
instant messaging (RFC 4875). It&#x
Mercuro IMS Client also implement XCAP. Mercuro IMS Client is fully compliant
with main OMA specifications like:
Capabilities query (xcap-caps)
RLS Service (rls-services)
Resource List (resource-lists)
IETF Presence Rules (pres-rules)
OMA Presence Rules (org.openmobilealliance.pres-rules)
OMA XCAP
Last month we have discovered a new IMS client that fully support MSRP for
instant messaging (RFC 4875). It's name is Mercuro IMS Client
___
Sip-implementors mailing list
Sip-implementors@lists.cs.columbia.edu
https://lists.cs.columbia.edu/cucs
22 matches
Mail list logo
