Hello, I'm not sure that this is the right mailing list for this question, but I'll ask anyway :) Are there any known issues with sip over tcp? In some scenarios, freeswitch doesn't behave in a standard way. Attached a picture with flow graph (from wireshark), where you can see such a problematic behavior. When user1 invites user2 (through the server), the server routes the invite message to user2, but when user2 responds, the server doesn't send an ack to this user! Looking forward to your reply, Thanks, Emil.
You failed to frame this misbehavior with any useful info. What REV are you running... what scenario, what mode of operation ie proxy media bypass media ... What I would like to see are debug logs on level 8 (press F8), I have yet to see it misbehave unless something in the packets causes it to misbehave and a ladder graph won't give us enough info to go on. /b On Apr 21, 2010, at 2:05 PM, Emil Berg wrote:
Hello,
I'm not sure that this is the right mailing list for this question, but I'll ask anyway :) Are there any known issues with sip over tcp?
In some scenarios, freeswitch doesn't behave in a standard way. Attached a picture with flow graph (from wireshark), where you can see such a problematic behavior. When user1 invites user2 (through the server), the server routes the invite message to user2, but when user2 responds, the server doesn't send an ack to this user!
Looking forward to your reply, Thanks,
Emil.
are you running that on the FS box ? run the inline sip console trace to confirm it's not sending to somewhere else based on a changed contact addr. On Wed, Apr 21, 2010 at 2:05 PM, Emil Berg <emilbergg@gmail.com> wrote:
Hello,
I'm not sure that this is the right mailing list for this question, but I'll ask anyway :) Are there any known issues with sip over tcp?
In some scenarios, freeswitch doesn't behave in a standard way. Attached a picture with flow graph (from wireshark), where you can see such a problematic behavior. When user1 invites user2 (through the server), the server routes the invite message to user2, but when user2 responds, the server doesn't send an ack to this user!
Looking forward to your reply, Thanks,
Emil.
_______________________________________________ FreeSWITCH-users mailing list FreeSWITCH-users@lists.freeswitch.org http://lists.freeswitch.org/mailman/listinfo/freeswitch-users UNSUBSCRIBE:http://lists.freeswitch.org/mailman/options/freeswitch-users http://www.freeswitch.org
-- Anthony Minessale II FreeSWITCH http://www.freeswitch.org/ ClueCon http://www.cluecon.com/ Twitter: http://twitter.com/FreeSWITCH_wire AIM: anthm MSN:anthony_minessale@hotmail.com <MSN%3Aanthony_minessale@hotmail.com> GTALK/JABBER/PAYPAL:anthony.minessale@gmail.com<PAYPAL%3Aanthony.minessale@gmail.com> IRC: irc.freenode.net #freeswitch FreeSWITCH Developer Conference sip:888@conference.freeswitch.org <sip%3A888@conference.freeswitch.org> googletalk:conf+888@conference.freeswitch.org<googletalk%3Aconf%2B888@conference.freeswitch.org> pstn:+19193869900
Even if i have not done a so in depth analysis, i have several random and not reproduceable behaviour (but continuous) using FS with SIP/TLS (i only use it over SIP/TLS) that seems to have a representation of the issue equal to this one reported by Emil. Fabio On 21/04/10 21.05, Emil Berg wrote:
Hello,
I'm not sure that this is the right mailing list for this question, but I'll ask anyway :) Are there any known issues with sip over tcp?
Well it saddens me that these issues are just over looked and not reported. When reporting issues with FreeSWITCH please follow the bug reporting guidelines on the wiki. Sitting on bugs isn't going to get them fixed. Not collecting the right info and reporting them properly won't either. /b On Apr 22, 2010, at 1:21 AM, Fabio Pietrosanti (naif) wrote:
Even if i have not done a so in depth analysis, i have several random and not reproduceable behaviour (but continuous) using FS with SIP/TLS (i only use it over SIP/TLS) that seems to have a representation of the issue equal to this one reported by Emil.
Fabio
Are you arrogantly refusing to collect the actual sip traces but still feel the need to report an issue? That is called FUD and we do not tolerate it here. Either hold your tongues or collect the info. Do not just use our mailing list to say you have "random and not reproducible problems" It does nobody any good. We have now wasted 3 email exchanges simply asking for the information. If you were able to produce the ladder diagram surely you could have done what I asked and did a pcap from the FS box and a console trace. Maybe you should learn more about network topology before you send us any more email. On Thu, Apr 22, 2010 at 1:21 AM, Fabio Pietrosanti (naif) < lists@infosecurity.ch> wrote:
Even if i have not done a so in depth analysis, i have several random and not reproduceable behaviour (but continuous) using FS with SIP/TLS (i only use it over SIP/TLS) that seems to have a representation of the issue equal to this one reported by Emil.
Fabio
On 21/04/10 21.05, Emil Berg wrote:
Hello,
I'm not sure that this is the right mailing list for this question, but I'll ask anyway :) Are there any known issues with sip over tcp?
_______________________________________________ FreeSWITCH-users mailing list FreeSWITCH-users@lists.freeswitch.org http://lists.freeswitch.org/mailman/listinfo/freeswitch-users UNSUBSCRIBE:http://lists.freeswitch.org/mailman/options/freeswitch-users http://www.freeswitch.org
-- Anthony Minessale II FreeSWITCH http://www.freeswitch.org/ ClueCon http://www.cluecon.com/ Twitter: http://twitter.com/FreeSWITCH_wire AIM: anthm MSN:anthony_minessale@hotmail.com <MSN%3Aanthony_minessale@hotmail.com> GTALK/JABBER/PAYPAL:anthony.minessale@gmail.com<PAYPAL%3Aanthony.minessale@gmail.com> IRC: irc.freenode.net #freeswitch FreeSWITCH Developer Conference sip:888@conference.freeswitch.org <sip%3A888@conference.freeswitch.org> googletalk:conf+888@conference.freeswitch.org<googletalk%3Aconf%2B888@conference.freeswitch.org> pstn:+19193869900
Hi Anthony, i really apologise for not being still able to provide the trace, i am under product release and this is an issue of the many to be managed and it's in my company backlog. I did not wanted to make FUD or being arrogant, really. It's just that i read an issue in the mailing list similar to what i experience. We still not analyzed deeply and you know that a non deterministic bug it's something quite difficult to be traced down, require a continuous testing environment to catch the issue while collecting a lot of logs :( Will do it, just is in a schedule of activities. Fabio On 22/04/10 17.33, Anthony Minessale wrote:
Are you arrogantly refusing to collect the actual sip traces but still feel the need to report an issue? That is called FUD and we do not tolerate it here. Either hold your tongues or collect the info. Do not just use our mailing list to say you have "random and not reproducible problems" It does nobody any good. We have now wasted 3 email exchanges simply asking for the information. If you were able to produce the ladder diagram surely you could have done what I asked and did a pcap from the FS box and a console trace. Maybe you should learn more about network topology before you send us any more email.
Hello everybody, Sorry for not answering so long. There were holidays here and only now I got back to office. I'm a beginner and I just installed freeswitch and started playing with it and see if it works with my client. This is why I didn't provide any info. I just wanted to know if this is a known issue. If someone could tell me please how can I produce these logs, I will attach them. Thank you, Emil. On Thu, Apr 22, 2010 at 6:45 PM, Fabio Pietrosanti (naif) < lists@infosecurity.ch> wrote:
Hi Anthony, i really apologise for not being still able to provide the trace, i am under product release and this is an issue of the many to be managed and it's in my company backlog.
I did not wanted to make FUD or being arrogant, really.
It's just that i read an issue in the mailing list similar to what i experience. We still not analyzed deeply and you know that a non deterministic bug it's something quite difficult to be traced down, require a continuous testing environment to catch the issue while collecting a lot of logs :(
Will do it, just is in a schedule of activities.
Fabio On 22/04/10 17.33, Anthony Minessale wrote:
Are you arrogantly refusing to collect the actual sip traces but still feel the need to report an issue? That is called FUD and we do not tolerate it here. Either hold your tongues or collect the info. Do not just use our mailing list to say you have "random and not reproducible problems" It does nobody any good. We have now wasted 3 email exchanges simply asking for the information. If you were able to produce the ladder diagram surely you could have done what I asked and did a pcap from the FS box and a console trace. Maybe you should learn more about network topology before you send us any more email.
_______________________________________________ FreeSWITCH-users mailing list FreeSWITCH-users@lists.freeswitch.org http://lists.freeswitch.org/mailman/listinfo/freeswitch-users UNSUBSCRIBE:http://lists.freeswitch.org/mailman/options/freeswitch-users http://www.freeswitch.org
Hi Emil, There's a page on the wiki which describes how to report bugs and how to collect the relevant information. http://wiki.freeswitch.org/wiki/Reporting_Bugs -Steve On 25 April 2010 07:50, Emil Berg <emilbergg@gmail.com> wrote:
Hello everybody,
Sorry for not answering so long. There were holidays here and only now I got back to office. I'm a beginner and I just installed freeswitch and started playing with it and see if it works with my client. This is why I didn't provide any info. I just wanted to know if this is a known issue. If someone could tell me please how can I produce these logs, I will attach them.
Thank you, Emil.
On Thu, Apr 22, 2010 at 6:45 PM, Fabio Pietrosanti (naif) <lists@infosecurity.ch> wrote:
Hi Anthony, i really apologise for not being still able to provide the trace, i am under product release and this is an issue of the many to be managed and it's in my company backlog.
I did not wanted to make FUD or being arrogant, really.
It's just that i read an issue in the mailing list similar to what i experience. We still not analyzed deeply and you know that a non deterministic bug it's something quite difficult to be traced down, require a continuous testing environment to catch the issue while collecting a lot of logs :(
Will do it, just is in a schedule of activities.
Fabio On 22/04/10 17.33, Anthony Minessale wrote:
Are you arrogantly refusing to collect the actual sip traces but still feel the need to report an issue? That is called FUD and we do not tolerate it here. Either hold your tongues or collect the info. Do not just use our mailing list to say you have "random and not reproducible problems" It does nobody any good. We have now wasted 3 email exchanges simply asking for the information. If you were able to produce the ladder diagram surely you could have done what I asked and did a pcap from the FS box and a console trace. Maybe you should learn more about network topology before you send us any more email.
_______________________________________________ FreeSWITCH-users mailing list FreeSWITCH-users@lists.freeswitch.org http://lists.freeswitch.org/mailman/listinfo/freeswitch-users UNSUBSCRIBE:http://lists.freeswitch.org/mailman/options/freeswitch-users http://www.freeswitch.org
_______________________________________________ FreeSWITCH-users mailing list FreeSWITCH-users@lists.freeswitch.org http://lists.freeswitch.org/mailman/listinfo/freeswitch-users UNSUBSCRIBE:http://lists.freeswitch.org/mailman/options/freeswitch-users http://www.freeswitch.org
participants (5)
-
Anthony Minessale
-
Brian West
-
Emil Berg
-
Fabio Pietrosanti (naif)
-
Steven Ayre