Re: Query regarding Owner IP in SDP field.

Kevin Boyle <[email protected]>
Newsgroups gmane.ietf.megaco
Message-ID <[email protected]>
Last I checked, the draft you reference has been expired for 3.5 years.  I
wouldn't put much stock in expired drafts.

As for conference vs. transfer, there are specific call processing
requirements for each outlined by the various regional SDOs.  These call
processing requirements are carried out, and billed for, by the MGC.  Since
the MG should just do what it is commanded by the MGC and has little to no
call processing knowledge, why does it need to know whether a particular
manipulation is any particular feature?

Kevin

-----Original Message-----
From: [email protected] [mailto:[email protected]] On Behalf Of
nupur gupta
Sent: Monday, December 15, 2008 5:50 AM
To: [email protected]
Subject: [Megaco] Query regarding Owner IP in SDP field.

Hi All,

Referring to the call flow examples, for Call Transfer and Call Conference,
given in the following:
http://tools.ietf.org/html/draft-ietf-megaco-callflows-04

As far as my understanding goes, the only way to differentiate between Call
Transfer and Call Conference at MG1/MG3 is to analyze the Owner IP field in
SDP part of MODIFY message (Step 37 and step 39, Sec 8.1).
If the owner IP received in SDP in Modify is same as previously received
owner IP, then it is Call Conference else it Call Transfer.

How ever, as per RFC3525, the owner IP field is optional and hence not
necessarily present in the SDP part.
So what is other way (and may be more concrete approach) to distinguish
between Call Transfer and Call conference at MG1 and MG3?

Thanks and Regards,
Nupur Gupta,
Software Engineer,
Aricent technologies ltd.
_______________________________________________
Megaco mailing list
[email protected]
https://www.ietf.org/mailman/listinfo/megaco
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.