[Rtcomm] [Rtcomm] [Bug 6930] Incomming CallerID on VoIP account fails to associate with existing contact
From: bugzilla-daemon at maemo.org bugzilla-daemon at maemo.orgDate: Thu Dec 24 17:41:12 EET 2009
- Previous message: [Rtcomm] [Bug 6930] Incomming CallerID on VoIP account fails to associate with existing contact
- Next message: [Rtcomm] [Bug 6930] Incomming CallerID on VoIP account fails to associate with existing contact
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
https://bugs.maemo.org/show_bug.cgi?id=6930 matti.savolainen at verizon.net changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |matti.savolainen at verizon.net ------- Comment #5 from matti.savolainen at verizon.net 2009-12-24 17:41 GMT+3 ------- This may (or may not?) be related, but if I use a SIP VoIP provider that provides caller ID, it is not shown on N900. At home I have Viatalk VoIP service with caller ID. When using my Grandstream HT502 SIP adapter with a regular phone, I can see the incoming caller name (as long as Viatalk has it in their database...) When I tested this with my N900, I can only see the number at someIPaddress. It would be very nice if the N900 was able to utilize this common feature. -- Configure bugmail: https://bugs.maemo.org/userprefs.cgi?tab=email Replies to this email are NOT read, instead please add comments at https://bugs.maemo.org/show_bug.cgi?id=6930 ------- You are receiving this mail because: ------- You are the assignee for the bug, or are watching the assignee.
- Previous message: [Rtcomm] [Bug 6930] Incomming CallerID on VoIP account fails to associate with existing contact
- Next message: [Rtcomm] [Bug 6930] Incomming CallerID on VoIP account fails to associate with existing contact
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]