Merged doc confirms you are telling the truth :-). We need the
sipXbridge logs to see what exceptions it encountered that caused it to
respond with such. It would also be a good idea to upgrade to 4.4 to
make sure we are not hunting bugs that are already fixed in the current
release.
On 04/30/2011 04:44 AM, Peter van der Salm wrote:
Sorry, forgot to attach the merged.xml...
Hi Folks,
I have attached a merged.xml file from several calls to 0204638507, a number in
the PSTN to which our SipXecs is connected through the Sipxbridge and a SIP
trunk.
Sipxbridge throws a 500 server internal error at us with some of the calls.
This seem to happen for a couple of minutes after another, and then after some
time the same call from the same source is just handled normally. We are
running 4.2.1-018971.dhubler 2010-08-21T04:59:18 build34.
Has anybody an idea on what the cause of this behaviour might be? Or even an
idea on how to solve this?
thanks in advance!
Peter van der Salm
Smart Future cv,
Buys Ballotstraat 14,
3572 ZR Utrecht,
The Netherlands
phone: +31 308 793 512
fax: +31 847 156 296
mobile: +31 620 749 471
[email protected]
_______________________________________________
sipx-users mailing list
[email protected]
List Archive: http://list.sipfoundry.org/archive/sipx-users/
_______________________________________________
sipx-users mailing list
[email protected]
List Archive: http://list.sipfoundry.org/archive/sipx-users/
