Upgrading from 0.2.x

One of the most significant changes from 0.2.x version is that HTML5 video elements are not handled by JsSIP anymore. Instead, media stream handling tools are facilitated so you can freely decide when and where to attach the local and remote media Streams. For more info see JsSIP.RTCSession.

This version comes with a new concept of optional arguments, meaning that every argument in API methods wich are not mandatory, are enclosed in a JavaScript Object as the last method argument. The name of this argument is ‘options’.

The following changes must be taken into consideration when upgrading from 0.2.x to 0.3.x version.

UA Class

Configuration Parameters

• outgoing_proxy_set renamed to ws_servers.
• stun_server renamed to stun_servers.

call()

• Optional arguments are passed through the new ‘options’ argument.
• HTML5 video element references are not passed anymore.
• mediaTypes changed to mediaConstraints.

API 0.3.x | API 0.2.x

sendMessage()

• Optional arguments are passed through the new ‘options’ argument.

API 0.3.x | API 0.2.x

RTCSession Class

This is the new name for the old Session Class.

Instance Properties

• local_identity changed from String to JsSIP.NameAddrHeader instance.
• remote_identity changed from String to JsSIP.NameAddrHeader instance.

answer()

• Optional arguments are passed through the new ‘options’ argument.
• HTML5 video element references are not passed anymore.

API 0.3.x | API 0.2.x

terminate()

• Optional arguments are passed through the new ‘options’ argument.

API 0.3.x | API 0.2.x

cancel()

• Dissapears in favour of terminate().

reject()

• Dissapears in favour of terminate().