On Tue, Mar 16, 2010 at 1:52 PM, Jeff Gilmore <j...@thegilmores.net> wrote: > On my server running 4.0.4 ISO, which as been stable for several months, I > suddenly could not call offsite (through my trunks on sipxBridge). Looking > in the sipxbridge log gave me this message: > > "2010-03-16T17:41:48.156000Z":10694:JAVA:WARNING:choicevoip.ev.ithaca.ny.us:PipelineThread-90:00000000:AccountManagerImpl:"Could > not match user part of inbound request URI" > "2010-03-16T17:41:48.161000Z":10695:JAVA:WARNING:choicevoip.ev.ithaca.ny.us:PipelineThread-90:00000000:DialogContext:"Setting > ITSP info to NULL" > "2010-03-16T17:41:48.162000Z":10696:JAVA:WARNING:choicevoip.ev.ithaca.ny.us:PipelineThread-90:00000000:AccountManagerImpl:"Could > not match user part of inbound request URI" > "2010-03-16T17:41:48.162000Z":10697:JAVA:WARNING:choicevoip.ev.ithaca.ny.us:PipelineThread-90:00000000:AccountManagerImpl:"Could > not match user part of inbound request URI" > "2010-03-16T17:41:48.164000Z":10698:JAVA:WARNING:choicevoip.ev.ithaca.ny.us:PipelineThread-90:00000000:DialogContext:"Setting > ITSP info to NULL" > "2010-03-16T17:41:48.166000Z":10699:JAVA:ERR:choicevoip.ev.ithaca.ny.us:PipelineThread-90:00000000:BackToBackUserAgent:"Caught > exception " > org.sipfoundry.sipxbridge.symmitron.SymmitronException: Error in processing > request Ports not available > at > org.sipfoundry.sipxbridge.symmitron.SymmitronClient.createEvenSym(SymmitronClient.java:183) > at > org.sipfoundry.sipxbridge.BackToBackUserAgent.createRtpSession(BackToBackUserAgent.java:318) > at > org.sipfoundry.sipxbridge.BackToBackUserAgent.sendInviteToItsp(BackToBackUserAgent.java:1598) > at > org.sipfoundry.sipxbridge.CallControlManager.processInvite(CallControlManager.java:579) > at > org.sipfoundry.sipxbridge.CallControlManager.processRequest(CallControlManager.java:2760) > at > org.sipfoundry.sipxbridge.SipListenerImpl.processRequest(SipListenerImpl.java:326) > at gov.nist.javax.sip.EventScanner.deliverEvent(EventScanner.java:223) > at > gov.nist.javax.sip.SipProviderImpl.handleEvent(SipProviderImpl.java:189) > at > gov.nist.javax.sip.DialogFilter.processRequest(DialogFilter.java:1056) > at > gov.nist.javax.sip.stack.SIPServerTransaction.processRequest(SIPServerTransaction.java:809) > at > gov.nist.javax.sip.stack.TCPMessageChannel.processMessage(TCPMessageChannel.java:530) > at > gov.nist.javax.sip.parser.PipelinedMsgParser.run(PipelinedMsgParser.java:342) > at java.lang.Thread.run(Thread.java:619) > > No number I tried would work, and all gave the same results. I was able to > fix it by restarting sip trunking, media relay, proxy and registrar. > > Has anyone seen this before? Is there anything I can do to avoid it? I had > made no changes to the system config today, although I did plug in 8 new > users.
You may have hit on a port that was being used by some other process. What does sipxrelay.log look like? Ranga > > Thanks, > > Jeff > _______________________________________________ > sipx-users mailing list sipx-users@list.sipfoundry.org > 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/ > -- M. Ranganathan _______________________________________________ sipx-users mailing list sipx-users@list.sipfoundry.org 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/
