Hi Franz,
Thanks for the response.
As suggested followed below commands to check the GRANTs on database hss_db.
mysql -u root -p
show grants for 'hss'@'server.net1.test';
The output result is same as mentioned below.
Could you please guide me here to proceed further.
Regards, Sainath
-- F
Daniel-Constantin Mierla-6 wrote
> Hello,
>
> so practically all registration appear to come from 127.0.0.1:xyz, where
> xyz is some port value.
for devices connected to 443, yes it is (kamailio listen 5060/5061, and
devices can connect also directly)
> My guess is that the connection to the tc
Thanks. I missed that param.
--
View this message in context:
http://sip-router.1086192.n5.nabble.com/Acc-message-to-syslog-tp145000p145047.html
Sent from the Users mailing list archive at Nabble.com.
___
SIP Express Router (SER) and Kamailio (OpenSE
Obviously the access of HSS to the database did not succeed.
You should check if access permissions to the database is enabled for HSS.
Check the GRANTs on the database hss_db.
mysql -u root -p
show grants for 'hss'@'server.net1.test';
quit;
The result should be:
+--
Thanks again and here is the pcap file.
Thanks
Abdul
From: Daniel-Constantin Mierla
Sent: Friday, January 22, 2016 8:46 AM
To: malik sherif; Kamailio (SER) - Users Mailing List
Subject: Re: [SR-Users] Kamailio and freeswitch integration for SBC
Can you attach
Hello,
I have this scenario:
- subscriber registers using TLS
- call arrives from PSTN gateway (in UDP) to subscriber
- I relay the INVITE to subscriber but it doesn't answer the call
- the subscriber has callforward enabled
- we send the call to PSTN callforward destination using carrier
No, I meant when it is taken from dialog max lifetime value (so when the
override_lifetime is not set).
Looks like I need to dig in the code anyhow, I am not the author of the
module to know by heart what is inside -- just need some spare time when
I get to the office, not easy to set a testbed wh
Somehow I couldn't follow exactly the issue. Maybe you can paste here a
sip network trace for the issue and present what is the desired
behaviour. Then maybe we can provide some hints on how to solve it.
Cheers,
Daniel
On 14/01/16 20:13, McConnachie, Alex wrote:
>
> I am stumped as my DID provide
Hello,
changing the R-URI (sip address in the first line of request) can be
done with varables:
- $ru - the entire r-uri
- $rd - only the domain part of r-uri
Cheers,
Daniel
On 14/01/16 23:25, Ryan Mottley wrote:
> Hi,
>
> We're running a system with Kamailio running in front of Asterisk ju
It does it when the value is taken from override_lifetime, if that's what you
mean. The override_lifetime value has been set sufficiently high such that a
refresh is not required because calls on our platform cannot last more than 4
hours.
Phil Lavin
Telecoms Systems Manager
CloudCall by SYNET
Hello,
since the first announcement was more about discovering the interest, I
am following up now with the note to say that the event is going to take
place, having already a rather consistent number of interested people.
Everything on site is reserved, courtesy of Kamailio friends from
Alicante
On 26/01/16 12:54, Phil Lavin wrote:
>
> Sorry, correction – desired expires is always 1 second LESS than expires.
>
Is this above happening when taking it from the dialog module value?
Cheers,
Daniel
>
>
>
>
>
> Phil
>
>
>
> *From:*Phil Lavin
> *Sent:* 26 January 2016 11:54
> *To:* 'mico
Hi,
The log_facility for acc is LOG_DAEMON by default -
http://www.kamailio.org/docs/modules/4.3.x/modules/acc.html#acc.p.log_facility
I have changed it to LOCAL1:
modparam("acc", "log_facility", "LOG_LOCAL1")
And have the main logs as LOCAL0:
log_facility=LOG_LOCAL0
This is then distributed
Hello,
so practically all registration appear to come from 127.0.0.1:xyz, where
xyz is some port value.
My guess is that the connection to the tcp proxy is cut and the kamailio
tries to open one.
Is the tcp proxy routing traffic to other apps? Why not using another
Kamailio that does bridging fr
Hello,
can you check the acc module parameters, I think there is one for
setting the syslog facility as well.
Cheers,
Daniel
On 26/01/16 16:19, Yasin CANER wrote:
> Hello;
>
> Kamailio V4.3 is configured with syslog for loggin. Acc message as
> below writes to message but not kamailio.log te
The spec for building the package is on opensuse build service, the part
related to dependencies to mysql package is at:
https://build.opensuse.org/package/view_file/home:kamailio:v4.3.x-rpms/kamailio43/kamailio.spec?expand=1
line 429.
Although I maintain that build project, I am not a user of r
I tried both and both failed. They both asked for mysql-lib.
RHEL 5 didn't ship with mysql-lib, but it did have mysql55-mysql-libs.
2016-01-26 0:06 GMT-08:00 Daniel-Constantin Mierla :
> Interesting, the package should have not built if the dependencies are not
> met.
>
> In the subject you ment
Hello;
Kamailio V4.3 is configured with syslog for loggin. Acc
message as below writes to message but not kamailio.log text as
specified. Here is debugging and logging configuration. Could you
check it please. Why dont write acc message to kamailio.log
Hi Daniel, thanks for quick reply!
e.g.
10.100.1.24 - sip phone
10.100.1.85 - server
- sip phone is configured to register to 10.100.1.85:443
- tcp proxy listen on 443
- when SIP request comes, tcp proxy open connect to Kamailio 127.0.0.1:5061,
and send request there
- tcp proxy does not modify s
Sorry, correction - desired expires is always 1 second LESS than expires.
Phil
From: Phil Lavin
Sent: 26 January 2016 11:54
To: 'mico...@gmail.com' ; Kamailio (SER) - Users Mailing
List
Cc: Telco Team
Subject: RE: [SR-Users] Strange PUA Behaviour
Hi Daniel,
Not setting the lifetime does ind
Hi Daniel,
Not setting the lifetime does indeed take the expiry from the dialog but the
mechanism that refreshes the expiry when the call is ongoing does not run
unless max_expires time is less than the lifetime. This seems to be because of
the below code in pua.c:
if((p->desired_expires> p->e
Hello,
the pending write message is due to asynchronous tcp -- practically,
even if the tcp connection is not ready, the SIP routing process is not
blocked.
If the connection is found or the connection was setup quickly, then is
not a risk of blocking and the message is sent immediately.
I guess
Hello,
can you make a diagram of how the tcp proxy is involved in the sip
traffic routing? From where it receives the traffic and where it sends
it? Does it open connections towards kamailio?
Kamailio is using source IP and port at the moment of opening the tcp
connection to identify the tcp conn
Hello,
thanks to tackling this further ... see my comments inline...
On 26/01/16 11:46, Phil Lavin wrote:
>
> We now have something of a resolution to this. Config is below. The
> key differences are:
>
>
>
> · pua – db_mode set to 0. This stops multiple states for a
> single dialog (ea
Hi Phil,
sorry, couldn't get the time to analyze the pcap, but I still want to do
it and sort it out, being in my short list, just that some higher
priority events, not necessary related to work, squeezed my spare time a
lot.
Cheers,
Daniel
On 22/01/16 14:19, Phil Lavin wrote:
>
> Hi Daniel,
>
>
We now have something of a resolution to this. Config is below. The key
differences are:
* pua - db_mode set to 0. This stops multiple states for a single
dialog (early, trying, confirmed and terminated) from showing in the presentity
table. I suspect this is a bug?
* pua_dial
Hi folk!
Have a rare issue with tls connections.
Have a server with 100+ active tls connections, that are connected to
separate TCP proxy, that listen on port 443.
TCP proxy send sip traffic to Kamailio via localhost:5061. In this way all
connections in Kamailio are considered from Localhost.
I
Interesting, the package should have not built if the dependencies are
not met.
In the subject you mention kamailio-mysql-4.2.7-3.1.x86_64 but then the
link is for kamailio-mysql-4.3.4-2.1.x86_64.rpm -- which is the one you
actually used?
Can you provide the commands you used while attempting to
28 matches
Mail list logo
