31 okt 2012 kl. 18:51 skrev Uri Shacked :
> Hi,
> can two kamailio servers, one running 3.2 and the other 3.3 run using the
> same DB?
> one will turn to version table X and the other to version table Y
> (i am not using the modules that the DB table changed...
Simple answer: No.
I am sure the
Hi,
can two kamailio servers, one running 3.2 and the other 3.3 run using the
same DB?
one will turn to version table X and the other to version table Y
(i am not using the modules that the DB table changed...
BR,
Uri
___
SIP Express Router (SER) and Kama
I swithced again to tcp, and 'kamctl ps' now gives the following:
Process:: ID=0 PID=5913 Type=attendant
Process:: ID=1 PID=5914 Type=slow timer
Process:: ID=2 PID=5915 Type=timer
Process:: ID=3 PID=5916 Type=MI FIFO
Process:: ID=4 PID=5917 Type=ctl handler
Process:: ID=5 PID=5918 Type=MI DA
Is this all the output of kamctl ps? Because there is no udp or tcp
worker process. If yes, then is something wrong with your config, be
sure you set proper children parameter value.
Cheers,
Daniel
On 10/31/12 4:53 PM, Ramazan Yilmaz wrote:
And the output of 'kamctl ps' is as following (after
And the output of 'kamctl ps' is as following (after changing back to tls):
Process:: ID=0 PID=5621 Type=attendant
Process:: ID=1 PID=5622 Type=slow timer
Process:: ID=2 PID=5623 Type=timer
Process:: ID=3 PID=5624 Type=MI FIFO
Process:: ID=4 PID=5625 Type=ctl handler
Process:: ID=5 PID=5626
These messages are for tls. When switched to TCP, it works fine. What can
be the problem?
On Wed, Oct 31, 2012 at 3:39 PM, Daniel-Constantin Mierla wrote:
> Hello,
>
> does registration over UDP work fine? Are these messages for tcp or tls
> connections?
>
> Can you paste the output of 'kamctl
Hello All,
Did anyone get a chance to look at my question below?
Can anyone explain what will happen when the next hop is the rls
server address? How will this notify get handled.
Thanks,
Sangeeta
On Tue, Oct 30, 2012 at 5:01 PM, Sangeeta Shah wrote:
> I have another follow up question on RL
Friends,
Dispatcher has a mode 8 - "use first destination" which makes sense for a
textfile driven dispatcher configuration.
Now if I use a database - will dispatcher first sort on priority, then take the
first?
It seems so from the documentation of the text file:
priority: sets the pri
Hello,
does registration over UDP work fine? Are these messages for tcp or tls
connections?
Can you paste the output of 'kamctl ps'?
Cheers,
Daniel
On 10/30/12 5:32 PM, Ramazan Yilmaz wrote:
Any ideas? It really seems as a bug, as the logs say. But do you have
any workaround suggestion?
O
31 okt 2012 kl. 14:19 skrev Alex Balashov :
> Inside if(loose_route()) will do.
The question was "where is the right place
>
>> to check the new INVITE?"
Proper answer would be after this block... :-)
/O
>
> if(has_totag()) {
> if(loose_route()) {
> if(is_method("INVITE")) {
>
Inside if(loose_route()) will do.
if(has_totag()) {
if(loose_route()) {
if(is_method("INVITE")) {
# It's a reinvite.
}
}
}
On 10/31/2012 09:15 AM, Alex Solt wrote:
I appreciate for the response.
I am using an old kamailio app. The has_totag() an
31 okt 2012 kl. 14:15 skrev Alex Solt :
> I appreciate for the response.
>
> I am using an old kamailio app. The has_totag() and loos_route() blocks are
> within the route() block. The question is where is the right place to check
> the new INVITE?
> Is it after the has_totag() block?
>
>
>
I appreciate for the response.
I am using an old kamailio app. The has_totag() and loos_route() blocks are
within the route() block. The question is where is the right place to check the
new INVITE?
Is it after the has_totag() block?
route
{
if (has_totag())
{
...
if (loose_rout
Yes. The reinvite is a sequential (in-dialog) request and, like all sequential
requests, is handles in a different place in the route script than initial
requests.
Sequential requests are processed in the loose_route() section of the main
request route. Initial requests (such as initial INVITE
31 okt 2012 kl. 13:53 skrev Alex Solt :
> Hi,
>
> Is there any function in kamailio that could differentiates between a new
> incoming INVITE message and a re-INVITE message for an existing active call?
Check the default configuration script for how we separate messages in a dialog.
Look for
Hi,
Is there any function in kamailio that could differentiates between a new
incoming INVITE message and a re-INVITE message for an existing active call?
Thanks,
AS
___
SIP Express Router (SER) and Kamailio (
Hello,
I followed the instruction mentioned in Kamailio website. When I do a make
all, I get the error. Please let me know how to fix this. I am new to
Kamailio.
---
Package mono-2 was not found in the pkg-config search path.
Perhaps you should add the directory containing `mono-
Friends,
The 2600Hz project that builds an API-driven telephony service have selected to
switch to Kamailio as a SIP proxy for their SBC. They blog about the switch,
comparing Kamailio with their previous choice and coming to a conclusion:
"To our minds, a more active development community mean
31 okt 2012 kl. 06:49 skrev Vijay Thakur :
> Dear Sir,
>
> Is there any one in the list who have set up (integrated) Kamailio with
> sylkserver for conference. There is very less available information on the
> internet on this topic. All the required changes are made in sylkserver
> config fi
31 okt 2012 kl. 06:39 skrev Jeremy Ardley :
> Hi,
>
> I'm after advice.
>
> I'm developing a script to provide a degree of PBX functionality for a
> small to medium office using Kamailio & SEMS.
>
> This includes mapping internal extensions to external PSTN numbers via
> the SIP trunk provider
20 matches
Mail list logo
