Vikram Ragukumar wrote:
>
> Daniel,
>
> Thank you for your response.
>
> We have verified that it is indeed a bug with VoipSwitch. We uninstalled
> the older version (v2.0.0965) of VoipSwitch that we were running and
> replaced it with a newer version (v2.985), and the problem went away.
>
>
hi guys,
it is my first time to use XCAP, i want to implement XCAP server to support
maybe huge amount of user accesses (as cloud solution), so far, i can find
out three XCAP server solution:
1. openSER with XCAP Server Module
http://kamailio.org/docs/modules/devel/modules_k/xcap_server.html
2.
Daniel-Constantin Mierla writes:
> seems to be related to tcp connection management. Do you get the
> messages all the time? Or they appear and disappear from time to time?
there were 1 GBs of them one night and the user restarted kamailio. i
have asked for more info, i.e., what came to syslog
The answer is YES. The setup you talk about requires a little work on the
routing domain, but with Kamailio and RTPProxy you'll be fine.
On Tue, Dec 4, 2012 at 8:00 PM, Zero Aggression <
zeroaggress...@googlemail.com> wrote:
> hanks so muc
___
SIP Expre
Hello,
I am a bit new to VoIP, and I just need a quick yes/no (and maybe pointers)
answer.
Is the following possible (and smart) to do with Kamailio?
Kamailio server. Dual-homed (internal network, Internet).
Internal users connect to Kamailio to make calls to internal and Internet
SIP peers. Users
Hi,
I notice that under my /tmp folder there are openser_receiver filles as
well (kamailio_fifo and kamailio_ctl are know)
Version is 3.3.2 latest branch.
Any ideas?
Thanks,
Uri
___
SIP Express Router (SER) and Kamailio (OpenSER) - sr-users mailing
Hi Alexandr,
thanks, that seems to have fixed it. But I am curious, why should having
TLS enabled cause kamailio to crash in this configuration?
Owen
On 3 December 2012 22:27, Alexandr Dubovikov wrote:
> Hi Owen,
>
> you don't need TLS for sip capturing, please undef WITH_TLS and try again,
>
On 12/4/12 6:43 PM, Daniel Tryba wrote:
On Tuesday 04 December 2012 17:49:43 Daniel-Constantin Mierla wrote:
The only difference is that there is no error in syslog since the uac_*
commands aren't executed a second time. The second subscribe will not be
rewritten when restore mode is either man
On Tuesday 04 December 2012 17:49:43 Daniel-Constantin Mierla wrote:
> > The only difference is that there is no error in syslog since the uac_*
> > commands aren't executed a second time. The second subscribe will not be
> > rewritten when restore mode is either manual or auto if uac_* are
> > con
Hello,
On 11/30/12 3:42 PM, Daniel Tryba wrote:
On Friday 30 November 2012 09:42:11 Daniel-Constantin Mierla wrote:
I'm trying to get the MWI indicator on endpoints to work by redirecting
the SUBSCRIBE to the voicemail server (asterisk) using
usc_replace_(to|from). This works fine for the initi
Hello,
I was looking to the patch and I spotted that you didn't assign anymore
a value to he variable -- next is the specific part of the diff:
- /* fallback to normal srv lookup */
- he=srv_sip_resolvehost(name, 0, port, proto, 0, 0);
+ /* fallback to srv lookup */
+ n
Hello,
only several algorithms are suitable for full stateless usage, I am
mainly referring to those doing hashes over attributes of the sip
message (like hash over call id).
For the other you would need to use tm module and t_relay(). That will
make it easy for you.
Otherwise, you can use
Hello,
seems to be related to tcp connection management. Do you get the
messages all the time? Or they appear and disappear from time to time?
Cheers,
Daniel
On 12/3/12 11:51 PM, Juha Heinanen wrote:
any idea what could be the cause for lots of these kind syslog messages:
Dec 3 23:11:36 si
Hi,
My Kamalio development version works very well with websocket and webrtc
clients.
But when I try to call the guy in remote area (he had connected to the same
server with 3G dongle) no voice and video.
Here is how I have set it up.
1. Kamailio 3.4 development version running on public IP
2. NAT
Hello,
based on community interaction, development, package distributions and
documentation maintenance in the recent years, the default flavour has
been switched now to 'kamailio'.
As written in my previous email, we started the last phase to complete
the integration between kamailio-ser, a
Hello,
we plan to start the last phase of integration between kamailio and ser.
After about 4 years with same source code tree, there is still some
overhead caused by several duplicated modules. Following the decision to
go on with the most developed components and absorb the missing features
16 matches
Mail list logo
