Hello, I have the following problem:
sipXrelay is set up with debug enabled. sipXproxy is allocating a bunch of bridges for its own nefarious purposes. A call request comes in. sipXproxy tries to contact the sipXrelay which is still allocating gzillion bridges. sipXrelay bombs because it goes to process the request and trips on itself as it is still allocating bridges for the same client that had previously neglected to wait for its request to complete. Is this a valid possible scenario? sipXrelay is not set up to deal with this form of re-entrancy. i.e. it cannot deal with multiple outstanding requests from a single client. However, that can be changed if needed. Is this something sipXproxy can be expected to guard against - i.e. block procoessing requests until it is done getting all the bridges it needs? Alternatively I can lock on the server (sipxrelay). Doing both might be considered overkill. Thanks Ranga -- M. Ranganathan
_______________________________________________ sipx-dev mailing list [email protected] List Archive: http://list.sipfoundry.org/archive/sipx-dev Unsubscribe: http://list.sipfoundry.org/mailman/listinfo/sipx-dev sipXecs IP PBX -- http://www.sipfoundry.org/
