On Mon, 2008-06-16 at 16:58 -0400, Arjun Nair wrote: > sipX version information: > sipxportlib 3.10.1-012233 2008-04-14T18:08:20 oem-centos5 > sipxtacklib 3.10.1-012233 2008-04-14T18:13:36 oem-centos5 > sipxmedialib 3.10.1-012233 2008-04-14T18:17:34 oem-centos5 > sipxcalllib 3.10.1-012233 2008-04-14T18:21:26 oem-centos5 > sipxcommserverlib 3.10.1-012233 2008-04-14T18:26:07 oem-centos5 > sipxregistry 3.10.1-012233 2008-04-14T18:30:52 oem-centos5 > sipxpublisher 3.10.1-012233 2008-04-14T18:30:15 oem-centos5 > sipxproxy 3.10.1-012233 2008-04-14T18:29:15 oem-centos5 > sipxconfig 3.10.1-012233 2008-04-14T18:39:49 oem-centos5 > sipxvxml 3.10.1-012233 2008-04-14T18:32:36 oem-centos5 > sipxacd 3.10.1-012233 2008-04-14T18:42:50 oem-centos5 > sipxpbx 3.10.1-012233 2008-04-14T18:45:06 oem-centos5 > > You are right.. It looks like the code I am running is previous to rev. > 12619.. I am running this off the SCS Maint. Rls, which I was under the > impression is based on branch 3.10, but, clearly, that's not the case.. > Let me upgrade to branch 3.10 and test this. Thanks very much for your > help..
There's a very specific change to how these requests are routed in rev. 12619. That requires fixing some problems with the registrar code, and the Interop configuration was updated in parallel. This was to fix XECS-1313. You'll either have to move the codebase to a newer revision, or move the Interop configuration back to match the codebase. Whichever you choose, I'd like you to verify that it works. Dale _______________________________________________ sipx-dev mailing list [email protected] List Archive: http://list.sipfoundry.org/archive/sipx-dev Unsubscribe: http://list.sipfoundry.org/mailman/listinfo/sipx-dev
