I did the 4.0.4 -> 4.2 upgrade last night and everything appears to have gone smoothly so far except when I started testing new features I noticed SLA had a peculiar problem that I thought worth mentioning. If you have an HA environment and DNS SRV is splitting the registrations between those servers, then SLA/BLA will only work between phones that are registered on the same server.
As a test I set up a shared line on 4 phones. After they rebooted their registrations were split between my two servers. When I seized the line by picking it up, I notice only one of the other phones showed the line was seized. When I went to one of the phones that didn't show the line seize and seized the line, only one of the other phones showed the line seize. The common factor was where the phone had registered. The workaround I implemented until I can figure out what is going in is to set the outbound proxy on each shared line to point to only one of the servers. Once I did this SLA behaved as expected. How is SLA/BLA infromation communicated amongst servers? Where should I begin in troubleshooting this problem? _______________________________________________ sipx-users mailing list [email protected] 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/
