reuse m.proto when stringifying sdp

When stringifying a sdp that was parsed with sdp.js there is a bug where sdp.js uses m.transport instead of m.proto. This was resulting in RTP/SAVFP webrtc rtp profiles being stringified with the wrong rtp profile (RTP/AVP) because m.transport didn't exist.