On Wed, 2009-07-01 at 19:45 +0100, Carl Anthony wrote: > Ok, I finally got myself enough time to try and resolve this problem, > and have made some progress. I have attached the ngrep output, but > from my understanding of it it seems the topex box is not handling the > SIP refer (required to transfer a call) being sent to it from sipx > server .. although the topex box accepted the refer, it then turns > around and was unable to complete it. > > Well, thats my understanding. Would appreciate a second opinion.
There's no call in that output that is the result of the REFER, but there is a notice that such a call was received somewhere. There's no way to tell from what you sent whether the call was omitted from the trace or was sent somewhere other than the sipXecs. It's much easier to see the call flows if you use the sipXecs tools for tracing rather than ngrep. See: http://sipx-wiki.calivia.com/index.php/Display_SIP_message_flow_using_Sipviewer#Getting_SIP_Messages_to_display when you get the trace data, take a look at it using sipviewer and/or post the trace with a description of your configuration (identify components by IP address), what you were doing, and which call in the trace you're talking about (by call-id or frame number in the trace, preferably). > One secondary effect I have seen is that calls that have been affected > this way, remain hanging for hours and days on the sipx side (when you > list active calls via the web GUI). Its like sipx has actually > contacted the destination extension number (albeit without ringing the > extension) and is waiting for the topex side for confirmation before > it would hand-off the call to the destination extension. If at this > stage the topex side fails (as seems to be happening), sipx seems to > have no way of stopping the transferred call from being registered in > the system. I am just speculating here based on my observations, and > relative inexperience of sipx. There are some conditions under which calls that are not completed normally will end up appearing in this state - most of those are fixed in the 4.0.1 release. I suggest that you upgrade. > BTW, is their a CLI way I can list active calls in sipx ? Also, any > CLI commands to terminate active calls ? Relying only on the GUI can > be cumbersoome and inconvenient in some situations. No. _______________________________________________ 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/
