On Fri, 2010-03-05 at 11:48 +0530, Amarnath Kanchivanam wrote:
> Can anyone help me in understanding the difference BTW session and dialog?
The session is the "media", usually streams of RTP packets. A session
is described by SDP.
The dialog is relationship that is created/destroyed by the SIP
m
Attila Sipos wrote:
> So this leads me to another question:
>
> What is the practical difference between:
> sip:+12345...@domain.org;user=phone
> and
> sip:+12345...@anotherdomain.org;user=phone
and
tel:+12345678
> ?
>
> Is it that in the first case, the request gets sent t
The form of the user part is really the responsibility of the owner of
the domain. user=phone is really only meaningful if the domain owner
allows/supports that. In absence of user=phone, the domain may *choose*
to treat the user part according to tel uri syntax, or not.
*if* user=phone is pres
The E.164 problem is described in draft-elwell-sip-e164-problem-statement
Cheers,
-Victor
On Fri, Mar 5, 2010 at 3:13 PM, Attila Sipos
wrote:
>
> In response to a question "[Sip-implementors] Global and local - SIP
> URI",
> it was written:
>
>>>If the SIP URI has a param ;user=phone then the us
El Viernes 05 Marzo 2010, Attila Sipos escribió:
> So this leads me to another question:
>
> What is the practical difference between:
> sip:+12345...@domain.org;user=phone
> and
> sip:+12345...@anotherdomain.org;user=phone
> ?
>
> Is it that in the first case, the request gets sent to "d
In response to a question "[Sip-implementors] Global and local - SIP
URI",
it was written:
>>If the SIP URI has a param ;user=phone then the userinfo part is
supposed to
>>be a telephone number, sharing syntax with the TEL URI.
>>
>>So you could consider the following SIP URI as "global" (in term
El Viernes 05 Marzo 2010, Laurent Etiemble escribió:
> Hello,
>
> The and elements serves different purposes:
> - is used to reference an element.
Yes right, I missed that point and thought that it could also point to a
(within the same xcap-root). Thanks.
> 3.1). This way, the same ele
El Viernes 05 Marzo 2010, hanifa.mohammed escribió:
> Thanks for the response. Pl clarify my assumption.
>
> 1. So, when there is no "user=phone" parameter in the SIP uri, there is no
> context of Local or Global.
> Or is there any other way to figure out whether a SIP uri is global or
> local?
El Viernes 05 Marzo 2010, Alok 2 Tiwari escribió:
> A session is a collection of participants, and streams of media between
> them, for the purposes of communication. If SDP is used, a session is
> defined by the concatenation of the SDP user name, session
> id, network type, address typ
> Can anyone help me in understanding the difference BTW session
> and dialog?
RFC 3261 section 6 might be useful since it provides definitions for both.
___
Sip-implementors mailing list
Sip-implementors@lists.cs.columbia.edu
https://lists.cs.columbi
Thanks for the response. Pl clarify my assumption.
1. So, when there is no "user=phone" parameter in the SIP uri, there is no
context of Local or Global.
Or is there any other way to figure out whether a SIP uri is global or
local?
2. Simply the presence of '+' in the userinfo part of the SIP ur
There are more SIP response codes than relevant ISDN mappings
so translations can result in loss of original response code.
For ISDN-->SIP--->ISDN, this problem can be reduced by using
the SIP Reason header ( http://www.rfc-editor.org/rfc/rfc3326.txt )
where a Q.850 cause code can be specified.
12 matches
Mail list logo
