When compiling kamailio v3.3, I am getting this error from sipcapture
and siptrace. I am compiling on solaris 10, 64bit Sun server with gnu
tools.
CC (gcc) [M sipcapture.so] sipcapture.o
In file included from sipcapture.c:76:0:
sipcapture.h:48:4: error: unknown type name 'u_int32_t'
sipcapture.h:49:4: error: unknown type name 'u_int32_t'
gmake[1]: *** [sipcapture.o] Error 1
In file included from siptrace.c:54:0:
../../modules/sipcapture/sipcapture.h:48:4: error: unknown type name
'u_int32_t'
../../modules/sipcapture/sipcapture.h:49:4: error: unknown type name
'u_int32_t'
gmake[1]: *** [siptrace.o] Error 1
Thanks
Nathaniel
Hello Daniel,
Sorry for the delay!
I will get around to testing with the latest master branch sometime over the next couple of days and will report back here.
Many thanks,
Charles
Daniel-Constantin Mierla <miconda(a)gmail.com> wrote:
Hello,
can you try with latest master branch -- it should be fixed by:
http://git.sip-router.org/cgi-bin/gitweb.cgi/sip-router/?a=commit;h=1d89d7b…
Cheers,
Daniel
On 5/29/12 5:52 PM, Daniel-Constantin Mierla wrote:
Hello,
finally had a chance to look over it. I guess it is some race, resulting in a memory space being overwritten. The 200ok for publish with ringing state is processed more or less at the time when 200ok for invite comes and dialog changes state.
Can you re-compile with MEMDBG=1 (edit the Makefile.defs or give it in the command line parameter) and try again? Maybe the memory manager can catch the fault operation and provide more details.
Cheers,
Daniel
On 5/17/12 6:58 PM, Charles Chance wrote:
Hi Daniel,
I have sent the messages over to you.
I look forward to hear what you can find.
Best,
Charles
From: Daniel-Constantin Mierla [mailto:miconda@gmail.com]
Sent: 17 May 2012 15:06
To: Charles Chance
Cc: 'SIP Router - Kamailio (OpenSER) and SIP Express Router (SER) -Users Mailing List'
Subject: Re: FW: (Devel) Segmentation fault using pua_dialoginfo
Hello,
the content of ps->param is pretty much all invalid. So looks like a callback on a freed/invalid parameter, could be a double-callback execution.
Set debug=3 and send all the messages for such case -- it might be quite a lot of them, so send them to my email address, the mailing list has a limit of message size.
Cheers,
Daniel
On 5/17/12 2:13 PM, Charles Chance wrote:
Hi,
Requested output as follows:
(gdb) frame 1
#1 publ_cback_func (t=0xb3dc8e38, type=1024, ps=0xbfcdd5d8)
at send_publish.c:246
246 hash_code= core_hash(hentity->pres_uri, NULL, HASH_SIZE);
(gdb) p *ps
$2 = {req = 0x0, rpl = 0xb7c30340, param = 0xb3dc3ff4, code = 412, flags = 0,
branch = 0, t_rbuf = 0x0, dst = 0x0, send_buf = {s = 0x0, len = 0}}
(gdb) p *(ua_pres_t*)(*ps->param)
$3 = {id = {s = 0x20455942 <Address 0x20455942 out of bounds>,
len = 980445555}, pres_uri = 0x40323531, event = 875444279,
expires = 875703856, desired_expires = 858861105, flag = 808794676,
db_flag = 1394618421, cb_param = 0x322f5049, next = 0xa0d302e,
ua_flag = 979462486, etag = {
s = 0x50495320 <Address 0x50495320 out of bounds>, len = 808333871},
tuple_id = {s = 0x5044552f <Address 0x5044552f out of bounds>,
len = 775436064}, body = 0x322e3034, content_type = {
s = 0x312e3134 <Address 0x312e3134 out of bounds>, len = 1648047155},
watcher_uri = 0x636e6172, call_id = {
s = 0x397a3d68 <Address 0x397a3d68 out of bounds>, len = 1647593320},
to_tag = {s = 0x3435634b <Address 0x3435634b out of bounds>,
len = 842149473}, from_tag = {
s = 0x63306461 <Address 0x63306461 out of bounds>, len = 808334648},
cseq = 1767246349, version = 1394621025, outbound_proxy = 0x322f5049,
extra_headers = 0x552f302e, record_route = {
s = 0x31205044 <Address 0x31205044 out of bounds>, len = 825111097},
remote_contact = {s = 0x312e3836 <Address 0x312e3836 out of bounds>,
len = 976498224}, contact = {
s = 0x36373135 <Address 0x36373135 out of bounds>, len = 1701985073}}
Yes, it is a test server so very happy to arrange for remote access if required. In the meantime, I will do a little more digging to try to find out why entity is null.
Cheers,
Charles
--
Daniel-Constantin Mierla - http://www.asipto.comhttp://twitter.com/#!/miconda - http://www.linkedin.com/in/miconda
No virus found in this message.
Checked by AVG - www.avg.com
Version: 2012.0.2176 / Virus Database: 2425/5004 - Release Date: 05/16/12
--
Daniel-Constantin Mierla - http://www.asipto.comhttp://twitter.com/#!/miconda - http://www.linkedin.com/in/miconda
Kamailio Advanced Training, Seattle, USA, Sep 23-26, 2012 - http://asipto.com/u/katu
--
Daniel-Constantin Mierla - http://www.asipto.comhttp://twitter.com/#!/miconda - http://www.linkedin.com/in/miconda
Kamailio Advanced Training, Seattle, USA, Sep 23-26, 2012 - http://asipto.com/u/katu
Kamailio Practical Workshop, Netherlands, Sep 10-12, 2012 - http://asipto.com/u/kpw
Hi all,
I'm facing a problem with multiple contact in 'location' table with the same
'username'.
The idea is to rewrite R-URI with 1 contact and if there is no answer or SIP
5xx, try with the second.
Is that make sense? I use SER0.9.9.
Regards,
Igor.
Hey guys,
I'm trying to plan a deployment for a couple thousands of users. As we are
facing now some issues for scaling, I'd like to make a modular architecture
in order to add a server when needed.
I was thinking about N+1 Kamailio Proxies to Register customers and handle
the border of the network, 1+1 Redirect servers so internal Network
Elements can "find" the right Proxy to terminate a call. Customers would
use DNS SRV to decide which Proxy to send a REGISTER and then send INVITES
to that same proxy.
As we have a private core network addressing, I'm thinking I'll have an
Asterisk farm in order to perform media handling.
Do you have some recommendation or guidelines for this deployment?
Thanks!
Uriel
Hi all, I have a project for the 3G related, AMR and AMR-WB support.
I'm using the client develop suite from the PortSIP(http://www.portsip.com),
as their said
support the AMR, AMR-WB with RFC4867.
Now I have to setup a SIP server/SIP PBX in our Lab for test, does the SIPX
support these codecs and RFC4867 ?
Also, any other Server/PBX which support AMR, AMR-WB recommended are
welcome.
Best regards,
HI
I am testing the following case in the kamailio 3.3 presence server,
all are in 192.168.122.0 network
101 (bria, ip:.224) ----- kamailio ps( ip:.32) --- 103 (
jitsi, ip:.1)
on 101 I added 103 in the contact list, 101 <-> 103 can see each
other,
Then on 101, I deleted 103, thus on 103, 101 became grey, so far so
good.
Now I tried to add 103 back to contact list, on 101 I can see 103's
status (online),
but on jitsi 103, I can not see 101's status. ( grey)
The watcher table showed that status terminated.
+----+------------------------+------------------+----------------+----------+--------+------------+---------------+
| id | presentity_uri | watcher_username | watcher_domain |
event | status | reason | inserted_time |
+----+------------------------+------------------+----------------+----------+--------+------------+---------------+
| 1 | sip:103@192.168.122.32 | 101 | 192.168.122.32 |
presence | 1 | | 1339752028 |
| 2 | sip:101@192.168.122.32 | 103 | 192.168.122.32 |
presence | 3 | terminated | 1339752031 |
+----+------------------------+------------------+----------------+----------+--------+------------+---------------+
I guess it should be status=1 in this case, but somehow kamailio
seems does not update the table?
I have a complete packet-trace file if needed.
thanks.
min
Hi
I'm using drouting module and seems that it only allows digit-only
prefixes. Also all the number of digits to be stripped ('strip' defined
in dr_gateways) must be all digits too. When I used non-digits in these,
Kamailio crashed.
Is there any way in drouting module that I can use prefixes with
alphabet and dots, e.g. "gateway1."? Thanks very much!
Yufei
--
Yufei Tao
Red Embedded
This E-mail and any attachments hereto are strictly confidential and intended solely for the addressee. If you are not the intended addressee please notify the sender by return and delete the message.
You must not disclose, forward or copy this E-mail or attachments to any third party without the prior consent of the sender.
Red Embedded Design, Company Number 06688253 Registered in England: The Waterfront, Salts Mill Rd, Saltaire, BD17 7EZ
Hello,
finally had a chance to look over it. I guess it is some race, resulting
in a memory space being overwritten. The 200ok for publish with ringing
state is processed more or less at the time when 200ok for invite comes
and dialog changes state.
Can you re-compile with MEMDBG=1 (edit the Makefile.defs or give it in
the command line parameter) and try again? Maybe the memory manager can
catch the fault operation and provide more details.
Cheers,
Daniel
On 5/17/12 6:58 PM, Charles Chance wrote:
>
> Hi Daniel,
>
> I have sent the messages over to you.
>
> I look forward to hear what you can find.
>
> Best,
>
> Charles
>
> ------------------------------------------------------------------------
>
> *From:*Daniel-Constantin Mierla [mailto:miconda@gmail.com]
> *Sent:* 17 May 2012 15:06
> *To:* Charles Chance
> *Cc:* 'SIP Router - Kamailio (OpenSER) and SIP Express Router (SER)
> -Users Mailing List'
> *Subject:* Re: FW: (Devel) Segmentation fault using pua_dialoginfo
>
> Hello,
>
> the content of ps->param is pretty much all invalid. So looks like a
> callback on a freed/invalid parameter, could be a double-callback
> execution.
>
> Set debug=3 and send all the messages for such case -- it might be
> quite a lot of them, so send them to my email address, the mailing
> list has a limit of message size.
>
> Cheers,
> Daniel
>
> On 5/17/12 2:13 PM, Charles Chance wrote:
>
>> Hi,
>>
>> Requested output as follows:
>>
>> (gdb) frame 1
>>
>> #1 publ_cback_func (t=0xb3dc8e38, type=1024, ps=0xbfcdd5d8)
>>
>> at send_publish.c:246
>>
>> 246 hash_code= core_hash(hentity->pres_uri, NULL, HASH_SIZE);
>>
>> (gdb) p *ps
>>
>> $2 = {req = 0x0, rpl = 0xb7c30340, param = 0xb3dc3ff4, code = 412,
>> flags = 0,
>>
>> branch = 0, t_rbuf = 0x0, dst = 0x0, send_buf = {s = 0x0, len = 0}}
>>
>> (gdb) p *(ua_pres_t*)(*ps->param)
>>
>> $3 = {id = {s = 0x20455942 <Address 0x20455942 out of bounds>,
>>
>> len = 980445555}, pres_uri = 0x40323531, event = 875444279,
>>
>> expires = 875703856, desired_expires = 858861105, flag = 808794676,
>>
>> db_flag = 1394618421, cb_param = 0x322f5049, next = 0xa0d302e,
>>
>> ua_flag = 979462486, etag = {
>>
>> s = 0x50495320 <Address 0x50495320 out of bounds>, len = 808333871},
>>
>> tuple_id = {s = 0x5044552f <Address 0x5044552f out of bounds>,
>>
>> len = 775436064}, body = 0x322e3034, content_type = {
>>
>> s = 0x312e3134 <Address 0x312e3134 out of bounds>, len = 1648047155},
>>
>> watcher_uri = 0x636e6172, call_id = {
>>
>> s = 0x397a3d68 <Address 0x397a3d68 out of bounds>, len = 1647593320},
>>
>> to_tag = {s = 0x3435634b <Address 0x3435634b out of bounds>,
>>
>> len = 842149473}, from_tag = {
>>
>> s = 0x63306461 <Address 0x63306461 out of bounds>, len = 808334648},
>>
>> cseq = 1767246349, version = 1394621025, outbound_proxy = 0x322f5049,
>>
>> extra_headers = 0x552f302e, record_route = {
>>
>> s = 0x31205044 <Address 0x31205044 out of bounds>, len = 825111097},
>>
>> remote_contact = {s = 0x312e3836 <Address 0x312e3836 out of bounds>,
>>
>> len = 976498224}, contact = {
>>
>> s = 0x36373135 <Address 0x36373135 out of bounds>, len = 1701985073}}
>>
>> Yes, it is a test server so very happy to arrange for remote access
>> if required. In the meantime, I will do a little more digging to try
>> to find out why entity is null.
>>
>> Cheers,
>>
>> Charles
>>
>
>
> --
> Daniel-Constantin Mierla -http://www.asipto.com
> http://twitter.com/#!/miconda <http://twitter.com/#%21/miconda> -http://www.linkedin.com/in/miconda
>
> ------------------------------------------------------------------------
>
> No virus found in this message.
> Checked by AVG - www.avg.com <http://www.avg.com>
> Version: 2012.0.2176 / Virus Database: 2425/5004 - Release Date: 05/16/12
>
--
Daniel-Constantin Mierla - http://www.asipto.comhttp://twitter.com/#!/miconda - http://www.linkedin.com/in/miconda
Kamailio Advanced Training, Seattle, USA, Sep 23-26, 2012 - http://asipto.com/u/katu
Hello
I've two problems regarding dialog module- used for profiling users that
are in-a-call.
My topology is quiet simple.
SIP-USER-71141---->Kamailio------------->Asterisk[AGI]||
CALLEE<-----------------Kamailio<--------------------------------||
1- I wish to store my custom SIP header value in profiles.
I'm having trouble in figuring out on how to use Dialog_vars table in my
kamailio server. I'm using dialog module to profile SIP users that are in
call or making a call. It works well and the dialog maintains an entry when
the call is established. Now, the difficult part is that I want my custom
header to be inserted into either dialog table or dialog_vars table such
that when I do a query "*is_in_profile("$avp(my_value)")*" it returns me a
result.
2- Alternative to 1, I can log A,B leg separately but it doesn't erase all
data on call hangup.
Asterisk AGI changes the caller-id of SIP-USERA such that if it was 71141
it would be something like "007" on its way out to destination via
kamailio. Now, at this point in kamailio when the call is answered by
destination the dialog module saves the call data with values corresponding
to "007" and not "71141".
I have to disable the "dialog", "detect_spirals" in order to count this one
call as two separate entities BUT problem occurs when on hangup the B-Leg
gets erased from the table but the A-leg remains in DB for as long as
infinity.
Please help me in this.
Let me know if more details are required from me.
Regards,
Sammy G.
Hi All
With the upcoming release of version 3.3.0, we have updated our kamailio debian
repositories.
* Debian 5.0 "lenny" will no longer be supported. This means that no more
nightly builds for this distribution will be triggered. We'll provide builds
for stable releases of 3.0 ,3.1 and 3.2 branches though.
* Ubuntu 12.04 "Precise" is now supported for nightly builds and 3.2+ versions.
Next time a 3.2.x version is tagged we'll provide the build. Meanwhile you
can download the nightly build of 3.2 branch for this distro.
* There will be no more nightly builds of 3.1 branch. We'll provide stable
builds in case another version is released though.
* We now support nightly builds of branch 3.3 (same as 3.2 and master). You can
test latest git versions of branch 3.3 until a stable release is built using
these repositories:
deb http://deb.kamailio.org/kamailio33-nightly squeeze main
deb http://deb.kamailio.org/kamailio33-nightly wheezy main
deb http://deb.kamailio.org/kamailio33-nightly lucid main
deb http://deb.kamailio.org/kamailio33-nightly precise main
All the information and repositories can be found in kamailio wiki as usual:
http://www.kamailio.org/dokuwiki/doku.php/packages:debshttp://www.kamailio.org/wiki/packages/debs