Re: [SR-Users] kamailio does not start with db_mongdb and usrloc

[Daniel-Constantin Mierla]

Hello,

can you try with latest master branch or apply the patch from the next
commit to your branch?

  *
https://github.com/kamailio/kamailio/commit/d50498cf483cd22ac4e62af5aaa86fc27654f640

If possible, test it with both mongo server versions and if works fine
with both, then I am going to backport.

Cheers,
Daniel


On 28.02.18 18:49, Stephane wrote:
> Hello Daniel,
>
> I tried with mongoc 1.8.0 (the trace I have sent) and also mongoc
> 1.9.2. The result is the same : a "failed to parse" with as indication
> "unrecognized field 'table_version'" when using mongo server version
> 3.6.2.
>
> Both mongoc versions are running fine with a mongo server version 3.0.15.
>
> Kind regards,
> Stephane
>
>  
>
>
> On 28 February 2018 at 15:25, Daniel-Constantin Mierla
> > wrote:
>
> Hello,
>
> I see in the pcap that the returned error contains:
>
> Failed to parse: { find: "version", filter: { table_name:
> "location" }, table_version: 1, $readPreference: { mode:
> "secondaryPreferred" }, $db: "kamailio" }. Unrecognized field
> 'table_version'.
>
> What is the version of mongoc library? I tried to quick search on
> google and found a similar report :
>
>   - https://github.com/mongodb/mongo-php-driver/issues/516
> 
>
> On the other hand, it works with same lib but for different
> versions of mongo server ... so might be something different.
>
> Cheers,
> Daniel
>
>
> On 27.02.18 11:26, Stephane wrote:
>> Hello Daniel,
>>
>> You will find two pcap files in attachment. I am using the same
>> mongoc library version in both cases.
>> Let me know if you need more info.
>>
>> Kind regards,
>> Stephane
>>
>> On 27 February 2018 at 09:01, Daniel-Constantin Mierla
>> > wrote:
>>
>> Hello,
>>
>> can you send here the requests sent by kamailio for the two
>> mongodb versions? To compare and see where it can be fixed.
>>
>> Also, were you using the same mongoc library version in both
>> cases?
>>
>> Cheers,
>> Daniel
>>
>>
>> On 26.02.18 12:57, Stephane wrote:
>>> Hello,
>>> I made some additional tests. 
>>> The problem is only present when kamailio is facing mongo
>>> release 3.2 (or higher). 
>>> With mongo version 3.0 (or lower), the request sent by
>>> kamailio is different: it contains $query and $table_version
>>> elements and mongo accepts it.
>>> Kind regards,
>>> Stephane
>>>
>>> On 23 February 2018 at 10:48, Stephane
>>> > wrote:
>>>
>>> Hello Daniel,
>>>
>>> I took a pcap trace. And I see the following in the
>>> answer sent by mongo
>>>
>>> Failed to parse: { find: "version", filter: {
>>> table_name: "location" }, table_version: 1, $db:
>>> "kamailio", $readPreference: { mode: "primaryPreferred"
>>> }, $clusterTime: { clusterTime: Timestamp(1519379980,
>>> 1), signature: { hash: BinData(0,
>>> ), keyId: 0 } }
>>> }. Unrecognized field
>>> 
>>> 'table_version'.codecodeNameFailedToParseoperationTimeZ$clusterTimeXclusterTimeZsignature3hashkeyId
>>>
>>> Kind regards,
>>> Stephane
>>>
>>> On 23 February 2018 at 09:39, Daniel-Constantin Mierla
>>> > wrote:
>>>
>>> Hello,
>>>
>>> I don't know if you can see the result sent back by
>>> mongodb in its logs, it doesn't show it there. Maybe
>>> you can sniff the traffic on the network and see if
>>> mongodb sends the proper response back. Kamailio
>>> logs like nothing was retrieved.
>>>
>>> Cheers,
>>> Daniel
>>>
>>>
>>> On 22.02.18 18:02, Stephane Focant wrote:
 Hello,
 I have an issue when I try to use kamailio 5.1 with
 usrloc and db_mongdb modules.
 When I try to start kamailio, I get the following
 error:

 0(22216) DEBUG:  [db.c:314]: db_do_init2():
 connection 0x7f735b5c4100 not found in pool
  0(22216) DEBUG: db_mongodb
 [mongodb_connection.c:55]:
 db_mongodb_new_connection(): connection open to:
 mongodb://10.0.12.149
 
 ,10.0.12.150,10.0.12.151/kamailio?replicaSet=sre_location=true=primaryPreferred
 
 

Re: [SR-Users] kamailio does not start with db_mongdb and usrloc

[Stephane]

Hello Daniel,

I tried with mongoc 1.8.0 (the trace I have sent) and also mongoc 1.9.2.
The result is the same : a "failed to parse" with as indication
"unrecognized field 'table_version'" when using mongo server version 3.6.2.

Both mongoc versions are running fine with a mongo server version 3.0.15.

Kind regards,
Stephane




On 28 February 2018 at 15:25, Daniel-Constantin Mierla 
wrote:

> Hello,
>
> I see in the pcap that the returned error contains:
>
> Failed to parse: { find: "version", filter: { table_name: "location" },
> table_version: 1, $readPreference: { mode: "secondaryPreferred" }, $db:
> "kamailio" }. Unrecognized field 'table_version'.
>
> What is the version of mongoc library? I tried to quick search on google
> and found a similar report :
>
>   - https://github.com/mongodb/mongo-php-driver/issues/516
> On the other hand, it works with same lib but for different versions of
> mongo server ... so might be something different.
>
> Cheers,
> Daniel
>
>
> On 27.02.18 11:26, Stephane wrote:
>
> Hello Daniel,
>
> You will find two pcap files in attachment. I am using the same mongoc
> library version in both cases.
> Let me know if you need more info.
>
> Kind regards,
> Stephane
>
> On 27 February 2018 at 09:01, Daniel-Constantin Mierla 
> wrote:
>
>> Hello,
>>
>> can you send here the requests sent by kamailio for the two mongodb
>> versions? To compare and see where it can be fixed.
>>
>> Also, were you using the same mongoc library version in both cases?
>>
>> Cheers,
>> Daniel
>>
>> On 26.02.18 12:57, Stephane wrote:
>>
>> Hello,
>> I made some additional tests.
>> The problem is only present when kamailio is facing mongo release 3.2 (or
>> higher).
>> With mongo version 3.0 (or lower), the request sent by kamailio is
>> different: it contains $query and $table_version elements and mongo accepts
>> it.
>> Kind regards,
>> Stephane
>>
>> On 23 February 2018 at 10:48, Stephane  wrote:
>>
>>> Hello Daniel,
>>>
>>> I took a pcap trace. And I see the following in the answer sent by mongo
>>>
>>> Failed to parse: { find: "version", filter: { table_name: "location" },
>>> table_version: 1, $db: "kamailio", $readPreference: { mode:
>>> "primaryPreferred" }, $clusterTime: { clusterTime: Timestamp(1519379980,
>>> 1), signature: { hash: BinData(0, ),
>>> keyId: 0 } } }. Unrecognized field 'table_version'.code
>>> codeNameFailedToParseoperationTimeZ$clusterTimeXclusterTimeZ
>>> signature3hashkeyId
>>>
>>> Kind regards,
>>> Stephane
>>>
>>> On 23 February 2018 at 09:39, Daniel-Constantin Mierla <
>>> mico...@gmail.com> wrote:
>>>
 Hello,

 I don't know if you can see the result sent back by mongodb in its
 logs, it doesn't show it there. Maybe you can sniff the traffic on the
 network and see if mongodb sends the proper response back. Kamailio logs
 like nothing was retrieved.

 Cheers,
 Daniel

 On 22.02.18 18:02, Stephane Focant wrote:

 Hello,
 I have an issue when I try to use kamailio 5.1 with usrloc and
 db_mongdb modules.
 When I try to start kamailio, I get the following error:

 0(22216) DEBUG:  [db.c:314]: db_do_init2(): connection
 0x7f735b5c4100 not found in pool
  0(22216) DEBUG: db_mongodb [mongodb_connection.c:55]:
 db_mongodb_new_connection(): connection open to: mongodb://10.0.12.149
 ,10.0.12.150,10.0.12.151/kamailio?replicaSet=sre_location=tru
 e=primaryPreferred
  0(22216) DEBUG: db_mongodb [mongodb_dbase.c:864]: db_mongodb_query():
 query to collection [version]
  0(22216) DEBUG: db_mongodb [mongodb_dbase.c:898]: db_mongodb_query():
 query filter: { "table_name" : "location" }
  0(22216) DEBUG: db_mongodb [mongodb_dbase.c:917]: db_mongodb_query():
 columns filter: { "table_version" : 1 }
  0(22216) DEBUG:  [db_res.c:120]: db_new_result(): allocate 56
 bytes for result set at 0x7f735b5c4450
  0(22216) DEBUG: db_mongodb [mongodb_dbase.c:746]:
 db_mongodb_store_result(): no result from mongodb
  0(22216) DEBUG:  [db.c:404]: db_table_version(): no row for
 table location found
  0(22216) ERROR:  [db.c:450]: db_check_table_version(): invalid
 version 0 for table location found, expected 9 (check table structure and
 table "version")
  0(22216) ERROR: usrloc [dlist.c:659]: register_udomain(): error during
 table version check.
  0(22216) DEBUG:  [db_pool.c:100]: pool_remove(): removing
 connection from the pool
  0(22216) ERROR: registrar [registrar.c:651]: domain_fixup(): failed to
 register domain
  0(22216) ERROR:  [core/route.c:1154]: fix_actions(): fixing
 failed (code=-1) at cfg:/usr/local/kamailio-5.1/et
 c/kamailio/kamailio.cfg:660
  0(22216) ERROR:  [core/rvalue.c:3860]: fix_rval_expr(): failure
 in cfg at line: 660 col: 22
  0(22216) ERROR:  [core/rvalue.c:3860]: fix_rval_expr(): 

Re: [SR-Users] Trunks with registration

[Daniel Tryba]

On Wed, Feb 28, 2018 at 01:50:20PM +0200, ?? ?? 
wrote:
> - Is it possible to tell Kamailio which transport protocol to use other
> than by configuring auth_proxy column of uacreg table with domain name that
> has SRV record?

Don't know.

> - What are the priorities of different transport protocols in SRV record
> when it is used?

This van be configured with a NAPTR record:

$ host -t NAPTR sip.example.org
sip.example.org has NAPTR record 10 1 "s" "SIP+D2T" "" 
_sip._tcp.sip.example.org.
sip.example.org has NAPTR record 100 1 "s" "SIP+D2U" "" 
_sip._udp.sip.example.org.


___
Kamailio (SER) - Users Mailing List
sr-users@lists.kamailio.org
https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users

Re: [SR-Users] Changing contact header

[Daniel Tryba]

On Wed, Feb 28, 2018 at 04:54:19PM +0530, Cibin Paul wrote:
> In my setup, Kamailio acts as a registration server and route the
> calls to different asterisk boxes. The clients using IPV6 private ip
> and IPV4  public ip address are rejected by the asterisk server. On
> printing the contact header, I am getting the private ip (ipv6). Is
> there a way to change the contact header with public ip in all
> scenarios. I tried updating the contact header as below and
> unfortunately not working. Is there a better way to handle the
> scenario. As of now we don/t have a plan to implement ipv6 network. 

Maybe you could take a look at the topoh or topos modules, they rewrite
the contact header (and more).


___
Kamailio (SER) - Users Mailing List
sr-users@lists.kamailio.org
https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users

Re: [SR-Users] kamailio does not start with db_mongdb and usrloc

[Daniel-Constantin Mierla]

Hello,

I see in the pcap that the returned error contains:

Failed to parse: { find: "version", filter: { table_name: "location" },
table_version: 1, $readPreference: { mode: "secondaryPreferred" }, $db:
"kamailio" }. Unrecognized field 'table_version'.

What is the version of mongoc library? I tried to quick search on google
and found a similar report :

  - https://github.com/mongodb/mongo-php-driver/issues/516

On the other hand, it works with same lib but for different versions of
mongo server ... so might be something different.

Cheers,
Daniel

On 27.02.18 11:26, Stephane wrote:
> Hello Daniel,
>
> You will find two pcap files in attachment. I am using the same mongoc
> library version in both cases.
> Let me know if you need more info.
>
> Kind regards,
> Stephane
>
> On 27 February 2018 at 09:01, Daniel-Constantin Mierla
> > wrote:
>
> Hello,
>
> can you send here the requests sent by kamailio for the two
> mongodb versions? To compare and see where it can be fixed.
>
> Also, were you using the same mongoc library version in both cases?
>
> Cheers,
> Daniel
>
>
> On 26.02.18 12:57, Stephane wrote:
>> Hello,
>> I made some additional tests. 
>> The problem is only present when kamailio is facing mongo release
>> 3.2 (or higher). 
>> With mongo version 3.0 (or lower), the request sent by kamailio
>> is different: it contains $query and $table_version elements and
>> mongo accepts it.
>> Kind regards,
>> Stephane
>>
>> On 23 February 2018 at 10:48, Stephane > > wrote:
>>
>> Hello Daniel,
>>
>> I took a pcap trace. And I see the following in the answer
>> sent by mongo
>>
>> Failed to parse: { find: "version", filter: { table_name:
>> "location" }, table_version: 1, $db: "kamailio",
>> $readPreference: { mode: "primaryPreferred" }, $clusterTime:
>> { clusterTime: Timestamp(1519379980, 1), signature: { hash:
>> BinData(0, ), keyId:
>> 0 } } }. Unrecognized field
>> 
>> 'table_version'.codecodeNameFailedToParseoperationTimeZ$clusterTimeXclusterTimeZsignature3hashkeyId
>>
>> Kind regards,
>> Stephane
>>
>> On 23 February 2018 at 09:39, Daniel-Constantin Mierla
>> > wrote:
>>
>> Hello,
>>
>> I don't know if you can see the result sent back by
>> mongodb in its logs, it doesn't show it there. Maybe you
>> can sniff the traffic on the network and see if mongodb
>> sends the proper response back. Kamailio logs like
>> nothing was retrieved.
>>
>> Cheers,
>> Daniel
>>
>>
>> On 22.02.18 18:02, Stephane Focant wrote:
>>> Hello,
>>> I have an issue when I try to use kamailio 5.1 with
>>> usrloc and db_mongdb modules.
>>> When I try to start kamailio, I get the following error:
>>>
>>> 0(22216) DEBUG:  [db.c:314]: db_do_init2():
>>> connection 0x7f735b5c4100 not found in pool
>>>  0(22216) DEBUG: db_mongodb [mongodb_connection.c:55]:
>>> db_mongodb_new_connection(): connection open to:
>>> mongodb://10.0.12.149
>>> 
>>> ,10.0.12.150,10.0.12.151/kamailio?replicaSet=sre_location=true=primaryPreferred
>>> 
>>> 
>>>  0(22216) DEBUG: db_mongodb [mongodb_dbase.c:864]:
>>> db_mongodb_query(): query to collection [version]
>>>  0(22216) DEBUG: db_mongodb [mongodb_dbase.c:898]:
>>> db_mongodb_query(): query filter: { "table_name" :
>>> "location" }
>>>  0(22216) DEBUG: db_mongodb [mongodb_dbase.c:917]:
>>> db_mongodb_query(): columns filter: { "table_version" : 1 }
>>>  0(22216) DEBUG:  [db_res.c:120]: db_new_result():
>>> allocate 56 bytes for result set at 0x7f735b5c4450
>>>  0(22216) DEBUG: db_mongodb [mongodb_dbase.c:746]:
>>> db_mongodb_store_result(): no result from mongodb
>>>  0(22216) DEBUG:  [db.c:404]: db_table_version():
>>> no row for table location found
>>>  0(22216) ERROR:  [db.c:450]:
>>> db_check_table_version(): invalid version 0 for table
>>> location found, expected 9 (check table structure and
>>> table "version")
>>>  0(22216) ERROR: usrloc [dlist.c:659]:
>>> register_udomain(): error during table version check.
>>>  0(22216) DEBUG:  [db_pool.c:100]: pool_remove():
>>> removing connection from the pool
>>>  0(22216) ERROR: registrar 

Re: [SR-Users] Question on contribution of documentation improvements

[Daniel-Constantin Mierla]

Hello,

thanks for this work!

At the end, it doesn't matter that much with the patches for typos in
the documentation, up to you how do you want to make the pull request
for this case.

I am a proponent of splitting commits per component (like core, modules,
libs, ...) because it is easier to review the patches. I typically check
quickly any patch to core and major modules, for one large patch that is
hard to do in short time and complex to follow up later.

Moreover, for split commits, when it is the case, the backports are
straightforward with git cherry-pick. One large commit is likely to fail
to cherry-pick in stable branch, due to new features in some modules,
etc.., while with split commits, many of them just work.

I also do a lot of 'git log -p src/modules/name' when someone reports a
regression, which is easier to follow if that module had commits only
related to its content.

I don't think this PR is a must to backport, and again, your decision at
the end, but if I would look from the perspective of tracking changes
per component later with 'git log -p ...', then I would do split commits
per component, even it is a large number of affected components.

Cheers,
Daniel


On 28.02.18 14:03, Floimair Florian wrote:
> Hi guys!
>
> While reading through documentation I realized there are a lot of typos 
> (typing errors) and some misspellings so I decided to try to correct them.
> I dit this in all of Kamailios module and lib documentation (the xml in the 
> doc folders) and they turned out to be quite a lot.
> Right now this sits on my fork of kamailo on github, but I would like to get 
> this back into the main repository.
>
> What's puzzling me though, is how to most effectively get this in via a pull 
> request due to the following:
>
> For now I have made a single commit for each module I touched. Therefore 
> quite a lot of commits have accumulated.
> Actually 152 commits in modules and 4 commits in lib.
> Since most of the commits in modules are rather small (ranging from 1 line 
> changed to 4) with only a few having more, I am not sure if that's the way to 
> go to have a single commit for each module.
>
> Therefore I am unsure if a squashed version would be more appropriate. 
> Therefore I created a second branch on my forked repository.
>
> Unsquashed: https://github.com/ffloimair/kamailio/tree/wip-fix-typos
> Squashed: https://github.com/ffloimair/kamailio/tree/wip-fix-typos
>
>
> In total a diff --stat to master results in  205 files changed, 521 
> insertions(+), 521 deletions(-)
>
> So please let me know what would be the wanted (and most efficient) way to 
> proceed.
>
>
>
>
>  
>  
> With best regards
>
> Florian Floimair
> Innovation - Software-Development
>
> COMMEND INTERNATIONAL GMBH
> A-5020 Salzburg, Saalachstraße 51
> Tel: +43-662-85 62 25
> Fax: +43-662-85 62 26
> http://www.commend.com
>
> Security and Communication by Commend
>
> FN 178618z | LG Salzburg
>
>
> ___
> Kamailio (SER) - Users Mailing List
> sr-users@lists.kamailio.org
> https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users

-- 
Daniel-Constantin Mierla
www.twitter.com/miconda -- www.linkedin.com/in/miconda
Kamailio Advanced Training - March 5-7, 2018, Berlin - www.asipto.com
Kamailio World Conference - May 14-16, 2018 - www.kamailioworld.com


___
Kamailio (SER) - Users Mailing List
sr-users@lists.kamailio.org
https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users

[SR-Users] Question on contribution of documentation improvements

[Floimair Florian]

Hi guys!

While reading through documentation I realized there are a lot of typos (typing 
errors) and some misspellings so I decided to try to correct them.
I dit this in all of Kamailios module and lib documentation (the xml in the doc 
folders) and they turned out to be quite a lot.
Right now this sits on my fork of kamailo on github, but I would like to get 
this back into the main repository.

What's puzzling me though, is how to most effectively get this in via a pull 
request due to the following:

For now I have made a single commit for each module I touched. Therefore quite 
a lot of commits have accumulated.
Actually 152 commits in modules and 4 commits in lib.
Since most of the commits in modules are rather small (ranging from 1 line 
changed to 4) with only a few having more, I am not sure if that's the way to 
go to have a single commit for each module.

Therefore I am unsure if a squashed version would be more appropriate. 
Therefore I created a second branch on my forked repository.

Unsquashed: https://github.com/ffloimair/kamailio/tree/wip-fix-typos
Squashed: https://github.com/ffloimair/kamailio/tree/wip-fix-typos


In total a diff --stat to master results in  205 files changed, 521 
insertions(+), 521 deletions(-)

So please let me know what would be the wanted (and most efficient) way to 
proceed.




 
 
With best regards

Florian Floimair
Innovation - Software-Development

COMMEND INTERNATIONAL GMBH
A-5020 Salzburg, Saalachstraße 51
Tel: +43-662-85 62 25
Fax: +43-662-85 62 26
http://www.commend.com

Security and Communication by Commend

FN 178618z | LG Salzburg


___
Kamailio (SER) - Users Mailing List
sr-users@lists.kamailio.org
https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users

Re: [SR-Users] cnxcc module - make auth for redis connection

[Daniel-Constantin Mierla]

Hello,

maybe authentication support was not implemented in cnxcc. Eventually it
can be extracted from the ndb_redis, that module has it implemented already.

  *
https://www.kamailio.org/docs/modules/stable/modules/ndb_redis.html#ndb_redis.p.server

Cheers,
Daniel


On 27.02.18 14:39, Donat Zenichev wrote:
> Nevertheless, I want to find the needed solution.
> In my opinion - If module is able to connect to redis databases, it'd
> better to perform it with authentication.
>
> Because, there are cases when db located on localhost is improper
> solution or other users mustn't see hkeys, amounts inside hkeys it etc.
> So I think no one will be mind, to have whole possibility - real-time
> billing (cnxcc) working with redis securely.
>
> So please don't be apathetic to my request.
>
> 2018-02-26 9:44 GMT+02:00 Donat Zenichev  >:
>
> Hi community.
> This message is specially dedicated to developers of the kamailio
> project.
>
> I need to find solution how to make authentication for connections
> of cnxcc with redis.
> For that moment, cnxcc module is able to connect to redis only
> without password (Carlos Ruiz Díaz will add this possibility later?).
> So that, this makes database vulnerable.
>
> Well, furthermore I don't want to use local redis database, cuz I
> think machine that contains kamailio daemon, must perform just
> this kind of actions - SIP proxying (kamailio server is not to be
> a database server or anything else).
>
> For that moment we use separate redis db for cases like that, but
> this is not best practice I think.
> I already tried to find solution (for e.g. connections via another
> module like db_redis:
> https://github.com/kamailio/kamailio/pull/1432
> ) but I got advice
> - achieving my goal by sr-users mailing list.
>
> Please pay attention for my request. I think this will be very
> helpfull for others.
>
>
>
> -- 
> -- 
> BR, Donat Zenichev
> Wnet VoIP team
> Tel Ukraine:  +380(44) 5-900-800
> Tel USA: +164(67) 8-174-17 (ext 1320)
> https://w-net.us/ 
>
>
>
>
> -- 
> -- 
> BR, Donat Zenichev
> Wnet VoIP team
> Tel Ukraine:  +380(44) 5-900-800
> Tel USA: +164(67) 8-174-17 (ext 1320)
> https://w-net.us/ 
>
>
> ___
> Kamailio (SER) - Users Mailing List
> sr-users@lists.kamailio.org
> https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users

-- 
Daniel-Constantin Mierla
www.twitter.com/miconda -- www.linkedin.com/in/miconda
Kamailio Advanced Training - March 5-7, 2018, Berlin - www.asipto.com
Kamailio World Conference - May 14-16, 2018 - www.kamailioworld.com

___
Kamailio (SER) - Users Mailing List
sr-users@lists.kamailio.org
https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users

Re: [SR-Users] kamailio 5.1 compilation error

[Daniel-Constantin Mierla]

Hello,

I added g++ in the tutorial -- iirc, in the past c++ compiler was
installed by default with gcc package, but I noticed also that with
latest distros it is separate package:

  *
http://kamailio.org/docs/tutorials/5.1.x/kamailio-install-guide-git/#prerequisites

g++ is needed by some modules that link to C++ libraries, such as
app_sqlang, phonenum or ndb_cassandra.

Cheers,
Daniel


On 27.02.18 15:21, Aqs Younas wrote:
> Sorry guys, I have been strictly following below guide for the
> installation. 
>
> https://kamailio.org/docs/tutorials/5.1.x/kamailio-install-guide-git/
>
> Feeling dumb I should have searched it before. After installing g++
> issue is resolved. 
>
> Thanks, everyone. 
>
> On 27 February 2018 at 19:17, Rinor Hoxha  > wrote:
>
> Hi Aqs,
>
> Add app_sqlang to skip_modules if you do not need it.
>
> example: (tune it to your needs)
>
> make PREFIX="/usr/local/kamailio" include_modules="db_mysql
> dialplan app_lua" skip_modules="app_jsdt app_perl app_python
> *app_sqlang*" cfg
>
> Br, Rinor
>
>
> On 02/27/2018 03:04 PM, Aqs Younas wrote:
>> Greetings list, 
>>
>> I am trying to install Kamailio 5.1 from source code on
>> Debian 8.10. But It is failing with below error. Don't know what
>> could be wrong. 
>>
>> Any suggestion is much appreciated. Thanks. 
>>
>>
>> make --no-print-directory -C ./squirrel/squirrel SQMARCH64="-m64"
>> CC_EXTRA_FLAGS="-fPIC" \
>>         OUT="../../libsquirrel.a" sq64
>> gcc -O2 -m64 -D_SQ64 -fno-exceptions -fno-rtti -Wall
>> -fno-strict-aliasing -c sqapi.cpp sqbaselib.cpp sqfuncstate.cpp
>> sqdebug.cpp sqlexer.cpp sqobject.cpp sqcompiler.cpp sqstate.cpp
>> sqtable.cpp sqmem.cpp sqvm.cpp sqclass.cpp -I../include -I.
>> -Iinclude -fPIC
>> gcc: error trying to exec 'cc1plus': execvp: No such file or
>> directory
>> gcc: error trying to exec 'cc1plus': execvp: No such file or
>> directory
>> gcc: error trying to exec 'cc1plus': execvp: No such file or
>> directory
>> gcc: error trying to exec 'cc1plus': execvp: No such file or
>> directory
>> gcc: error trying to exec 'cc1plus': execvp: No such file or
>> directory
>> gcc: error trying to exec 'cc1plus': execvp: No such file or
>> directory
>> gcc: error trying to exec 'cc1plus': execvp: No such file or
>> directory
>> gcc: error trying to exec 'cc1plus': execvp: No such file or
>> directory
>> gcc: error trying to exec 'cc1plus': execvp: No such file or
>> directory
>> gcc: error trying to exec 'cc1plus': execvp: No such file or
>> directory
>> gcc: error trying to exec 'cc1plus': execvp: No such file or
>> directory
>> gcc: error trying to exec 'cc1plus': execvp: No such file or
>> directory
>> Makefile:51: recipe for target 'sq64' failed
>> make[3]: *** [sq64] Error 1
>> Makefile:44: recipe for target 'libsquirrel.a' failed
>> make[2]: *** [libsquirrel.a] Error 2
>> Makefile:511: recipe for target 'modules' failed
>> make[1]: *** [modules] Error 1
>> make[1]: Leaving directory '/usr/src/kamailio/src'
>> Makefile:27: recipe for target 'all' failed
>> make: *** [all] Error 2
>>
>>
>> Br, Aqs. 
>>
>>
>> ___
>> Kamailio (SER) - Users Mailing List
>> sr-users@lists.kamailio.org 
>> https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users
>> 
>
>
> ___
> Kamailio (SER) - Users Mailing List
> sr-users@lists.kamailio.org 
> https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users
> 
>
>
>
>
> ___
> Kamailio (SER) - Users Mailing List
> sr-users@lists.kamailio.org
> https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users

-- 
Daniel-Constantin Mierla
www.twitter.com/miconda -- www.linkedin.com/in/miconda
Kamailio Advanced Training - March 5-7, 2018, Berlin - www.asipto.com
Kamailio World Conference - May 14-16, 2018 - www.kamailioworld.com

___
Kamailio (SER) - Users Mailing List
sr-users@lists.kamailio.org
https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users

Re: [SR-Users] please downgrade warning message

[Daniel-Constantin Mierla]

On 27.02.18 21:02, Juha Heinanen wrote:
> I noticed this when I start a correctly configured kamailio:
>
> Feb 27 21:55:45 rautu /usr/bin/sip-proxy[29529]: WARNING: registrar 
> [registrar.c:369]: mod_init(): empty reg_xavp_cfg or sock_flag not set -> 
> resetting
>
> Neither of those two are mandatory.  I'm not using registered()
> function.  Please downgrade the message to info or debug level.
>
Done in master and 5.1 branches.

Daniel

-- 
Daniel-Constantin Mierla
www.twitter.com/miconda -- www.linkedin.com/in/miconda
Kamailio Advanced Training - March 5-7, 2018, Berlin - www.asipto.com
Kamailio World Conference - May 14-16, 2018 - www.kamailioworld.com


___
Kamailio (SER) - Users Mailing List
sr-users@lists.kamailio.org
https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users

[SR-Users] Changing contact header

[Cibin Paul]

Hello,

In my setup, Kamailio acts as a registration server and route the calls to 
different asterisk boxes. The clients using IPV6 private ip and IPV4  public ip 
address are rejected by the asterisk server. On printing the contact header, I 
am getting the private ip (ipv6). Is there a way to change the contact header 
with public ip in all scenarios. I tried updating the contact header as below 
and unfortunately not working. Is there a better way to handle the scenario. As 
of now we don/t have a plan to implement ipv6 network. 

$var(p1) = "