[ekiga] ekiga.schemas: fix a possible UDP port collision

[Eugen Dedu <ededu src gnome org>]

commit 5594395f76f6010de68343b657cd8b86586d0807
Author: VÃctor Manuel JÃquez Leal <vjaquez igalia com>
Date:   Fri Dec 21 19:30:19 2012 +0100

    ekiga.schemas: fix a possible UDP port collision
    
    The SIP listen port is configured to be 5060, and the default UDP port
    range is from 5060 to 5100. This means that the first UDP port used by
    Opal is going to be 5060, but it will already be used by the SIP
    endpoint, causing an error in the connection. At the next port
    binding, the problem will be solved "magically".
    
    This issue has raised in the gatekeeper registration process: after
    setting up the SIP and the H323 endpoints, the H323 endpoint starts
    the gatekeeper registration. Opal uses the first port in the UDP range
    to connect to the configured gatekeeper, i.e. 5060, but the
    registration silently fails, because the port is already in use. The
    workaround was to unregister and register again.
    
    It remains to do the migration on current ekiga installations.
    
    Closes bug #690621.

 ekiga.schemas.in.in |    2 +-
 1 files changed, 1 insertions(+), 1 deletions(-)
---
diff --git a/ekiga.schemas.in.in b/ekiga.schemas.in.in
index a2c18e4..0f17555 100644
--- a/ekiga.schemas.in.in
+++ b/ekiga.schemas.in.in
@@ -413,7 +413,7 @@
       <applyto>/apps/@PACKAGE_NAME@/protocols/ports/udp_port_range</applyto>
       <owner>Ekiga</owner>
       <type>string</type>
-      <default>5060:5100</default>
+      <default>5061:5100</default>
       <locale name="C">
 	<short>UDP port range</short>
 	<long>The range of UDP ports that Ekiga will use.</long>