GNOME Bugzilla – Bug 416478
Caller identification and evolution
Last modified: 2007-03-10 13:47:44 UTC
We have asterisk VoIP. I can call to any phone with number (eg 123 456 789). When I receive call it is identified as sip:123456789@192.168.1.1 Ekiga can use evolution only for VOIP URL. I would like to be able to choose any normal phone number from evolution and dial it. When I receive call I want to identify user from recieved number. It needs to specify "default SIP server", which is going to be used as suffix for dialing (maybe to use the server I am registered to).
Eh... the third first paragraphs seem to ask ekiga to recognize who's calling depending on where the call comes from. This is about receiving calls. The fourth seems to be about making calls -- and is alreay implemented : you can set one of your account as the default. Could you clarify ?
When I receive call from my VoIP server from normal phone line it is received sip:123456789@192.168.1.1. In my evolution contacts I have phone number as 123 456 789. So when I call number I would like to be able to dial by selecting contact with phone number "123 456 789" and let it be dialed as sip:123456789@192.168.1.1. What I am asking for is some kind of translation between "real phone number" and sip. Is it more clear now? Thanks.
Well, it isn't that clearer : 1) did you notice that you just have to double-click on someone in the call history to call it ? 2) if you're registered to your VoIP server @192.168.1.1 and it is set as the default route for calls, then you just have to dial 123456789 in ekiga, and ekiga will try to call that number @192.168.1.1. All in all, I don't see which enhancement you're asking... doesn't ekiga already do it!?
Ekiga can't dial strings that are in a POTS field of a contact in Evo. I guess that's pt.1. The other thing (default account) is unclear, as it already does that. J.
Perhaps we could use the POTS field of an evolution contact, if there's no VoIP field ?
#334470 is related, maybe even a dup.
You are right. It is a dup (closing). I missed this one. I would really like to have this feature. *** This bug has been marked as a duplicate of 334470 ***