Later SDP regeneration

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



Hi!

Just to follow up for the archives:

On Fre, 2012-11-23 at 12:41 +0100, Bernd Petrovitsch wrote:
[...]
> On Die, 2012-10-23 at 11:05 +0200, Andreas Wehrmann wrote:
> > On 10/23/2012 10:59 AM, Bernd Petrovitsch wrote:
[..]
> What is actually the way to go with a media transport adapter if there
> is a change in the media streams which must be announced via a new SDP?
> Should the MTA call pjsua_call_reinvite() or pjsua_call_update()?

If I understand the RFCs correctly, that's actually the only way to go.

However, also working is:
- do not answer the call initially in any way. pjsua-lib itself sends an
  answer with 100 anyways. We just copy the remote SDP away.
- if we have the correct address+port, we finish the negotiation
  pjmedia_sdp_neg_negotiate() with the current call.
  We then completely redo the SDP negotiation with 
  pjmedia_sdp_neg_create_w_remote_offer() within the current call (using
  pjsua-internal.h header) to get the negotiator into the same state as
  before. Finally answer the call.
No need to change anything in pjsip's source code.

Kind regards,
	Bernd
-- 
mobile: +43 664 4416156              http://www.sysprog.at/
    Linux Software Development, Consulting and Services




[Index of Archives]     [Asterisk Users]     [Asterisk App Development]     [Linux ARM Kernel]     [Linux ARM]     [Linux Omap]     [Fedora ARM]     [IETF Annouce]     [Security]     [Bugtraq]     [Linux]     [Linux OMAP]     [Linux MIPS]     [Linux API]
  Powered by Linux