On Thu, Jan 12, 2012 at 9:55 PM, George Niculae <[email protected]> wrote: > On Thu, Jan 12, 2012 at 9:29 PM, George Niculae <[email protected]> wrote: >> On Thu, Jan 12, 2012 at 8:52 PM, Sven Evensen <[email protected]> >> wrote: >>> Snapshot attached. It is most likely the 550 user as this is the one giving >>> the "internal error" >>> >> >> Yes, there is a problem with that schedules for that user, deleting >> them and recreating should fix the problem. Let me check exactly which >> schedule gives error >> > Actually here is where your problem lies: > > INSERT INTO ring (ring_id, number, "position", expiration, ring_type, > user_id, enabled, schedule_id) VALUES (221, '559', 0, 30, 'At the same > time', 29, true, 5); > INSERT INTO ring (ring_id, number, "position", expiration, ring_type, > user_id, enabled, schedule_id) VALUES (223, '560', 2, 1, 'If no > response', 29, true, 2); > INSERT INTO ring (ring_id, number, "position", expiration, ring_type, > user_id, enabled, schedule_id) VALUES (224, '560', 3, 1, 'If no > response', 29, true, 4); > > ring position for user 550 are 0, 2, 3 instead 0, 1, 2 - not sure how > it make it this way > > You could repair it by: > > psql -U postgres SIPXCONFIG > update ring SET position=1 where ring_id=223; > update ring SET position=2 where ring_id=224; > > --
Accidentally replied off-list, so back to it - problem was caused by SOAP API usage (poor validation) and repaired in postgres db George ----------- Come meet us at CoLab @ CSU in March (5th & 6ht) http://www.sipfoundry.org/sipx-colab http://wiki.sipfoundry.org/display/sipXecs/2012+sipX-CoLab+Hackfest _______________________________________________ sipx-users mailing list [email protected] List Archive: http://list.sipfoundry.org/archive/sipx-users/
