I'd setup another solaris server with kamailio v3.2, applied the patch
and tested the change. Kamailio did not crash nor took a core dump. So
it looks like it might be a hardware problem now.
Thanks
Nathaniel
On 5/9/2012 1:52 PM, Akan wrote:
I changed the use_domain parameter for usrloc to 0
Hi to all,
please could somevody help me with more complicated rtpproxy scenario? I
still cannot understand how to make it working.
We have SBC based on kamailio 3.2.3. Everything seems to work until I
want to translate all SDP messages by SBC IP address (for both sides).
Moreover, I need to
Hi all,
When record routing is enabled, that means, the proxy will act statefull mode,
There has to be a mechanism for storing dialogue states.
Like the location of the peers (Contact header filed of initial INVITE
and 200 OK).
And i suspect these states are stored in variables which has a lifesp
Hi,
I'm installing a brand-new Kamailio / Siremis system.
I have an issue with Siremis failing to load PDO extensions. I have
other systems working O.K. on Centos 5.x
This is my configuration:
Centos 6.2
php-5.3.3-3.el6_2.8.i686.rpm
php-cli-5.3.3-3.el6_2.8.i686.rpm
php-common-5.3.3-3.el6_2.8.i
Hi,
*
*
*
*
We are facing a problem in our opener proxy receiving: *"Message too big"
error.*
Looking at the INVITE message sent by opener I notice the following in the
record-route header:
Record-Route:
Is this a valid value for vsd? Can we correct the value?
Thanks,
R
The parameter [server:default] of TLS config file must be declared? I want
specify two different interfaces (WAN and LAN) and I don't know which
interface will be used as default by TLS module...
Someone know some information about my question?
Best Regards
Hi,
i'll look at it - but first next week (the rest of this blocked by LinuxTag).
Kind regards & thanks,
Carsten
2012/5/22 Gnaneshwar Gatla :
> Hey,
>
> I have fixed the incorrect uri’s being generated by this module while
> publishing user location. This patch also includes some more user recor
On Tue, May 22, 2012 at 5:41 PM, Daniel-Constantin Mierla
wrote:
> Hello,
>
> is 205.164.40.74 the IP address of VoipSwitch? If yes, then the BYE is
> constructed to be sent back to it, because the r-uri has this IP address.
>
> R-uri in the BYE must have the IP address and port of UAC1.
>
> If yo
Hello,
is 205.164.40.74 the IP address of VoipSwitch? If yes, then the BYE is
constructed to be sent back to it, because the r-uri has this IP address.
R-uri in the BYE must have the IP address and port of UAC1.
If you give here all the sip trace for such call (from INVITE to the
BYE, taken
On 2012-05-22 at 12:40, Daniel-Constantin Mierla wrote:
> ok, done few time ago -- I kind of forgot about it.
Thanks!
--
Øyvind Kolbu
pgp27x2xYmzrC.pgp
Description: PGP signature
___
SIP Express Router (SER) and Kamailio (OpenSER) - sr-users mailing
Hey,
I have fixed the incorrect uri's being generated by this module while
publishing user location. This patch also includes some more user record data
to the xml during publish.
I'm not sure if I have followed the naming convention right. Please find the
patch file attached.
Regards,
Gnaneshw
Hello,
few clarifications about siptrace, see inline ...
On 5/22/12 9:31 AM, Marius Zbihlei wrote:
On 05/22/2012 10:07 AM, Klaus Darilion wrote:
In my opinion it would be cool if core has a feature to log every
received and every sent message. The logging should include
timestamp+proto+sourceI
Hello,
On 5/22/12 12:33 PM, Timo Teras wrote:
On Tue, 22 May 2012 13:11:04 +0300 Timo Teras wrote:
On Tue, 22 May 2012 10:46:34 +0200 Daniel-Constantin Mierla
wrote:
Hello,
On 5/19/12 10:39 PM, Timo Teräs wrote:
Search for keywords case insensitively instead of using strstr().
SQlite sto
On 5/22/12 11:20 AM, Øyvind Kolbu wrote:
On 17.05.2012 18:16, Spencer Thomason wrote:
I just tested the patch and it works perfectly.
Daniel, can you backport to 3.2?
Hello,
ok, done few time ago -- I kind of forgot about it.
Cheers,
Daniel
--
Daniel-Constantin Mierla - http://www.asipto.
On Tue, 22 May 2012 13:11:04 +0300 Timo Teras wrote:
> On Tue, 22 May 2012 10:46:34 +0200 Daniel-Constantin Mierla
> wrote:
>
> > Hello,
> >
> > On 5/19/12 10:39 PM, Timo Teräs wrote:
> > > Search for keywords case insensitively instead of using strstr().
> > > SQlite stores decltype as-is, an
On Tue, 22 May 2012 10:46:34 +0200 Daniel-Constantin Mierla
wrote:
> Hello,
>
> On 5/19/12 10:39 PM, Timo Teräs wrote:
> > Search for keywords case insensitively instead of using strstr().
> > SQlite stores decltype as-is, and does the affinity type testing
> > case insensitively too.
>
> Perha
Hi,
we've got some free tickets for LinuxTag 2012, we want to share.
If you like to receive one, just send me a short reply.
They are given away on a first come, first served basis.
Meet us at Hall 7.2b, Booth 278!
So long,
Carsten
P.S.: I'll give a presentation about Kamailio, IMS and Rich
Com
On 17.05.2012 18:16, Spencer Thomason wrote:
I just tested the patch and it works perfectly.
Daniel, can you backport to 3.2?
--
Øyvind
___
SIP Express Router (SER) and Kamailio (OpenSER) - sr-users mailing list
sr-users@lists.sip-router.org
http://
Hello,
On 5/19/12 10:39 PM, Timo Teräs wrote:
Search for keywords case insensitively instead of using strstr().
SQlite stores decltype as-is, and does the affinity type testing
case insensitively too.
Perhaps you should push it asap, so it gets some testing before 3.3.0 is
released.
Thanks,
On 05/22/2012 10:07 AM, Klaus Darilion wrote:
In my opinion it would be cool if core has a feature to log every
received and every sent message. The logging should include
timestamp+proto+sourceIP:port+receivedIP:port for received messages and
timestamp+proto+sourceIP:port+destinationIP:port for
I second that.
Siptrace doesn't log everything, but workarounds can be done, such as using
a combination of setting a flag and using the sip_trace( ) function, and
using them as well from the onsend_route for some outgoing messages, with
careful handling to prevent duplicate logging.
Reda
On T
In my opinion it would be cool if core has a feature to log every
received and every sent message. The logging should include
timestamp+proto+sourceIP:port+receivedIP:port for received messages and
timestamp+proto+sourceIP:port+destinationIP:port for sent messages. For
TLS of course it should l
22 matches
Mail list logo
