Re: [SR-Users] Segfault in Kamailio 1-3-4 to 1.5.5

2011-02-28 Thread Henning Westerholt 
On Monday 28 February 2011, Andrew O. Zhukov wrote:
> As I understood you do not provide any support for a legacy versions.

Hi Andrew,

1.5 still used from a lot of people, including us. Have you tried to reach one 
of the companies on this list:

http://www.kamailio.org/w/business-directory/

There is also a dedicated business list which maybe you get a faster response 
for your support query, more information can be found here:

http://www.kamailio.org/w/business/

Best regards,

Henning

___
SIP Express Router (SER) and Kamailio (OpenSER) - sr-users mailing list
sr-users@lists.sip-router.org
http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users

Re: [SR-Users] Calls are killed during kamailio restart

2011-02-28 Thread Henning Westerholt 
On Thursday 24 February 2011, Efelin Novak wrote:
> I'd like to ask whether my situation is normal. During kamailio restart
> calls are dropped from mediaproxy. Those two programs are connected using
> kamailio.sock. Why RTP strem is dropped when SIP proxy is restarted? I
> would expect just undelivered BYE or something.

Hi Efelin,

i'm not an expert with mediaproxy, but does the kamailio hold some state that 
mediaproxy need to proper route the RTP packets? This would explain the 
behaviour that you observe, as this would probably lost during a restart.

Cheers,

Henning

___
SIP Express Router (SER) and Kamailio (OpenSER) - sr-users mailing list
sr-users@lists.sip-router.org
http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users

[SR-Users] UC Expo 2011, London, next week

2011-02-28 Thread Daniel-Constantin Mierla 

Hello,

I will be visiting the first day of UC Expo in London 
(http://www.ucexpo.co.uk/), Tuesday, March 8. If you are going to be 
there and want to meet for a chat about Kamailio & VoIP, drop me an email.


Cheers,
Daniel

--
Daniel-Constantin Mierla
http://www.asipto.com


___
SIP Express Router (SER) and Kamailio (OpenSER) - sr-users mailing list
sr-users@lists.sip-router.org
http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users

Re: [SR-Users] kamctl db exec

2011-02-28 Thread Henning Westerholt 
On Saturday 26 February 2011, 侯旭光 wrote:
> But I need to use the feature, is it aviliable or not?

Hi 侯旭光,

ok.. Have you tried if its work with an simple example?

kamctl exec "show databases" 

Cheers,

Henning

___
SIP Express Router (SER) and Kamailio (OpenSER) - sr-users mailing list
sr-users@lists.sip-router.org
http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users

[SR-Users] Kamailio Installation

2011-02-28 Thread Suresh Bhandari 
Hello Community,

I am new to Kamailio, and this list as well.

I am trying to install Kamailio 3.1.2, but I am getting too many errors. I
have fixed some but still not getting the way.

I am using Red Hat Enterprise Linux (RHEL) 5, and /usr/local directory.

When I ran the following command:

make group_include="standard standard-dep mysql"
include_modules="carrierroute peering" install

it prompted not found error for the file docbookx.dtd, I found it
(modules/auth/auth.xml, and modules_s/acc_syslog/acc_syslog.xml) and fixed
it as it was errorenous URL location.

For reference earlier it was
http://www.oasis-open.org/docbookid/id/g/4.5/docbookx.dtd, which I changed
to http://www.oasis-open.org/docbook/xml/4.5/docbookx.dtd.

Now when I run the previous command again, I am getting the follwing errors:
*nsgmls:http://www.oasis-open.org/docbook/xml/4.5/docbookx.dtd:116:17:E:
"X20AC" is not a function name*

If I ignore this, and continue, I am not able to find the "sip-router"
service in /etc/init.d.

The entire errors is attached here.

Please help me solve the issue.

TIA

Suresh
make: *** No rule to make target `install'.  Stop.
___
SIP Express Router (SER) and Kamailio (OpenSER) - sr-users mailing list
sr-users@lists.sip-router.org
http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users

Re: [SR-Users] Unable to start Siremis

2011-02-28 Thread jack 
Make suyre that themo_writable is enabed and alllow all access to write to disk . Booth are set in the httpd.conf filesJack Bloch4Voice LLCTel   : 1-888-VOICE17   ext. 202e-mail: j...@4voice.netweb   : www.4voice.netThe information contained in this email may be confidential or otherwise protected from disclosure. If you're not the intended recipient, or if it was sent to you in error, please delete this email. Any dissemination, distribution or other use of the contents of this email by anyone other than the intended recipient is strictly prohibited.


 Original Message 
Subject: Re: [SR-Users] Unable to start Siremis
From: hb 
Date: Sun, February 27, 2011 10:20 pm
To: j...@4voice.net
Cc: sr-users@lists.sip-router.org

Hi jack：        I got the same problem with you.        I know little about apache and HTML, would you tell me how to configuration apache specific.        Thanks a lot.                                                                                                                                                      haibo huang  



___
SIP Express Router (SER) and Kamailio (OpenSER) - sr-users mailing list
sr-users@lists.sip-router.org
http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users

[SR-Users] Radius authentication

2011-02-28 Thread Pablo Ros 
I am trying to authenticate through radius (info in LDAP database). I am
using kamailio 3.1

First of all I would like to clear up an issue:

As shown the way to do the authentication is done with:

*Code:*
if (! radius_www_authorize("uu.net")) {
www_challenge("uu.net", "0");
return;
}


Ok, when I installed openser I did it with kamailio "flavour" so it was
using the auth_radius module belonging to it.
Does anyone know which would be the correct way to do the challenge to the
user cause is was not working at all. The radius client does not even send
it. I got stuck some time till I just decided to load the module from ser
modules folder and then freeradius server started to get correctly my
requests. Actually I can even see it authenticates them correctly.

However Openser/Kamailio doesn't seem to see the same and it doesn't saves
location.



*Code:*

route[AUTH] {
#!ifdef WITH_AUTH
# Primeramente comprobamos si pertenece a nuestro dominio; si no ya no hace
falta comprobar credenciales.
if (uri==myself)
{
if (is_method("REGISTER"))
{
xlog("L_NOTICE","KAM-INFO: r[AUTH] - REGISTER - User
info: ($fu):($si)>\n");
if (!radius_www_authorize("i2cat.net")){
route(RADIUS);
#www_challenge("i2cat.net","0");
exit;
}
}

if ($au!=$tU)
{
sl_send_reply("403","Forbidden auth ID");
exit;
}
} else {

#!ifdef WITH_IPAUTH
if(allow_source_address())
{
# source IP allowed
return;
}
#!endif

# authenticate if from local subscriber
if (from_uri==myself)
{
if (!proxy_authorize("$fd", "subscriber")) {
proxy_challenge("$fd", "0");
exit;
}
if (is_method("PUBLISH"))
{
if ($au!=$tU) {
sl_send_reply("403","Forbidden auth
ID");
exit;
}
} else {
if ($au!=$fU) {
sl_send_reply("403","Forbidden auth
ID");
exit;
}
}

consume_credentials();
# caller authenticated
} else {
# caller is not local subscriber, then check if it
calls
# a local destination, otherwise deny, not an open
relay here
if (!uri==myself)
{
sl_send_reply("403","Not relaying");
exit;
}
}
}
#!endif
return;
}



Before doing the challenge then it just goes throught:

*Code:*

route[RADIUS]
{

   sl_send_reply("100", "Trying");
   append_to_reply("Expires: 600\r\n");
   append_to_reply("Min-Expires: 240\r\n");

   xlog("L_NOTICE","KAM-INFO: RADIUS AUTHENTICATION - AUTHORIZING USER $fU -
<$fu>:<$si>\n");

   xlog("L_NOTICE","KAM-INFO: CHALLENGING. - RETCODE-> $rc \n");
   www_challenge("i2cat.net", "0");
   switch($rc){
 case -5:
xlog("L_INFO", "-> 500: internal server error");
sl_send_reply("500", "Internal Server Error");
 case -4:
xlog("L_INFO", "-> 404: credentials not found");
sl_send_reply("404", "Credentials Not Found");
 case -3:
xlog("L_INFO", "-> 400: bad request - stale nonce");
sl_send_reply("400", "Bad Request");
 case -2:
xlog("L_INFO", "-> 401: invalid password");
sl_send_reply("401", "Invalid Password");
 case -1:
xlog("L_INFO", "-> 401: invalid user");
sl_send_reply("401", "Invalid User");
 default:
xlog("L_INFO", "-> 401: unauthorized");
sl_send_reply("401", "Unauthorized");
 }
}


But... I got that in the debug of Kamailio:


*Code:* 4(31099) DEBUG: auth [api.c:95]: auth: digest-algo: MD5 parsed
value: 1
 4(31099) DEBUG: auth_radius [sterman.c:271]: radius_authorize_sterman():
Success
 4(31099) WARNING: auth_radius [authorize.c:89]: RADIUS server did not send
SER-UID attribute in digest authentication reply
 4(31099) DEBUG: auth [challenge.c:102]: build_challenge_hf: realm='
i2cat.net'
 4(31099) DEBUG: auth [challenge.c:113]: build_challenge_hf: qop='auth'
 4(31099) DEBUG: auth [cha

Re: [SR-Users] Can only tranfer (refer) a call one time

2011-02-28 Thread Grzegorz Stanislawski 
it is just bypass to enable call transfers for users connected to sipx, 
when uplink ITSP doesn't support REFER.
sipxbridge works as SBC in b2bua mode, it stays in path of all calls to 
and from Your uplink ITSP and when it receives REFER i just makes new 
call (using INVITE) to Your ITSP, and then bridges new call with proper 
leg of previous call and disconects other one.
so inside sipx 'domain' you can use call transers using refer, and from 
Your ITSP side there are only invites byes and cancels.
in ex. in case when someone from outside calls you inside sipx, and you 
forward it back outside - from ITSP point of view there will be 2 calls, 
one to and one from your sipx, and he would have no idea that those 
calls are related.


drawback is of course that rtp streams are going back and forth through 
your internet uplink and AFAIR deaf silence at some point of transfer, 
but at least it works with all lousy ITSP's.


You should check sipx documentation or sipx mailing list, this thread is 
getting off-topic.


and REFER is not only for blind transfers ;-)

Grzegorz Stanislawski


W dniu 2011-02-27 20:35, Youngjin Park pisze:


Hi,

Can you tell me what advantage on INVITE has against REFER?

REFER is a kind of blind transfer and INVITE in sipXbridge is 3PCC?

Thanks in advance.

Youngjin


On Sun, Feb 27, 2011 at 6:40 AM, Grzegorz Stanislawski
mailto:stang...@netitel.pl>> wrote:

Hi.
We have proverb for this, i don't know english version but it
goes like this:
"When it isn't known what it's all about, it's about money"

Your ITSP had troubles with proper handling second transfer for
billing purposes so decided to disable it.
Proxy doesnt participate in call transfer, but ITSP it must
charge users properly: Alice should pay just for call to Bob,
Bob for "his" call to Charlie and so on.
If You are using sipX You should use sipXbridge, it replaces
REFER with INVITE and bridges calls.

Grzegorz Stanislawski



W dniu 2011-02-25 11:40, niklas rehnberg pisze:

Hi,
Thank for the quick response.
The issue occur only when the Alice is a PSTN client.
My ITSP says that they only supporting one call transfer
(very strange).
They can not explain why etc...
PSTN client:  Alice
MGW/MGC(ITSP): Cisco/SER
Our sip server:   SIPX

BR Niklas
2011/2/25 Iñaki Baz Castillo mailto:i...@aliax.net> >>

2011/2/25 niklas rehnberg mailto:niklas.rehnb...@gmail.com>
>>:
 > Hi,
 > Have following issue:
 >
 > Alice calling Bob.
 > Bob make call transfer to Charlie  (works fine)
 > Charlie transfer Alice to David.(the call break)
 >
 > Why is not possible to transfer the call more than one time?
 > Is it any parameters?
 >
 > My ITSP use SER together with Cisco MGW.

Niklas, nothing in SIP protocol neither in SER/Kamailio
makes your
scenario to fail. It must be a problem in your custom
setup. Try
identifying the problem capturing SIP traces.
Also take into account that a proxy doesn't participate
at all in the
process of a "call transfer". It's just a transparent
mechanism for a
proxy.

--
Iñaki Baz Castillo
mailto:i...@aliax.net> >>




___
SIP Express Router (SER) and Kamailio (OpenSER) - sr-users
mailing list
sr-users@lists.sip-router.org

http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users



___
SIP Express Router (SER) and Kamailio (OpenSER) - sr-users
mailing list
sr-users@lists.sip-router.org 
http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users





___
SIP Express Router (SER) and Kamailio (OpenSER) - sr-users mailing list
sr-users@lists.sip-router.org
http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users



___
SIP Express Router (SER) and Kamailio (OpenSER) - sr-users mailing list
sr-users@lists.sip-router.org
http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users

Re: [SR-Users] Segfault in Kamailio 1-3-4 to 1.5.5

2011-02-28 Thread Andrew O. Zhukov 

Henning,
Those guys is an expert in configuration file not in debugging of source 
code memory module.
I use ser, openser since 0.9 version. It's a lot of features added into 
the config for a this 5 years. I'm absolutely sure there is the trouble.



On 02/28/2011 11:43 AM, Henning Westerholt wrote:

On Monday 28 February 2011, Andrew O. Zhukov wrote:

As I understood you do not provide any support for a legacy versions.


Hi Andrew,

1.5 still used from a lot of people, including us. Have you tried to reach one
of the companies on this list:

http://www.kamailio.org/w/business-directory/

There is also a dedicated business list which maybe you get a faster response
for your support query, more information can be found here:

http://www.kamailio.org/w/business/

Best regards,

Henning




___
SIP Express Router (SER) and Kamailio (OpenSER) - sr-users mailing list
sr-users@lists.sip-router.org
http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users

Re: [SR-Users] no private memory left after mi mt_reload command

2011-02-28 Thread Henning Westerholt 
On Friday 25 February 2011, Javier Gallart wrote:
> we are currently doing it looking for error messages in the logs, and it´s
> ok, but since the request is processed by the kamailio routing script via
> the xmlrpc module with the dispatch_rpc() command , I was wondering if
> there could be a  way to check the command output inside the same script.

Hi Javier,

this xmlrpc transport does not return a result from the command execution on 
the server?

Cheers,

Henning

___
SIP Express Router (SER) and Kamailio (OpenSER) - sr-users mailing list
sr-users@lists.sip-router.org
http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users

Re: [SR-Users] Segfault in Kamailio 1-3-4 to 1.5.5

2011-02-28 Thread Iñaki Baz Castillo 
2011/2/25 Andrew O. Zhukov :
> In continue of letters:
> Kamailio 1.5.5 No TLS Segmentation Fault
> After upgrade from openser 1.3.4 to kamailio 1.5.5 the same crash set
>
> Can someone from developers provide me commercial support to fix this bug in
> malloc module.

Hi Andrew. Not sure if you have provided a detailed report of the
issue in some other mail, have you? If not, provide details please.

Regards.

-- 
Iñaki Baz Castillo


___
SIP Express Router (SER) and Kamailio (OpenSER) - sr-users mailing list
sr-users@lists.sip-router.org
http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users

Re: [SR-Users] Segfault in Kamailio 1-3-4 to 1.5.5

2011-02-28 Thread Timo Reimann 
On 28.02.2011 15:49, Iñaki Baz Castillo wrote:
> 2011/2/25 Andrew O. Zhukov :
>> In continue of letters:
>> Kamailio 1.5.5 No TLS Segmentation Fault
>> After upgrade from openser 1.3.4 to kamailio 1.5.5 the same crash set
>>
>> Can someone from developers provide me commercial support to fix this
> bug in
>> malloc module.
> 
> Hi Andrew. Not sure if you have provided a detailed report of the
> issue in some other mail, have you? If not, provide details please.

He provided detail, unfortunately in another thread which broke
continuity. Look for "After upgrade from openser 1.3.4 to kamailio 1.5.5
the same crash set" from 10.2., 7:37.


Cheers,

--Timo

___
SIP Express Router (SER) and Kamailio (OpenSER) - sr-users mailing list
sr-users@lists.sip-router.org
http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users

Re: [SR-Users] Segfault in Kamailio 1-3-4 to 1.5.5

2011-02-28 Thread Andrew O. Zhukov 

On 02/28/2011 05:06 PM, Timo Reimann wrote:

On 28.02.2011 15:49, Iñaki Baz Castillo wrote:

2011/2/25 Andrew O. Zhukov:

In continue of letters:
Kamailio 1.5.5 No TLS Segmentation Fault
After upgrade from openser 1.3.4 to kamailio 1.5.5 the same crash set

Can someone from developers provide me commercial support to fix this

bug in

malloc module.


Hi Andrew. Not sure if you have provided a detailed report of the
issue in some other mail, have you? If not, provide details please.


He provided detail, unfortunately in another thread which broke
continuity. Look for "After upgrade from openser 1.3.4 to kamailio 1.5.5
the same crash set" from 10.2., 7:37.


Cheers,

--Timo


I sent yesterday coredump directly.

___
SIP Express Router (SER) and Kamailio (OpenSER) - sr-users mailing list
sr-users@lists.sip-router.org
http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users

Re: [SR-Users] no private memory left after mi mt_reload command

2011-02-28 Thread Javier Gallart 
Hi Henning

yes, it does. We want to build the logic for acting upon a tree reload
failure -like sending an alarm or something of the kind-. We were deciding
whether to do it at the external java application that actually sends the
xmlrpc request and that will receive the response, or at the kamailo itself,
but I've found no way to access to the command output directly from the
kamailio configuration script. But that's fine, we will just do it outside.

Thanks for everything

Regards

Javi

On Mon, Feb 28, 2011 at 1:38 PM, Henning Westerholt <
henning.westerh...@1und1.de> wrote:

> On Friday 25 February 2011, Javier Gallart wrote:
> > we are currently doing it looking for error messages in the logs, and
> it´s
> > ok, but since the request is processed by the kamailio routing script via
> > the xmlrpc module with the dispatch_rpc() command , I was wondering if
> > there could be a  way to check the command output inside the same script.
>
> Hi Javier,
>
> this xmlrpc transport does not return a result from the command execution
> on
> the server?
>
> Cheers,
>
> Henning
>
___
SIP Express Router (SER) and Kamailio (OpenSER) - sr-users mailing list
sr-users@lists.sip-router.org
http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users

[SR-Users] dispatcher confusion

2011-02-28 Thread Klaus Darilion 
Hi!

Every time I use the dispatcher(k) module I am confused again. Sometimes
it seems that "probing" is a dedicated state, sometimes it seems that
"probing" is done also in "active" state, but never in "inactive" state.

IMO "probing" should only be a flag which indicates if OPTIONS should
sent or not. If probing is successful, then the state should be
"active". If probing is unsuccessful, then the state should be "inactive".

Current behavior is very strange (ds_probing_mode(0)):

--> startup state: A --> no probing

kamctl fifo ds_set_state i 1 sip:
--> state: I --> no probing

kamctl fifo ds_set_state a 1 sip:
--> state: A --> no probing

calling 3 times ds_mark_dst("p")
--> state: P --> probing (and dst is still loaded as last value into the
dst_avp, why?)

kamctl fifo ds_set_state i 1 sip:
--> state: I --> still probing

kamctl fifo ds_set_state a 1 sip:
--> state: P (???) --> probing

Thus, "ds_set_state a ..." does not set active, but probing if it was
probing before. Strange.

And as "inactive" does not stop probing when dst was in probing mode,
the destination becomes automatically "active" if the probing succeeds.

And why is a destination in probing mode loaded into the dst_avp? Very
weird.

Is there a reason for this behavior?

Thanks
Klaus



___
SIP Express Router (SER) and Kamailio (OpenSER) - sr-users mailing list
sr-users@lists.sip-router.org
http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users

[SR-Users] modulo operator

2011-02-28 Thread Klaus Darilion 
Hi!

Using kamailio 3.1.1, I failed to use '%' as described in the core
cookbook. Using 'mod' instead seems to work.

regards
Klaus

___
SIP Express Router (SER) and Kamailio (OpenSER) - sr-users mailing list
sr-users@lists.sip-router.org
http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users

Re: [SR-Users] dispatcher confusion

2011-02-28 Thread Daniel-Constantin Mierla 

Hello,

On 2/28/11 5:29 PM, Klaus Darilion wrote:

Hi!

Every time I use the dispatcher(k) module I am confused again. Sometimes
it seems that "probing" is a dedicated state, sometimes it seems that
"probing" is done also in "active" state, but never in "inactive" state.
if you set the global parameter for probing, then no matter the state, 
the pinging is done for all addresses.


If the module parameter is not set, only the destinations marked as 
"probing" should be pinged.


In devel version I tried to sort out a bit these states, so we should 
make it more sane and clear.





IMO "probing" should only be a flag which indicates if OPTIONS should
sent or not. If probing is successful, then the state should be
"active". If probing is unsuccessful, then the state should be "inactive".

Current behavior is very strange (ds_probing_mode(0)):

-->  startup state: A -->  no probing

kamctl fifo ds_set_state i 1 sip:
-->  state: I -->  no probing

kamctl fifo ds_set_state a 1 sip:
-->  state: A -->  no probing

When ds_probing_mode==0, only if you set P flag to address will be pinged.


calling 3 times ds_mark_dst("p")
-->  state: P -->  probing (and dst is still loaded as last value into the
dst_avp, why?)

kamctl fifo ds_set_state i 1 sip:
-->  state: I -->  still probing

kamctl fifo ds_set_state a 1 sip:
-->  state: P (???) -->  probing

Thus, "ds_set_state a ..." does not set active, but probing if it was
probing before. Strange.

And as "inactive" does not stop probing when dst was in probing mode,
the destination becomes automatically "active" if the probing succeeds.
inactive and probing are different flags. In devel I introduced new 
state 'disabled' for cases when you want to "remove" an address from 
destination list.

And why is a destination in probing mode loaded into the dst_avp? Very
weird.

If it is just probing and not inactive, then it is loaded as new dst.


Is there a reason for this behavior?
IIRC, I think Carsten developed most of the probing mode, maybe there 
was a reason behind current behavior.


Cheers,
Daniel

--
Daniel-Constantin Mierla
http://www.asipto.com


___
SIP Express Router (SER) and Kamailio (OpenSER) - sr-users mailing list
sr-users@lists.sip-router.org
http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users

[SR-Users] Question about time display in SIREMIS 2.0

2011-02-28 Thread Ricardo Martinez 
Hello.

Is there a way to adjust the timezone to display the charts and the logs in
the SIREMIS 2.0?  I have my linux machine with my local timezone, but the
display in the charts and the logs are not in synch with my local time.

Thanks in advance.



Regards,



Ricardo Martinez.-
___
SIP Express Router (SER) and Kamailio (OpenSER) - sr-users mailing list
sr-users@lists.sip-router.org
http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users

[SR-Users] Consulting needed

2011-02-28 Thread Pete Ashdown 
I have been trying to accomplish a couple tasks with Kamailio over the past
month with no luck.  What I need is a bit of one-on-one training with
someone who knows the lay of the land.  If you do this kind of consulting
and can use Skype with possibly a shared-screen terminal, please drop me an
email with your rate.




signature.asc
Description: OpenPGP digital signature
___
SIP Express Router (SER) and Kamailio (OpenSER) - sr-users mailing list
sr-users@lists.sip-router.org
http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users

Re: [SR-Users] Calls are killed during kamailio restart

2011-02-28 Thread Juha Heinanen 
Henning Westerholt writes:

> i'm not an expert with mediaproxy, but does the kamailio hold some state that 
> mediaproxy need to proper route the RTP packets? This would explain the 
> behaviour that you observe, as this would probably lost during a
> restart.

no, kamailio does not need to maintain any state unless use the engage
mediaproxy command in which case i think dialog module is needed.  i
would stay way of that mode (as well as the buggy dialog module).

-- juha

___
SIP Express Router (SER) and Kamailio (OpenSER) - sr-users mailing list
sr-users@lists.sip-router.org
http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users

Re: [SR-Users] Consulting needed

2011-02-28 Thread x-kamailio 
I need similar assistance. Drop me an email, too!

-- 
Mark Sidell
Partner
Forte, Inc.
919-942-7068
fax 919-969-2844
www.forteinc.com

___
SIP Express Router (SER) and Kamailio (OpenSER) - sr-users mailing list
sr-users@lists.sip-router.org
http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users

Re: [SR-Users] Segfault in Kamailio 1-3-4 to 1.5.5

2011-02-28 Thread Andrew O. Zhukov 

I someone interested in .
It's the old coredumps from 1.3.4. It's really much stabile then 1.5.5
I did degrade today night and going to try opensips.


warning: Missing the matching library file: 
/usr/lib/debug/.build-id/7f/bba7706883599d6df45722d7eb779d8768a80b
Core was generated by `openser -P /var/run/openser/openser.pid -m 32 -u 
openser -g openser -w /var/run'.

Program terminated with signal 11, Segmentation fault.
#0  fm_malloc (qm=0x7389e0, size=) at 
mem/f_malloc.c:267

267 mem/f_malloc.c: No such file or directory.
in mem/f_malloc.c
(gdb) bt full
#0  fm_malloc (qm=0x7389e0, size=) at 
mem/f_malloc.c:267

f = (struct fm_frag **) 0x778130
hash = 10
#1  0x004918ad in parse_headers (msg=0x7711b8, flags=256, 
next=0) at parser/msg_parser.c:308

hf = 
itr = (struct hdr_field *) 0xd302e3535666565
	tmp = 0x7298b6 "User-Agent: Asterisk PBX\r\nMax-Forwards: 
5\r\nContent-Length: 0\r\n\r\n"
	rest = 0x7298b6 "User-Agent: Asterisk PBX\r\nMax-Forwards: 
5\r\nContent-Length: 0\r\n\r\n"

end = 0x7298f7 ""
orig_flag = 0
__FUNCTION__ = "parse_headers"
#2  0x2b55fc18 in is_maxfwd_present (msg=0x7389e0, 
foo=0x7fffbf67f400) at mf_funcs.c:61

x = 
__FUNCTION__ = "is_maxfwd_present"
_c = 57 '9'
#3  0x2b55ed61 in w_process_maxfwd_header (msg=0x7389e0, 
str1=0xa ,
str2=0xd302e3535666565 ) 
at maxfwd.c:145

val = 
mf_value = {s = 0x2e9 , len = -1342089735}
__FUNCTION__ = "w_process_maxfwd_header"
#4  0x0040c28f in do_action (a=0x7462d0, msg=0x7711b8) at 
action.c:821

ret = 
v = 
to = 
p = 
tmp = 
new_uri = 
end = 
crt = 
len = 
user = 
	uri = {user = {s = 0x7fffbf67f820 "\005", len = 7643232}, passwd = {s = 
0x1 , len = 7629192}, host = {
s = 0x74a0f0 "\006", len = 7803320}, port = {s = 0x2 out of bounds>, len = 7803320}, params = {s = 0x7711b8 "�\211\a", len = 
4247863},
  headers = {s = 0xa8 , len = 1}, port_no = 
63760, proto = 48999, type = 32767, transport = {s = 0x70a4a0 "\b�\f��*",
len = -1083705312}, ttl = {s = 0x38404748fa 
"H\205�I\211�tJ\203=_\026.", len = 0}, user_param = {s = 0x86ed10 
"�\216\207", len = 1}, maddr = {
s = 0x3fb0012c05 
"\205��u\035\017�D$\017= {s = 0x3840752980 "", len = 9916304}, lr = {
s = 0xff96 , len = -1083705072}, r2 = 
{s = 0x770eb8 "N�\"��*", len = 1}, transport_val = {s = 0x3840475f2c 
"\203=5",
len = 8932}, ttl_val = {s = 0x86f0b8 "`�\206", len = 0}, 
user_param_val = {s = 0x3fb0014e6a 
"H\211�H\003S\bH\213\003H\211S\b�\004\020", len = 1},
  maddr_val = {s = 0x0, len = 9916304}, method_val = {s = 
0x2acd4030 "I\213~\bH�G0", len = -1083705072}, lr_val = {s = 
0x70a4a0 "\b�\f��*", len = 0},

  r2_val = {s = 0x417bc1 "H\205�tGH\211���\a", len = 65430}}
	next_hop = {user = {s = 0x70a4a0 "\b�\f��*", len = -1342088916}, passwd 
= {s = 0x0, len = 0}, host = {
s = 0x , 
len = 9935623}, port = {
s = 0x , 
len = 1081420160}, params = {s = 0xf , len = 
8754704},
  headers = {s = 0x4 , len = -1083705484}, 
port_no = 3768, proto = 119, type = ERROR_URI_T, transport = {
s = 0x38404748fa "H\205�I\211�tJ\203=_\026.", len = 15}, ttl = {s = 
0x384052146b "/etc/localtime", len = 8754704}, user_param = {
s = 0x4 , len = -1083705484}, maddr = {s 
= 0x770eb8 "N�\"��*", len = 1}, method = {s = 0x384048cc0e 
"\213\005\f\221,",
len = 5197468}, lr = {s = 0x2aee2059 "2011-01-27 
18:10:30','in','as5a292c8e','')", len = -1427234727}, r2 = {s = 
0x384048cf70 "\213\005�\215,",
len = 16}, transport_val = {s = 0x38404923d8 "�Y���Hc�L\211��0", 
len = 0}, ttl_val = {s = 0x200 , len = -1},

  user_param_val = {
s = 0x72971b "193.28.184.13;branch=z9hG4bK558b.e0feef55.0\r\nVia: 
SIP/2.0/UDP XXX.XX.XXX.13;branch=z9hG4bK558b.d0feef55.0\r\nVia: 
SIP/2.0/UDP XXX.XX.XXX.13;branch=z9hG4bK558b.c0feef55.0\r\nVia: 
SIP/2.0/UDP XXX.XX.XXX.70:"..., len = 0}, maddr_val = {s = 0x758c50 
"\002", len = 7703472}, method_val = {
s = 0x746988 "\016", len = 7655064}, lr_val = {s = 0x7711b8 
"�\211\a", len = 1}, r2_val = {s = 0x7711b8 "�\211\a", len = -1083705856}}

u = 
---Type  to continue, or q  to quit---
port = 
cmatch = 
aitem = 
adefault = 
spec = 
model = 
val = {rs = {s = 0x772508 "\n", len = 7807240}, ri = 7807992, flags = 0}
__FUNCTION__ = "do_action"
#5  0x0040e7db in run_action_list (a=, 
msg=0x7711b8) at action.c:132

ret = -1
t = (struct action *) 0x7462d0
__FUNCTION__ = "run_action_list"
#6  0x0045ba94 in eval_expr (e=0x746370, msg=0x7711b8, 
val=0xd302e3535666565) at route.c:1096

ret = 
rec_lev = 3
__FUNCTION__ = "eval_expr"
#7  0x0045b50d in eval_expr (e=0x7463b8, msg=0x7711b8, val=0x0) 
at route.c:1403

ret = 
rec_lev = 3
__FUNCT