Eric Green

Confirmed it in the code... @john-e-riordan this looks to be an order of operations issue. At the top of [`user-agent.stop()`](https://github.com/onsip/SIP.js/blob/master/src/api/user-agent.ts#L461) we transition to the `Stopped` state. We then cycle through...

To work around this you could dispose of your subscriptions manually before calling `stop()` on the user-agent.

Can you clean this up and provide some instructions and documentation on how it works?

The docs are generated automatically using https://www.npmjs.com/package/@microsoft/api-documenter. If you want to improve them we would happily take a PR.

I do not think that PhoneRTC in it's current state would work with SIP.js. What it does provide though is a good starting point at where mobile development is at....

@joseph-onsip, per our discussion it was my understanding that the changes you were making are javascript application level changes. The custom media handler should be compatible with any platform implementing...

Android L has built in WebRTC support. We have created an [iOS Cordova Plugin](https://github.com/onsip/onsip-cordova). Guides are available on [sipjs.com](http://sipjs.com/guides/mobile/cordova/).

I do not have much to report here, as you can probably tell from me removing the milestone. I can say that internally we are working on a mobile app...

@andrewvmail We ended up using native WebRTC and creating a custom SDH to interface with that. While I make it sound simple, it was far from that. At this point...

We have built the OnSIP mobile app using Nativescript. That being said - getting the WebRTC libraries to run in Nativescript is not for beginners. Some users have reported success...