From: SourceForge.net <no...@so...> - 2012-06-03 16:14:07
|
Bugs item #3530648, was opened at 2012-05-29 13:01 Message generated for change (Comment added) made by madzin You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=1046486&aid=3530648&group_id=219467 Please note that this message will contain a full copy of the comment thread, including the initial issue submission, for this request, not just the latest update. Category: Visio Interface Group: None Status: Open Resolution: None Priority: 5 Private: No Submitted By: Gilberto Tavan (pomate) Assigned to: Matus Madzin (madzin) Summary: Error in renderind disconnected MSC Initial Comment: I've noticed SCstudio has a bug in import function, when rendering of disconnected MSC. When a new instance of a node pops up, the messages are placed at the beginning of the .vsd file, they should be always added after the last message. Having multiple interfaces (IPaddresses) is quite common in SIP applications. In the attachment an example of SIP Call Flow, where the rendering is incorrect. ---------------------------------------------------------------------- Comment By: Matus Madzin (madzin) Date: 2012-06-03 09:14 Message: Hi, Firstly I would like to thank Mr. Tavan for good report. Now, I replay to xrehak's comment. Actually, I can confirm that it's basic feature of MSC, but I don't like any of xrehak's suggestions. If I understand the problem correctly, Mr. Tavan wants a linearization over all messages in an MSC diagram. To reach this functionality by clear solution, I suggest to set time stamp of each message from pcap as an absolute time constraint and create new feature of SCStudio to linearize messages in MSC diagram if it's possible (when the diagram is created from pcap file, it should be always possible). I think, it would be correct to assign this ticket to feature request category. Matus ---------------------------------------------------------------------- Comment By: Vojtech Rehak (xrehak) Date: 2012-05-29 23:18 Message: Actually, it is a basic feature of MSC that disconnected events on different instances can be placed arbitrarily. I suggest two solutions: - consider the interfaces of a single computer as standalone components and add some messages between these interfaces representing internal communication proceed within the computer; hence, the relevant messages will not be disconnected any more. (Ok. this should be hardly achieved from pcap. ) - consider the multiple interfaces as nicknames of the same computer and make a single instance representing all of them together (Matus, is there any possibility to specify this by parameters of pcap2z120.py?) ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=1046486&aid=3530648&group_id=219467 |