You are not logged in.
Pages: 1
It may happen that although your VoIP phone works fine, adding an Ekiga account to the phone is not that successful. Here's my situation:
I have a VoIP phone (Siemens Gigaset C590 IP) with an account representing a fixed line from the Czech republic, not needing a STUN server set.
I have a router (TP-Link WR741ND) over it.
After adding the Ekiga account the same way as the other account, the account is registered and can receive/send calls, but it's all silent. The solution is:
Under the phone management: Settings > Telephony > Advanced VoIP settings - read values of SIP port and RTP ports range.
Under the router management: Forwarding > Virtual Servers > Add new... add these two items subsequently:
SIP port (probably 5060) forwarding to the IP of your phone (probably 192.168.something.something).
RTP ports range (probably 5004-5020) forwarding the same way.
Under the phone management: Settings > Telephony > Connections > the Ekiga account - make sure it's like this:
Authentication name, Username and Display name are your Ekiga account. Authentication password is your password.
Domain, Proxy server address and Registration server are "ekiga.net".
STUN is enabled and STUN server is "stun.ekiga.net".
All ports are 5060, except for STUN server port which is 3478.
I have also set Outbound proxy mode to Automatic and the server is again "ekiga.net" but I don't know if it's necessary.
It's not much Arch specific, but it may help. It's strange the older account works without port forwarding.
Offline
Pages: 1