On Mon, May 16, 2011 at 11:42 PM, Peter van der Salm <[email protected]> wrote: > Hi Folks, > > We have updated a well running 421 system by mid of april to 4.4.0, the then > current latest stable release. That worked very well. > Yesterday we upgraded to the now current latest stable 4.4.0-2011-05-10. > We now don't have any incoming calls from our SIP trunk anymore. The calls > come in, sipxbridge replies tot he ITSP with a 100 trying, and then nothing > happens, until we cancel the call. It's nice and quiet in the office, but not > too good for the business after all ;-) > See merged.xml attached and the sipxbridge log. > Any suggestions on how to solve this would be most welcome. If nothing helps > I am prepared to reinstall....It's not a huge installation after all. > I have tried to remove the specific gateway for the ITSP and recreated it, > but to no avail. > Clearly the sipxbridge throws an error at us in the log file: > > 2011-05-16T14:13:19.082000Z":1099:JAVA:ERR:lt-sipx-01.lumiad.com:Thread-117:00000000:AccountManagerImpl:"unexpected > er$ > java.lang.NullPointerException > at > org.sipfoundry.sipxbridge.AccountManagerImpl.getItspAccount(AccountManagerImpl.java:248) > at > org.sipfoundry.sipxbridge.AccountManagerImpl.getItspAccount(AccountManagerImpl.java:296) > at > org.sipfoundry.sipxbridge.SipListenerImpl.processRequest(SipListenerImpl.java:433) > at gov.nist.javax.sip.EventScanner.deliverEvent(EventScanner.java:224) > at > gov.nist.javax.sip.SipProviderImpl.handleEvent(SipProviderImpl.java:192) > at > gov.nist.javax.sip.DialogFilter.processRequest(DialogFilter.java:1151) > at > gov.nist.javax.sip.stack.SIPServerTransaction.processRequest(SIPServerTransaction.java:823) > at > gov.nist.javax.sip.stack.UDPMessageChannel.processMessage(UDPMessageChannel.java:499) > at > gov.nist.javax.sip.stack.UDPMessageChannel.processIncomingDataPacket(UDPMessageChannel.java:459) > at > gov.nist.javax.sip.stack.UDPMessageChannel.run(UDPMessageChannel.java:295) > at java.lang.Thread.run(Thread.java:619) > > The warning for the absence of 172.20.4.14 is from an absent gateway that we > do not use, and has been switched off by now. >
Save the sip trunk configuration one more time so sipxbridge.xml to be regenerated. If error still persist collect a snapshot and I'll take a look at. George _______________________________________________ sipx-users mailing list [email protected] List Archive: http://list.sipfoundry.org/archive/sipx-users/
