> On Tue, Apr 6, 2010 at 4:49 PM, JOLY, ROBERT (ROBERT) 
> <[email protected]> wrote:
> 
> 
>       Two things:
>       
>       #1 - we need the sipxopenfire log that covers that time 
> when the sipXopenfire process started.   The log we have is a 
> repetition of the same error over and over again but does not 
> contain the events that led up to that periodic error.
>       
> 
> 
> i will send you this log, but it's not very exciting,  Error 
> starts right away.
>  
> 
>       #2 - If your system is still in this error state, could 
> you post the output of 'netstat -nap | grep 5064'.
>       
> 
> tcp        0      0 ::ffff:192.168.1.125:5064   :::*          
>               LISTEN      10721/java
> 
>  
> 
> 
>       One possibility is that the sipXopenfire process was 
> not able to bind to TCP port 5064 because another process had 
> it.  If that were to happen, this condition could lead to the 
> errors you are seeing. Obviously, if that turns out to be the 
> case, we need to improve our handling of that error condition.
>       
> 
> 
> I tracked this down into FindSipServer.findServer(SipURI uri) 
> where this subscribe message is returning a ProxyHop object 
> that has UDP as transport which i think is wrong based on the 
> message.  I don't have the line the misinterpretation happens 
> on because i would have to rebuild w/debugging turned on.
> 
> 
> SUBSCRIBE sip:[email protected] SIP/2.0
> 
> Call-ID: [email protected]
> CSeq: 1 SUBSCRIBE
> From: "Call Watcher" 
> <sip:[email protected]>;tag=6760726998052965323
> 
> To: <sip:[email protected]>
> Via: SIP/2.0/TCP 192.168.1.125:5064
> Max-Forwards: 70
> Contact: "~~id~xmpprlsclient" 
> <sip:[email protected]:5064;transport=tcp>
> 
> Expires: 3600
> Supported: eventlist
> Event: dialog
> Accept: 
> application/dialog-info+xml,application/rlmi+xml,multipart/related
> Content-Length: 0

I just committed something.  Could you please try again with revision 18532 or 
better?  Thanks
_______________________________________________
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/

Reply via email to