[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [osip-dev] osip uri segfault
From: |
Kuklin István |
Subject: |
Re: [osip-dev] osip uri segfault |
Date: |
Fri, 05 Jun 2015 15:01:56 +0200 |
Hi Aymeric,
okay, now I don't have segmentation faults but it still says 488. I'll
try to figure out this problem on my own as I know the exact
configuration.
Thank you!
István
2015. 06. 5, péntek keltezéssel 09.12-kor Aymeric Moizard ezt írta:
> Hi Istvan,
>
>
> It's possible that the 488 is not related to the "transport=tls" not
> being there... but I don't know you exact setup, objective, and
> neither
> asterisk code, so I can't tell...
>
>
> In order to add the transport=tls option, you need to provide already
> allocated string:
>
>
> osip_uri_param_add((&(invite->req_uri->url_params),
> osip_strdup("transport"), osip_strdup("tls"))
>
>
>
> Then, when deallocating the message, you won't get a free error!
>
>
> Regards
> Aymeric
>
>
>
> 2015-06-04 20:18 GMT+02:00 Kuklin István <address@hidden>:
> Hi Aymeric,
>
> Could you tell me how can I add a parameter to an SIP header
> of a call
> in order to send a TLS request? Here is the full scenario:
>
> I'd like to make calls with TLS signaling but for some reason
> the
> Asterisk server sends an 488 Not Acceptable Here response for
> the call
> (and the other phone doesn't ring), although the configuration
> on the
> server's side must be okay as this account can make TLS
> encrypted calls
> using other SIP agents.
>
> I noticed that I don't have the ;transport=tls parameter in my
> request
> header in contrast to other agents which use it.
>
> My agent:
> <--- SIP read from TLS:84.236.29.199:35428 --->
> INVITE sip:address@hidden SIP/2.0
> Via: SIP/2.0/TLS
> 192.168.0.12:5061;rport;branch=z9hG4bK1974510616
> ...
> Zoiper:
> <--- SIP read from TLS:84.236.29.199:33209 --->
> INVITE sip:address@hidden;transport=TLS SIP/2.0
> Via: SIP/2.0/TLS
>
> 84.236.29.199:33209;branch=z9hG4bK-d8754z-002ceb6591b4c029-1---d8754z-;rport
>
> As you see in the picture I attached I tried to add the
> parameter but if
> the two marked lines marked with FIXME are compiled (not
> commented out)
> both then my agent causes segmentation fault. Here is the gdb
> output:
>
> Program received signal SIGSEGV, Segmentation fault.
> [Switching to Thread 0x7fffdf287700 (LWP 6496)]
> 0x00007ffff65c6e2c in __GI___libc_free (mem=0x406181) at
> malloc.c:2945
> 2945 malloc.c: Nincs ilyen fájl vagy könyvtár. <--- in
> Hungarian:
> there's no such file or directory.
> (gdb) bt
> #0 0x00007ffff65c6e2c in __GI___libc_free (mem=0x406181) at
> malloc.c:2945
> #1 0x00007ffff6d8d671 in osip_uri_param_free ()
> from /usr/lib/x86_64-linux-gnu/libosipparser2.so.10
> #2 0x00007ffff6d8d80b in osip_uri_param_freelist ()
> from /usr/lib/x86_64-linux-gnu/libosipparser2.so.10
> #3 0x00007ffff6d8d302 in osip_uri_free ()
> from /usr/lib/x86_64-linux-gnu/libosipparser2.so.10
> #4 0x00007ffff6d9531a in osip_message_free ()
> from /usr/lib/x86_64-linux-gnu/libosipparser2.so.10
> #5 0x00007ffff217ffac in osip_transaction_free2 ()
> from /usr/lib/x86_64-linux-gnu/libosip2.so.10
> #6 0x00007ffff217fde7 in osip_transaction_free ()
> from /usr/lib/x86_64-linux-gnu/libosip2.so.10
> #7 0x00007ffff6b4fc28 in _eXosip_release_terminated_calls
> (excontext=0x9ef000)
> at udp.c:2008
> #8 0x00007ffff6b3a16d in eXosip_execute (excontext=0x9ef000)
> at
> eXconf.c:809
> #9 0x00007ffff6b3b1dc in _eXosip_thread (arg=0x9ef000) at
> eXconf.c:1090
> #10 0x00007ffff6911182 in start_thread (arg=0x7fffdf287700)
> at pthread_create.c:312
> #11 0x00007ffff663e47d in clone ()
> at ../sysdeps/unix/sysv/linux/x86_64/clone.S:111
> (gdb)
>
> Why am I not able to add that parameter? I couldn't figure it
> out.
>
> Thank you for your help!
> Regards,
> István
>
>
> _______________________________________________
> osip-dev mailing list
> address@hidden
> https://lists.gnu.org/mailman/listinfo/osip-dev
>
>
>
>
>
> --
> Antisip - http://www.antisip.com
>
smime.p7s
Description: S/MIME cryptographic signature