Despite the item had been solved in FreeSwitch , a loop in sipXproxy makes it unresponsive, after a successful RTP or SRTP session has been initiated between the peer (Bria 3.1) and IVR (FreeSwitch). First opinion in sipx community is that contact uri's "transport" parameter -tls- makes FreeSwitch to send back a TLS contact for itself. What field , below in the outgoing message from sipxproxy to FS, do you thing may cause such problem? INVITE sip:IVR@192.168.170.181:15060;action=autoattendant;schedule_id=aa_2;locale=tr SIP/2.0 Record-Route: <sip:192.168.170.181:5060 ;lr;transport=tls;sipXecs-CallDest=AA;sipXecs-rs=%2Aauth%7E.%2Afrom%7EYWEwOTI2NzY%60.900_ntap%2Aid%7EMTY5MTItMA%60%60%2184f0de49a313ca584ee35862fa4d9252> Via: SIP/2.0/TCP 192.168.170.181;branch=z9hG4bK-XX-0012PZd_u6j6OnK7JAUPHDaqMg Via: SIP/2.0/TCP 192.168.170.181;branch=z9hG4bK-XX-000fH`lb3A2NDuC0IqsFmhxrpA~PAM7JZIC3rLwtUKol6bPig;id=16912-0 Via: SIP/2.0/TLS 192.168.169.181:61075 ;branch=z9hG4bK-d8754z-4164505f91604f72-1---d8754z-;rport=2081 Max-Forwards: 18 Contact: <sip:201@192.168.169.181:2081;transport=TLS;x-sipX-nonat> To: <sip:100@looneytoons.karelarge.com> From: "201"<sip:201@looneytoons.karelarge.com>;tag=aa092676 Call-Id: MmFmMjBiMzI3ZmNmODgwODlkZmEyMzhlODZmOTdlODI. Cseq: 2 INVITE Allow: INVITE, ACK, CANCEL, OPTIONS, BYE, REFER, NOTIFY, MESSAGE, SUBSCRIBE, INFO Content-Type: application/sdp Proxy-Authorization: Digest username="201",realm="looneytoons.karelarge.com ",nonce="9ee121f8be0527beae3a3455968376024e1af191",uri=" sip:100@looneytoons.karelarge.com ;transport=tls",response="03874cc04dacca0c0b92eff6b7323ae6",cnonce="c0dd307d23e99221815573ddd076c2b6",nc=00000001,qop=auth,algorithm=MD5 Supported: replaces User-Agent: Bria 3 release 3.1.2.1 stamp 58992 Content-Length: 464 Date: Mon, 11 Jul 2011 12:50:25 GMT X-Sipx-Handled: X192.168.170.181-192.168.170.181 v=0 o=- 12954862226704555 1 IN IP4 192.168.169.181 s=Counterpath Bria 3.1 c=IN IP4 192.168.169.181 t=0 0 a=ice-ufrag:3fdf30 a=ice-pwd:0b801a2479c7c55e1abca5f2c867a0ba m=audio 49188 RTP/AVP 107 0 8 18 101 a=rtpmap:107 BV32/16000 a=rtpmap:18 G729/8000 a=fmtp:18 annexb=yes a=rtpmap:101 telephone-event/8000 a=fmtp:101 0-15 a=sendrecv a=candidate:1 1 UDP 659136 192.168.169.181 49188 typ host a=candidate:1 2 UDP 659134 192.168.169.181 49189 typ host On Wed, Jun 1, 2011 at 3:49 PM, Steven Ayre <steveayre@gmail.com> wrote:
Please submit those as a Jira.
On 1 June 2011 12:52, barisyanar <barisyanar@gmail.com> wrote:
Problem still exists with the new head: FreeSWITCH version: 1.0.head (git-43a5af7 2011-05-30 12-27-01 -0400)
Siptrace:
<http://pastebin.com/qtZdYepW>Core trace output:
http://pastebin.freeswitch.org/16420
On Tue, May 31, 2011 at 5:10 PM, Peter Olsson < peter.olsson@visionutveckling.se> wrote:
That’s not latest git head. Try latest, if it still occurs, report a bug in Jira.
/Peter
*Från:* freeswitch-dev-bounces@lists.freeswitch.org [mailto: freeswitch-dev-bounces@lists.freeswitch.org] *För *barisyanar *Skickat:* den 31 maj 2011 14:10 *Till:* freeswitch-dev@lists.freeswitch.org *Ämne:* Re: [Freeswitch-dev] Sipx TLS connections make Freeswitch crash
sorry, i ran script at wrong place. here is the new link:
http://pastebin.freeswitch.org/16418
and the siptrace is here - after printing fs_cli closes:
On Tue, May 31, 2011 at 2:42 PM, Steven Ayre <steveayre@gmail.com> wrote:
Unfortunately that coredump doesn't show anything useful:
#0 0x0000003efcf1fc98 in ?? ()
#1 0x00007fbe0eb43913 in ?? ()
#2 0x00007fbdf8016628 in ?? ()
#3 0x0000000000000001 in ?? ()
#4 0x0000000000000003 in ?? ()
#5 0x00007fbe0eb4536b in ?? ()
#6 0x00007fbdf801b160 in ?? ()
#7 0x0000000000bdc8c0 in ?? ()
#8 0x0000000000bdc8c0 in ?? ()
#9 0x00007fbdfc0064d8 in ?? ()
#10 0x0000000000000000 in ?? ()
Usually you'd expect to see the name of the function call instead of ??, that shows it can't find those. Did you keep the FS git checkout after installing it, and did you compile it with the debugging symbols?
-Steve
On 31 May 2011 11:51, barisyanar <barisyanar@gmail.com> wrote:
Here's the pastebin link: http://pastebin.freeswitch.org/16413
After getting sofia siptrace I'll report the bug.
On Mon, May 30, 2011 at 5:34 PM, Steven Ayre <steveayre@gmail.com> wrote:
It might also be useful to see the debug logs prior to the crash, with siptrace enabled (sofia global siptrace on).
Since this is a bug, you should submit it as a bug report at http://jira.freeswitch.org/.
Include a description of the problem, and attach the debug log including the siptrace and how to reproduce it.
Unfortunately the coredump you attached is not much use to anyone without the local directory you compiled FS from. Please load the coredump in gdb (the gnu debugger) and collect the backtrace and also attach that. There are instructions of how to do so at http://wiki.freeswitch.org/wiki/Reporting_Bugs#Creating_A_Backtrace_With_gdb... the support-d/fscore_pb script in the git checkout will automate that process by posting it to our pastebin.
-Steve
On 30 May 2011 15:17, barisyanar <barisyanar@gmail.com> wrote:
http://www.ceng.metu.edu.tr/~e1348093/paylasim/core.18007.zip is the new core got from fs compiled after devel-bootstrap.sh.
Version is: FreeSWITCH version: 1.0.7 (git-e19096c 2011-03-25 17-14-07 -0400)
bt from new core is similar:
#0 __strchr_sse42 () at ../sysdeps/x86_64/multiarch/strchr.S:131
#1 0x00007fbe0eb43913 in sofia_glue_get_url_from_contact (buf=0x0,
to_dup=0 '\000') at sofia_glue.c:4825
#2 0x00007fbe0eb4536b in sofia_overcome_sip_uri_weakness (
session=0x7fbdf8016628, uri=<value optimized out>,
transport=SOFIA_TRANSPORT_TCP_TLS, uri_only=SWITCH_TRUE, params=0x0)
at sofia_glue.c:1293
#3 0x00007fbe0eb24e10 in sofia_handle_sip_i_invite (nua=0x7fbdf80100c0,
profile=0xbdc8c0, nh=0x7fbdfc009d40, sofia_private=<value optimized out>,
sip=<value optimized out>, tags=<value optimized out>) at sofia.c:6732
#4 0x00007fbe0eb4002a in sofia_event_callback (event=nua_i_invite,
status=100, phrase=0x7fbdfc00a9c0 "Trying", nua=0x7fbdf80100c0,
profile=0xbdc8c0, nh=0x7fbdfc009d40, sofia_private=0x0,
sip=0x7fbdfc0064d8, tags=0x7fbdfc00a9b0) at sofia.c:936
#5 0x00007fbe0ebb1de3 in nua_application_event (dummy=<value optimized out>,
sumsg=<value optimized out>, ee=0x7fbdfc00a988) at nua_stack.c:393
#6 0x00007fbe0ec0f804 in su_base_port_execute_msgs (queue=0x7fbdfc00d380)
at su_base_port.c:280
#7 0x00007fbe0ec0fd51 in su_base_port_step (self=0x7fbdf80010f0, tout=0)
at su_base_port.c:473
#8 0x00007fbe0eb39b8a in sofia_profile_thread_run (
thread=<value optimized out>, obj=0xbdc8c0) at sofia.c:1617
#9 0x0000003efd2068e0 in start_thread (arg=0x7fbe0f96b710)
On Sun, May 22, 2011 at 12:06 PM, Anton VG <anton.vazir@gmail.com> wrote:
for valuable backtrace, you should compile FS with no optimization (-O0), running devel-bootstrap.sh will do it for you.
2011/5/16 barisyanar <barisyanar@gmail.com>:
Hi all, I am using Freeswitch 1.0.7 with sipx release-4.4. Whenever I try to make an IVR call with TLS, Freeswitch crashes dumping the attached core file. The output bt command is: #0 __strchr_sse42 () at ../sysdeps/x86_64/multiarch/strchr.S:131 #1 0x00007f9c0b4373c3 in sofia_glue_get_url_from_contact (buf=0x0, to_dup=0 '\000') at sofia_glue.c:4943 #2 0x00007f9c0b438e1b in sofia_overcome_sip_uri_weakness ( session=0x7f9c04017108, uri=<value optimized out>, transport=SOFIA_TRANSPORT_TCP_TLS, uri_only=SWITCH_TRUE, params=0x0) at sofia_glue.c:1296 #3 0x00007f9c0b4182b0 in sofia_handle_sip_i_invite (nua=0x7f9c04008890, profile=0x148dad0, nh=0x7f9c00009ec0, sofia_private=<value optimized out>, sip=<value optimized out>, tags=<value optimized out>) at sofia.c:6793 #4 0x00007f9c0b433aca in sofia_event_callback (event=nua_i_invite, status=100, phrase=0x7f9c0000ab40 "Trying", nua=0x7f9c04008890, profile=0x148dad0, nh=0x7f9c00009ec0, sofia_private=0x0, sip=0x7f9c00006658, tags=0x7f9c0000ab30) at sofia.c:942 #5 0x00007f9c0b4a5f53 in nua_application_event (dummy=<value optimized out>, sumsg=<value optimized out>, ee=0x7f9c0000ab08) at nua_stack.c:393 #6 0x00007f9c0b503974 in su_base_port_execute_msgs (queue=0x0) at su_base_port.c:280 #7 0x00007f9c0b503ec1 in su_base_port_step (self=0x7f9c040010f0, tout=0) at su_base_port.c:473 #8 0x00007f9c0b42d4ea in sofia_profile_thread_run ( thread=<value optimized out>, obj=0x148dad0) at sofia.c:1623 #9 0x0000003efd2068e0 in start_thread (arg=0x7f9c18116710) ---Type <return> to continue, or q <return> to quit--- at pthread_create.c:297 #10 0x0000003efcee0c9d in clone () And sipx's freeswitch log prints the line: 2011-05-16 15:04:51.530426 [WARNING] switch_core.c:1120 Cannot locate domain deneme.deneme.karelarge.com, where deneme.deneme.karelarge.com is my fqdn. No problem occurs during TCP connection. Problem is possibly caused by sipx, but i'll be glad to hear FS community's ideas.
_______________________________________________ FreeSWITCH-dev mailing list FreeSWITCH-dev@lists.freeswitch.org http://lists.freeswitch.org/mailman/listinfo/freeswitch-dev UNSUBSCRIBE:http://lists.freeswitch.org/mailman/options/freeswitch-dev http://www.freeswitch.org
_______________________________________________ FreeSWITCH-dev mailing list FreeSWITCH-dev@lists.freeswitch.org http://lists.freeswitch.org/mailman/listinfo/freeswitch-dev UNSUBSCRIBE:http://lists.freeswitch.org/mailman/options/freeswitch-dev http://www.freeswitch.org
_______________________________________________ FreeSWITCH-dev mailing list FreeSWITCH-dev@lists.freeswitch.org http://lists.freeswitch.org/mailman/listinfo/freeswitch-dev UNSUBSCRIBE:http://lists.freeswitch.org/mailman/options/freeswitch-dev http://www.freeswitch.org
_______________________________________________ FreeSWITCH-dev mailing list FreeSWITCH-dev@lists.freeswitch.org http://lists.freeswitch.org/mailman/listinfo/freeswitch-dev UNSUBSCRIBE:http://lists.freeswitch.org/mailman/options/freeswitch-dev http://www.freeswitch.org
_______________________________________________ FreeSWITCH-dev mailing list FreeSWITCH-dev@lists.freeswitch.org http://lists.freeswitch.org/mailman/listinfo/freeswitch-dev UNSUBSCRIBE:http://lists.freeswitch.org/mailman/options/freeswitch-dev http://www.freeswitch.org
_______________________________________________ FreeSWITCH-dev mailing list FreeSWITCH-dev@lists.freeswitch.org http://lists.freeswitch.org/mailman/listinfo/freeswitch-dev UNSUBSCRIBE:http://lists.freeswitch.org/mailman/options/freeswitch-dev http://www.freeswitch.org
!DSPAM:4de4db0432761032611453!
_______________________________________________ FreeSWITCH-dev mailing list FreeSWITCH-dev@lists.freeswitch.org http://lists.freeswitch.org/mailman/listinfo/freeswitch-dev UNSUBSCRIBE:http://lists.freeswitch.org/mailman/options/freeswitch-dev http://www.freeswitch.org
_______________________________________________ FreeSWITCH-dev mailing list FreeSWITCH-dev@lists.freeswitch.org http://lists.freeswitch.org/mailman/listinfo/freeswitch-dev UNSUBSCRIBE:http://lists.freeswitch.org/mailman/options/freeswitch-dev http://www.freeswitch.org
_______________________________________________ FreeSWITCH-dev mailing list FreeSWITCH-dev@lists.freeswitch.org http://lists.freeswitch.org/mailman/listinfo/freeswitch-dev UNSUBSCRIBE:http://lists.freeswitch.org/mailman/options/freeswitch-dev http://www.freeswitch.org