9 jul 2012 kl. 18:08 skrev Juha Heinanen:
Peter Dunkley writes:
I have no idea about the specifics of that test. It's not something I've ever used. But, the sipML5 client does send quite large INVITEs, so I wouldn't be at all surprised if they were larger than 4096 bytes.
yes, it turned out that the invite sent by sipml5 was 4432 bytes long due to large sdp.
it also turned out that sipml5 is using RTP/SAVPF audio that is not supported e.g. by sems:
Media Description, name and address (m): audio 39469 RTP/SAVPF 103 104 0 8 106 105 13 126
i wonder if any common sip clients support RTP/SAVPF?
Haven't seen that, but it's a requirement for WebRTC. I don't like that they are moving away from basic interoperability with SIP devices on the media plane, but it's happening slowly. All of us need to be on the WebRTC mailing lists and discuss this :-)
Cheers, /O