torkell: (Default)
2012-11-16 08:38 pm
Entry tags:

[livejournal.com profile] boggyb's laws of IP phones

Bonus post!

I would like to propose [livejournal.com profile] boggyb's laws of IP phones:

Law 1: Every IP phone will contain an easy-to-hit bug that makes it completely unusable for a common call flow.
Law 2: No two IP phones have the same bug.
Law 2a: Different versions of the same IP phone will have different bugs.

A bit of background: in SIP (which is what every IP phone that isn't Skype uses), you start a call by sending a request to the callee along with a SDP offer, which contains a list of media streams and codecs you support along with the IP address/port to send them to. The callee replies with a SDP answer containing the codec(s) that it has chosen for the call, along with where the callee expects to receive media on. Usually the answer contains a single codec which both ends will then use. The offer/answer process can be repeated during a call, for example to add a video stream. It's all deceptively simple but full of pitfalls for the unwary.



Anyway, on with the fail! Naming no names, because I can't remember which one has which bug.

Media FAIL )



The fail is not limited to handling audio - some clients can't even cope with the SIP signalling!

Extra FAIL )
torkell: (Default)
2011-07-08 08:29 pm
Entry tags:

Epic technology fail

By unaminious demand (even the spambot voted for it!), you get a tale of epic technology fail. Actually, it's not all that epic. But that didn't make it any less annoying.

Today's fail involves a collection of SIP phones, along with a B2BUA (which pretends to be two more SIP phones stuck together). The call scenario is a reasonably simple one: SIP phone A calls the B2BUA. The B2BUA does a blind transfer to SIP phone B, which diverts to SIP phone C.

The part of the SIP phones will be played by a collection of lolcats, while the B2BUA is played by a much more intelligent fox. Now, this is what's supposed to happen...
Here be lolcats! )