I added the define and recompiled. still got the same error. Here is the
change that I've made:
#define __OS_solaris 1 //* this is the line that i've added
#ifdef __OS_solaris
typedef uint8_t u_int8_t;
typedef uint16_t u_int16_t;
#define IPPROTO_IPIP IPPROTO_ENCAP /* Solaris IPIP protocol
Thank you for your replies.
How the Q value is defined?
-Message d'origine-
De : sr-users-boun...@lists.sip-router.org
[mailto:sr-users-boun...@lists.sip-router.org] De la part de Alex Balashov
Envoyé : vendredi 15 juin 2012 17:43
À : sr-users@lists.sip-router.org
Objet : Re: [SR-Users] C
Newer versions support serial forking through contacts.
On 06/15/2012 11:36 AM, Igor Potjevlesch wrote:
I don't want to do forking to multiple contact simultaneously. I want to try
with a first contact and try with the second one if the call goes to failure
route.
-Message d'origine-
D
Hello,
On 6/15/12 5:26 PM, Alex Balashov wrote:
On 06/15/2012 11:19 AM, Igor Potjevlesch wrote:
Hi all,
I’m facing a problem with multiple contact in ‘location’ table with the
same ‘username’.
The idea is to rewrite R-URI with 1 contact and if there is no answer or
SIP 5xx, try with the secon
I don't want to do forking to multiple contact simultaneously. I want to try
with a first contact and try with the second one if the call goes to failure
route.
-Message d'origine-
De : sr-users-boun...@lists.sip-router.org
[mailto:sr-users-boun...@lists.sip-router.org] De la part de Alex
On 06/15/2012 11:19 AM, Igor Potjevlesch wrote:
Hi all,
I’m facing a problem with multiple contact in ‘location’ table with the
same ‘username’.
The idea is to rewrite R-URI with 1 contact and if there is no answer or
SIP 5xx, try with the second.
Is that make sense? I use SER0.9.9.
Why on e
HI
I just did simple test-case: add user and delete user on kamailio 3.3
on 101 , I added 103, the watcher tables shows:
select * from watchers;
+++--++--+++---+
| id | presentity_uri
Hi all,
I'm facing a problem with multiple contact in 'location' table with the same
'username'.
The idea is to rewrite R-URI with 1 contact and if there is no answer or SIP
5xx, try with the second.
Is that make sense? I use SER0.9.9.
Regards,
Igor.
_
El Fri, 15 Jun 2012 17:06:51 +0200
Jon Bonilla (Manwe) escribió:
> El Fri, 15 Jun 2012 16:49:51 +0200
> Klaus Darilion escribió:
>
> > SRV may be troublesome if customers can use any SIP clients. Some SIP
> > clients really have a strange SRV implementation (eg. some make SRV
> > lookup for e
El Fri, 15 Jun 2012 16:49:51 +0200
Klaus Darilion escribió:
> SRV may be troublesome if customers can use any SIP clients. Some SIP
> clients really have a strange SRV implementation (eg. some make SRV
> lookup for every request, thus reREGISTER can end up at another proxy).
>
Kamailio for e
SRV may be troublesome if customers can use any SIP clients. Some SIP
clients really have a strange SRV implementation (eg. some make SRV
lookup for every request, thus reREGISTER can end up at another proxy).
regards
Klaus
On 15.06.2012 15:37, Uriel Rozenbaum wrote:
Hey guys,
I'm trying to
Hey guys,
I'm trying to plan a deployment for a couple thousands of users. As we are
facing now some issues for scaling, I'd like to make a modular architecture
in order to add a server when needed.
I was thinking about N+1 Kamailio Proxies to Register customers and handle
the border of the netwo
Thanks a lot.
On Fri, Jun 15, 2012 at 4:31 PM, Olle E. Johansson wrote:
>
> 15 jun 2012 kl. 05:56 skrev Jakson Kalsson:
>
> >
> >
> > Hi all, I have a project for the 3G related, AMR and AMR-WB support.
> >
> > I'm using the client develop suite from the PortSIP(
> http://www.portsip.com), as th
HI
I am testing the following case in the kamailio 3.3 presence server,
all are in 192.168.122.0 network
101 (bria, ip:.224) - kamailiops( ip:.32) --- 103 (
jitsi, ip:.1)
on 101 I added 103 in the contact list, 101 <-> 103 can see each
other,
Then on 101, I
happy coding, Vicente!
Samuel
On 15 June 2012 10:58, Konstantin M. wrote:
> Welcome, Vicente.
>
> I'm happy about to redis news!
>
>
> 2012/6/15 Vicente Hernando
>
>> Many thanks for the welcome!
>>
>> My current plans about ndb_redis module focus on creating an useful API
>> so to export some
Welcome, Vicente.
I'm happy about to redis news!
2012/6/15 Vicente Hernando
> Many thanks for the welcome!
>
> My current plans about ndb_redis module focus on creating an useful API
> so to export some functions to other modules.
>
> Then we are thinking here about creating a simpler dialplan
Many thanks for the welcome!
My current plans about ndb_redis module focus on creating an useful API
so to export some functions to other modules.
Then we are thinking here about creating a simpler dialplan module based
on redis. We will be glad to share it with the community, and every
fee
2012/6/15 Daniel-Constantin Mierla :
> I am introducing Vicente as a new registered developer - he submitted lately
> very useful patches to ndb_redis module (e.g., array support in replies,
> redis free function for config), new ones being on the pipe -- he can
> present better his plans or you ju
15 jun 2012 kl. 08:44 skrev Daniel-Constantin Mierla:
> Hello,
>
> I am introducing Vicente as a new registered developer - he submitted lately
> very useful patches to ndb_redis module (e.g., array support in replies,
> redis free function for config), new ones being on the pipe -- he can pre
15 jun 2012 kl. 05:56 skrev Jakson Kalsson:
>
>
> Hi all, I have a project for the 3G related, AMR and AMR-WB support.
>
> I'm using the client develop suite from the PortSIP(http://www.portsip.com),
> as their said
> support the AMR, AMR-WB with RFC4867.
>
> Now I have to setup a SIP server
20 matches
Mail list logo
