Re: [Sip-implementors] What's the difference between session and dialog in SIP?

Hi Amar, A dialog is a peer-to-peer SIP relationship between two user agents that persists for some time. The dialog facilitates sequencing of messages and proper routing of requests between the user agents. Adialog is identified by a call identifier, local tag, and a remote tag. A session is

[Sip-implementors] SIP-ISDN mappings 500>127>480

hi, Came to know that 500 on SIP should be implemented as 127 (page-58) on ISDN side but for the reverse mapping 127 is mapped to 480 (page-33). These pages are from " q.1912.5_ww9.doc " downloaded from " http://www.itu.int/itudoc/itu-t/aap/sg11aap/history/q1912.5/q.1912.5.html ".

[Sip-implementors] What's the difference between session and dialog in SIP?

Hi All, Can anyone help me in understanding the difference BTW session and dialog? Thanks Amar ___ Sip-implementors mailing list Sip-implementors@lists.cs.columbia.edu https://lists.cs.columbia.edu/cucslists/listinfo/sip-implementors

Re: [Sip-implementors] XCAP/OMA: Why rather than in resource-lists application?

Hello, The and elements serves different purposes: - is used to reference an element. It can be defined in another document but must be under the same XCAP root (RFC 4826 Para. 3.1). This way, the same element can appear at different places by reference and be defined in one place. The refere

Re: [Sip-implementors] [Simple] SIP SUBSCRIBE and PUBLISH Request URI Question

Hi. Please do not copy questions to both sip-implementors and IETF mailing lists. This question belongs only on the sip-implementors list. The short answer to your question is that nothing guarantees that a URI with a port indicates the same resource as the same URI without a port. For details,

Re: [Sip-implementors] Invalid character in Request URI Parameter

El Jueves, 4 de Marzo de 2010, Sorin Ionescu escribió: > Hi all, > > RFC 3261 sec 19.1.1 says that any SIP URI parameters that are not > recognized should be silently ignored. > > However, in the case that an invalid (not allowed by ABNF in sec 25) > character is encountered (such as a white spac

[Sip-implementors] Invalid character in Request URI Parameter

Hi all, RFC 3261 sec 19.1.1 says that any SIP URI parameters that are not recognized should be silently ignored. However, in the case that an invalid (not allowed by ABNF in sec 25) character is encountered (such as a white space or a ^) in a SIP URI on in the Request URI, what should and UAS

[Sip-implementors] SIP SUBSCRIBE and PUBLISH Request URI Question

Hi all, does anyone knows if there is a spec or extension from IETF, OMA or 3GPP, which defines that the SUBSCRIBE or PUBLISH Request URI with and without a port points to the same resource, that is, the URI canonized and without port? I've looked at IETF SIP, SUBSCRIBE and PUBLISH related RFCs and

[Sip-implementors] SIPit26 dates and location announced: Stockholm, Sweden May 17-21 2010

SIPforum, Edvina and Tandberg are happy to reveal facts about the next SIPit: - Kista - just north of Stockholm, Sweden - May 17-21, 2010 - Tests running Monday to Friday - Short seminars on hot topics to keep you up2date SIPit26 is hosted by Edvina and Tandberg and sponsored by a number of spons

[Sip-implementors] SIP-ISDN mappings 500>127>480

hi, Came to know that 500 on SIP should be implemented as 127 (page-58) on ISDN side but for the reverse mapping 127 is mapped to 480 (page-33). These pages are from " q.1912.5_ww9.doc " downloaded from " http://www.itu.int/itudoc/itu-t/aap/sg11aap/history/q1912.5/q.1912.5.html ".

Re: [Sip-implementors] Global and local - SIP URI

El Jueves, 4 de Marzo de 2010, hanifa.mohammed escribió: > Hi all, > > With respect to tel uri, there are two types: > 1. Global number - that starts with '+' > 2. Local number - others > > Similarly, is there any thing called Global Sip uri and Local Sip uri. > > My assumption: > Su