On Tue, Apr 6, 2010 at 7:42 AM, M. Ranganathan <[email protected]> wrote: > On Mon, Apr 5, 2010 at 4:40 PM, M. Ranganathan <[email protected]> wrote: >> On Mon, Apr 5, 2010 at 4:34 PM, Lazy Burd <[email protected]> wrote: >>> checkin 18325 to remove UDP as a listeningPointAddress is causing the >>> following error in any standard sipxecs installation AFAIK >>> >>> "2010-04-05T08:02:31.521000Z":42759:JAVA:INFO:systemp01:Timer-7769:00000000:WaitingForStartState:"WaitingForStartState::start >>> caught exception: "" >>> org.sipfoundry.sipcallwatcher.SubscribeDialog.SubscribeDialogStateException: >>> java.lang.NullPointerException >>> at >>> org.sipfoundry.sipcallwatcher.SubscribeDialog.SubscribeDialog.sendDialogFormingSubscribe(SubscribeDialog.java:173) >>> at >>> org.sipfoundry.sipcallwatcher.SubscribeDialog.WaitingForStartState.start(WaitingForStartState.java:14) >>> at >>> org.sipfoundry.sipcallwatcher.SubscribeDialog.SubscribeDialog.start(SubscribeDialog.java:54) >>> at >>> org.sipfoundry.sipcallwatcher.Subscriber$1.run(Subscriber.java:396) >>> at java.util.TimerThread.mainLoop(Timer.java:512) >>> at java.util.TimerThread.run(Timer.java:462) >>> Caused by: java.lang.NullPointerException >>> at >>> gov.nist.javax.sip.SipProviderImpl.getNewClientTransaction(SipProviderImpl.java:397) >>> at >>> org.sipfoundry.sipcallwatcher.Subscriber.sendDialogFormingSubscribe(Subscriber.java:291) >>> at >>> org.sipfoundry.sipcallwatcher.SubscribeDialog.SubscribeDialog.sendDialogFormingSubscribe(SubscribeDialog.java:168) >>> ... 5 more >>> >>> >> >> Hello Lazy, >> >> Yes - it is a timing issue that needs a fix in sipxopenfire. Does it >> affect the overall behavior? >> It should retry after that. >> >> >> Ranga > > Hello! > > Sorry! Bad diagnosis from me. > > Yes the udp listening point should be put back. Will ping Bob to do this > today. > > > Regards > > Ranga
After discussion with Bob, it is likely that this conclusion is in error as well. Please send logs. We had a timing issue on startup but that happens only once on startup and subsequently does not affect the functioning of sipxopenifre. SipXopenfire has been quite stable on our trial system. Thanks. Ranga > >> >> >>> >>> _______________________________________________ >>> 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/ >>> >> >> >> >> -- >> M. Ranganathan >> > > > > -- > M. Ranganathan > -- 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/
