On Tue, 2009-12-29 at 18:36 -0500, Alan van der Vyver wrote:
> Hi!
> 
> I have attached 6 trace files:
>       * trace3-2015 is extension 2015 registering with the 3.10 server
>         (from time stamp 22:35)
>       * trace3-2016 is extension 2016 registering with the 3.10 server
>         (from time stamp 22:35)
>       * trace4-2015 is extension 2015 registering with the 4.0.4
>         server using the 4.0.4 config file
>       * trace4-2016 is extension 2016 trying to register as 2015 on
>         the 4.0.4 server  using the 4.0.4 config file (thus 2016 does
>         not register)
>       * trace4-2-2015 is extension 2015 registering with the 4.0.4
>         server but using the config file from the 3.10 server.
>       * trace4-2-2016 is extension 2016 registering with the 4.0.4
>         server but using the config file from the 3.10 server.
> All traces were taken from the same telephone. The IP address of the
> 3.10 server is 10.0.100.11 (host name sipx1cvg) and the IP address of
> the 4.0.4 server is 10.0.100.12 (host name sipx2cvg).
> 
> To recap:
>      1. The phone, a Grandstream GXP 2010) has lines 2015 and 2016
>         configured on it.
>      2. When it is provisioned from the 3.10 server, both lines
>         register.
>      3. When it is provisioned from the 4.0.4 server, only one line
>         registers. When the server tells it to authenticate, the
>         second line tries to register as the first one.
>      4. In this latest round of tests, I tried copying the
>         configuration file for the phone from the 3.10 server to the
>         4.0.4 server, so when it reboots, it picks up the same
>         configuration it would have got from the 3.10 server. Both
>         lines then register OK.
>      5. It seems quite clear then that something in the provisioning
>         configuration file created by the 4.0.4 server is causing the
>         erroneous registration behaviour.
>      6. I don't really know what that might be. I have examined the
>         two files, but don't know enough to make some intelligent
>         guesses. There are too many changes to just work through each,
>         one-by-one.
> Any suggestions would be welcome.

Have you compared the working and non-working configuration files?



_______________________________________________
sipx-users mailing list sipx-users@list.sipfoundry.org
List Archive: http://list.sipfoundry.org/archive/sipx-users
Unsubscribe: http://list.sipfoundry.org/mailman/listinfo/sipx-users
sipXecs IP PBX -- http://www.sipfoundry.org/

Reply via email to