decode tel: URIs and expose over D-Bus to allow PSTN heuristics
Submitted by Robert McQueen @ramcq
Assigned to Mikhail Zabaluev
Description
23:38 < DocScrutinizer> Robot101: there's a problem with telepathy-sofiaSIP, contacts, and dialer. I got an account at sipgate.de, a german SIP provider. It has an associated landline number. Inbound call from e.g landline "+49 911 123456" are signalled and logged as origin:"SIP:0911123456@sipgate.de". This doesn't match to any contact that has tel:"0911123456" nor to "+49911123456". My question: is there a concept in telepathy to deal with this?
23:40 < Robot101> alas no, the address book code in the N900 has special-cases for doing suffix lookups on incoming PSTN calls, but the same isn't true of SIP URIs
23:40 < Robot101> it would need to have some heuristic to decompose them to pull out a telephone number
23:40 < Robot101> but it's always going to be a kinda lame hack
23:55 < DocScrutinizer> well, in twinklephone there's an option to check for "...;call=tel" parameter and in that case discard the domain part and display the user part as a plain simple phonenumber. Service "tel:" in any SIP addr should get handled same way. But yeah, basically I agree there has to be heuristics to deal with that, as there seems to be no consistent standard how carriers handle signalling of inbound calls via PSTN gateway
23:56 < Robot101> aha, call=tel sounds useful
23:56 < Robot101> want to send a wishlist bug to telepathy-rakia and say "expose tel: and ;call=tel numbers through a different namespace so that UIs can apply PSTN heuristics"?
(... he didn't ... :D)