Hi John Markh,
We ran some tests and it seems this feature works with 3.2.0 using the
setup explained in comment #2.
It might be a configuration issue. To help you configure properly, I'm
giving you an example in form of a screenshot attached.
It might be another issue. To get a more clean
You are absolutly right; this setup does work! I have received a phone
call on the account which is using none standard port (Spikko) which
really surprised me because Ekiga does not change to status to
Registred as it does to any other SIP account which uses standard SIP
port.
--
No Option to
Hi,
Please attach a debug output; I would like to understand this
registration issue.
Best regards,
Yannick
--
No Option to Configure Registrar Port
https://bugs.launchpad.net/bugs/409842
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is a bug
Thanks.
I would change the importance from low to show stopper because it is
impossible to use Ekiga with large number of VoIP providers.
--
No Option to Configure Registrar Port
https://bugs.launchpad.net/bugs/409842
You received this bug notification because you are a member of Ubuntu
Desktop
Hi,
Could you write down a list? I'm doing support for Ekiga on a daily
basis since years and we do not have much reports about SIP providers
not using the standard 5060 listen port. A list will effectively raise
the priority upstream. btw, i'm part of upstream: Ekiga - About
Best regards,
A list... that would be tough as there are thousands of VoIP providers. Here
are some that require none standard SIP ports:
sip.ritstele.com
d1.spikko.com
i2telecom.com
From my experience, many organizations deploy VoIP solutions on a none
standard ports to increase security (by obscurity).
Thank you.
--
No Option to Configure Registrar Port
https://bugs.launchpad.net/bugs/409842
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is a bug assignee.
--
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
** Attachment added: Dependencies.txt
http://launchpadlibrarian.net/29959610/Dependencies.txt
** Attachment added: ProcMaps.txt
http://launchpadlibrarian.net/29959611/ProcMaps.txt
** Attachment added: ProcStatus.txt
http://launchpadlibrarian.net/29959612/ProcStatus.txt
--
No Option
Hi,
What happen if you specify a port in the registrar field in the account
window?
e.g.
Spikko
Registrar: d1.spikko.com:5090
SIPGate
Registrar: sipgate.co.uk:5060
Best regards,
Yannick
--
No Option to Configure Registrar Port
https://bugs.launchpad.net/bugs/409842
You received this bug
** Changed in: ekiga (Ubuntu)
Importance: Undecided = Low
** Changed in: ekiga (Ubuntu)
Status: New = Incomplete
--
No Option to Configure Registrar Port
https://bugs.launchpad.net/bugs/409842
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is
Tired, does not work (nothing happens at all).
** Attachment added: Screenshot.png
http://launchpadlibrarian.net/29962102/Screenshot.png
--
No Option to Configure Registrar Port
https://bugs.launchpad.net/bugs/409842
You received this bug notification because you are a member of Ubuntu
I pushed upstream and attached the bug here.
Thank you.
Best regards,
Yannick
** Bug watch added: GNOME Bug Tracker #590975
http://bugzilla.gnome.org/show_bug.cgi?id=590975
** Also affects: ekiga via
http://bugzilla.gnome.org/show_bug.cgi?id=590975
Importance: Unknown
Status:
Thanks for sent this upstream, marking it as triaged.
** Changed in: ekiga (Ubuntu)
Status: Incomplete = Triaged
** Changed in: ekiga (Ubuntu)
Assignee: (unassigned) = Ubuntu Desktop Bugs (desktop-bugs)
--
No Option to Configure Registrar Port
https://bugs.launchpad.net/bugs/409842
** Changed in: ekiga
Status: Unknown = New
--
No Option to Configure Registrar Port
https://bugs.launchpad.net/bugs/409842
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is a bug assignee.
--
desktop-bugs mailing list
14 matches
Mail list logo
