hello ,
w have PBX gateway along with kamailio. all calls are routed to pbx
extensions. but if it happens to be an IP extrension we want the
kamailio to handle the speech without keeping the PBX channel busy.
if its an analog extension then this channel can be busy but if its
IP ex
Dne 12.2.2013 23:21, Mino Haluz napsal(a):
You have to figure it somehow with adjusting the python code of
media-dispatcher. We have developed special "/etc/init.d/kamailio
grace" command, which waits for the moment, when there are no calls,
so it can be restarted. It queries mediaproxy every s
On Tue, Feb 12, 2013 at 7:53 PM, Vinay V wrote:
> Hi All,
>
> I am in process of integrating lync 2010 with openfire xmpp server.
>
> Reading some of the blogs on kamailio found that it can be done using
> kamailio.
>
> Hence request if some body has done this please provide your inputs.
>
> Rega
Good morning Vinay.
I had this experience 1 year ago, so maybe Microsoft has improved something or
our client has discovered new functionality.
Calling from Lync Server to Outside.
1.- You need to modparam("rr", "enable_full_lr", 0) just to avoid Loose Router
parameter in this way "lr=on" and
I'm sorry Vinay.
I read it quickly so everything I've written is for just SIP calls purpose (no
xmpp server experience).
Regards.
--
Eduardo Lejarreta.
-Mensaje original-
De: Eduardo Lejarreta [mailto:lejarret...@sarenet.es]
Enviado el: miércoles, 13 de febrero de 2013 13:14
Para: 'v
I don't understand how this happens, hopefully somebody know why??
When the BYE is sent to Kamailio, it forwards to an incorrect address.
This address is only in dispatcher, so I don't understand how it gets to that?
U 192.168.9.130:5060 -> 4.55.10.163:5060
SIP/2.0 200 OK..Via: SIP/2.0/UDP
No records in acc table.
I usually grep logs, so I never noticed.
That's not good.
Feb 13 14:17:08 psbcpr002 kamailio: DEBUG: [cfg.y:1772]: loading module
acc.so
Feb 13 14:17:08 psbcpr002 kamailio: DEBUG: [sr_module.c:564]:
load_module: trying to load
Feb 13 14:17:08 psbcpr002 /usr/sbin/kama
Hello,
$shv(...) is referred as shared memory variable because it stores the
value in shared memory. That means if you set $shv(x) in one process,
you can read its value from another process. You have to be sure you
don't have races in setting the variable, that could be achieved with
locks f
