GNOME Bugzilla – Bug 705783
fails to make a call with voocall.cz
Last modified: 2013-08-12 12:23:01 UTC
Created attachment 251288 [details] PNG with account settings Description of problem: http://voocall.cz SIP provider works with Twinkle but not with Ekiga (and neither with Linphone). Version-Release number of selected component (if applicable): ekiga-4.0.1-1.fc18.x86_64 How reproducible: Always. Steps to Reproduce: Make a call to echo service. Actual results: Nothing happens, timeout. Expected results: Make a call. Additional info: I can provide my SIP account at http://voocall.cz if there is an interest. http://voocall.cz people are responsive, if one proves a SIP protocol violation they may fix it on their side.
Created attachment 251289 [details] PNG with echo service contact
Created attachment 251290 [details] Wireshark pcap with voocall.cz failed call from Ekiga
Created attachment 251291 [details] Wireshark pcap with voocall.cz successful call from Twinkle
Could you send me the -d 4 log of ekiga? Or alternatively if you can allow me to access temporarily an account on that server.
Ok, I looked into it. The problem is that with ekiga and twinkle you register to sip.voocall.cz. With twinkle you call ...@sip.voocall.cz and it works. With ekiga you call ...@voocall.cz and it does not. I called ...@sip.voocall.cz with ekiga and it works too. If you register with @sip..., you have to call with @sip... too, otherwise ekiga cannot know that you are registered to that address and use the correct user. Note also that voocall.cz and sip.voocall.cz have different IP addresses: snoopy:~$ host sip.voocall.cz sip.voocall.cz has address 77.78.119.186 sip.voocall.cz has IPv6 address 2001:1528:132:c00:0:2:5:1 snoopy:~$ host voocall.cz voocall.cz has address 77.78.119.183 voocall.cz mail is handled by 20 sns.nethost.sk. voocall.cz mail is handled by 10 mail-1.nethost.cz. So closing as notabug. Cheers, Eugen
There is also _sip._udp.voocall.cz which is A record 77.78.119.183 (although it should be SRV record). Anyway thanks for resolving it, I can confirm using @sip.voocall.cz everywhere (instead of @voocall.cz) works.