No help at all?
It would be a good start point a doc to read concern this aspect.
Of course, an example based on the conf could me help a lot better.
Thank's to all!
Simon
Il 06/05/2011 10:40, Simone Felici ha scritto:
Hello to all!
I need a little help with our ser installation
Hi,
did you look at the manuals?
You must simply issue a rtpproxy_offer/_answer to engage the RTPProxy
from your route/reply_route, as described in the manual:
http://www.kamailio.org/docs/modules/devel/modules/rtpproxy.html#id3056341
Carsten
2011/5/9 Simone Felici s.fel...@mclink.eu:
No help
Hello,
I'll start from here and set-up a scenario to test it out.
Is it compatible with ser-2.0.0-rc1 used by me?
Thank's for the answer.
Simon
Il 09/05/2011 10:28, Carsten Bock ha scritto:
Hi,
did you look at the manuals?
You must simply issue a rtpproxy_offer/_answer to engage the
Hi Simone,
it should be similar for SER 2.0.
The commands may be different though, so you probably do one of the following:
- upgrade to a more recent SER version
- check the readme for your version (should be in modules/nathelper directory)
Carsten
2011/5/9 Simone Felici s.fel...@mclink.eu:
Hi Carsten,
The upgrade is something I would like to do very! But at the moment there are so many customizations
on the structure. Could be maintained, but the work sould be almost long. I search to understand if
at least this command is implemented and then look forward.
Meanwhile many
Am 07.05.2011 01:03, schrieb Eric Hiller:
The only downside is now to add a new gateway involved editing the
config file and reloading kamailio. At some point I could put this in
SQL and just update the gateways daily ie. DASH.
you could store IP adresses in database tables of LCR module and
Am 08.05.2011 23:51, schrieb Pierpaolo Culurciello:
I
tried to analize the two flows of SIP messages but I didn't notice any
difference between them so I can't understand why Kamailio is not able
to register.
Take a look at the CSeq Header.
From readme:
Known limitations in this version:
Hello all,
Have this issue with my ser config. I try to load a fwdbusy value from db
using the $fu class, but it's complaining..
config:
...
if (avp_db_load($fu, s:fwdbusy)) {
...
log:
0(20749) ERROR: core [pvapi.c:516]: error searching pvar fu
0(20749) ERROR: core [pvapi.c:720]:
Hello,
the avpops module is now the one coming via kamailio development.
First, you have to load modules_k/pv.so module (to get $fu), then the
second parameter has to be PV format as well, e.g.,: $avp(fwdbusy)
(note: s: is optional now in the name of the avps, if it is missing then
the name
I recently interconnected to an upstream carrier using Kamailio 3.0,
working fine. We have configure 2 SIP trunks for failover/redundnacy.
I'm using dispatcher module to round robin calls to the carrier. I
wanted to monitor trunk usage between us. I was reading in the devel
3.2 about
Great, thank you.
BTW, is going to be deprecated the module_s/avp_db module (functions
like load_attrs, load_extra_attrs, etc)?
From the avp_db/README file:
...You may also want to check the avpops module which is more flexible and
contains more functions. In future SER releases the avp module
Hi All,
I'm trying to configure the dialog module with profiles for outbound
calls to different Dispatcher domains. I can get the dialog module
configured for inbound calls and pull statistics and separate calls
into specific profiles, that part is working well.
The problem I am having
I'm trying to configure the dialog module with profiles for outbound
calls to different Dispatcher domains. I can get the dialog module
configured for inbound calls and pull statistics and separate calls
into specific profiles, that part is working well.
The problem I am having specifically
On 05/09/2011 07:16 PM, JR Richardson wrote:
The problem I am having specifically is for outbound calls flowing
through a dispatcher, I want to separate calls into a profile for each
SIP domain that I send calls to. I'm not sure how do accomplish this.
I see in kamctl fifo dlg_list, there is
14 matches
Mail list logo
