date:20130628

Re: [SR-Users] Siremis 4.0 with Kamailio 4.0

2013-06-28 Thread Geoffrey Mina

I have cleaned up the XML/RPC.php error.  Now when I run the MI commands or
the XMLRPC commands they just return blank and it doesn't seem to connect
to the underlying system.


On Fri, Jun 28, 2013 at 4:48 PM, Geoffrey Mina wrote:

> We use Siremis for configuration of our LCR, ACL and CDR, so I would like
> to get it working.  The only thing not functioning now is the MI/XMLRPC
> features.
>
>
> The MI functions simply return no results, yet I can issue a kamctl fifo
> Xand it works.
>
>
> On Fri, Jun 28, 2013 at 3:52 PM, Ovidiu Sas  wrote:
>
>> If you simply want a web interface for MI/RPC commands, take a look at
>> the xhttp_rpc module:
>> http://kamailio.org/docs/modules/devel/modules/xhttp_rpc
>>
>> Regards,
>> Ovidiu Sas
>>
>> On Fri, Jun 28, 2013 at 5:09 PM, Geoffrey Mina 
>> wrote:
>> > I am having some trouble getting Siremis 4.0 to work with Kamailio 4.0.
>>  The
>> > PHP application is functioning fine and all the DB access is working as
>> > intended.  Where I am having an issue is with the "Command Services"
>> > section.  I am unclear weather I want the "MI" or "XMLRPC".  The basic
>> > functions I want to use would be:
>> >
>> > sip_trace on/off
>> > debug 
>> > lcr_reload
>> > address_reload
>> >
>> > I know they are going to be different coming from 1.5 to 4.0, but I am
>> > hoping there is still a way to get Siremis to invoke these commands.
>>  When I
>> > click on the XMLRPC section, I get this error:
>> >
>> > [2013-06-28 21:09:16 (GMT)] An exception occurred while executing this
>> > script:
>> > Error message: #2, require_once(XML/RPC.php) [function.require-once]:
>> failed
>> > to open stream: No such file or directory
>> > Script name and line number of error:
>> >
>> /var/www/siremis-4.0.0/siremis/modules/ser/service/asipto/libs/cmds/serxr.php:2
>> >
>> > function: errorHandler ( 2, "require_once(XML/RPC.php) [> > href='function.require-once'>funct...",
>> > "/var/www/siremis-4.0.0/siremis/modules/ser/service/asipto/libs/c...",
>> 2,
>> > Array(12) ) @ /var/www/siremis-4.0.0/openbiz/bin/sysheader.inc 117
>> > function: userErrorHandler ( 2, "require_once(XML/RPC.php) [> > href='function.require-once'>funct...",
>> > "/var/www/siremis-4.0.0/siremis/modules/ser/service/asipto/libs/c...",
>> 2,
>> > Array(12) ) @
>> > function: require_once ( ) @
>> >
>> /var/www/siremis-4.0.0/siremis/modules/ser/service/asipto/libs/cmds/serxr.php
>> > 2
>> > function: include_once (
>> > "/var/www/siremis-4.0.0/siremis/modules/ser/service/asipto/libs/c..." )
>> @
>> > /var/www/siremis-4.0.0/siremis/modules/ser/cms/form/XrcmdsForm.php 2
>> > function: include_once (
>> > "/var/www/siremis-4.0.0/siremis/modules/ser/cms/form/XrcmdsForm.p..." )
>> @
>> > /var/www/siremis-4.0.0/openbiz/bin/ObjectFactory.php 162
>> > function: constructObject ( "ser.cms.form.XrcmdsForm" ) @
>> > /var/www/siremis-4.0.0/openbiz/bin/ObjectFactory.php 56
>> > function: getObject ( "ser.cms.form.XrcmdsForm" ) @
>> > /var/www/siremis-4.0.0/openbiz/bin/easy/EasyView.php 348
>> > function: initAllForms ( ) @
>> > /var/www/siremis-4.0.0/openbiz/bin/easy/EasyView.php 232
>> > function: render ( ) @
>> /var/www/siremis-4.0.0/openbiz/bin/BizController.php
>> > 221
>> > function: renderView ( "ser.view.XrcmdsView", "", "", Null, "" ) @
>> > /var/www/siremis-4.0.0/openbiz/bin/BizController.php 107
>> > function: dispatchRequest ( ) @
>> > /var/www/siremis-4.0.0/openbiz/bin/BizController.php 32
>> > function: include_once (
>> > "/var/www/siremis-4.0.0/openbiz/bin/BizController.php" ) @
>> > /var/www/siremis-4.0.0/siremis/bin/controller.php 6
>> > function: include ( "/var/www/siremis-4.0.0/siremis/bin/controller.php"
>> ) @
>> > /var/www/siremis-4.0.0/siremis/bin/_forward.php 102
>> > function: include ( "/var/www/siremis-4.0.0/siremis/bin/_forward.php" )
>> @
>> > /var/www/siremis-4.0.0/siremis/index.php 3
>> >
>> >
>> > ___
>> > SIP Express Router (SER) and Kamailio (OpenSER) - sr-users mailing list
>> > sr-users@lists.sip-router.org
>> > http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users
>> >
>>
>>
>>
>> --
>> VoIP Embedded, Inc.
>> http://www.voipembedded.com
>>
>> ___
>> SIP Express Router (SER) and Kamailio (OpenSER) - sr-users mailing list
>> sr-users@lists.sip-router.org
>> http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users
>>
>
>
___
SIP Express Router (SER) and Kamailio (OpenSER) - sr-users mailing list
sr-users@lists.sip-router.org
http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users

Re: [SR-Users] LCR in Kamailio 4.0

2013-06-28 Thread Geoffrey Mina

Thanks.  I included ctl.so module and now I can properly use kamcmd to
reload LCR.





On Fri, Jun 28, 2013 at 4:57 PM, Gary Chen  wrote:

> lcr_rule_target is like a glue to link lcr_gw and lcr_rule tables together
> through rule_id and gw_id as well as lcr_id.
> In this case if you have several sets of lcr_id, you will end up with
> several duplicate gateway and rulls. It is not the best design and is hard
> to use.
>
> To reload lcr you do this: sercmd lcr.reload
>
> Gary Chen
>
>
> On Fri, Jun 28, 2013 at 6:50 PM, Geoffrey Mina wrote:
>
>> What is the value of the "target" table?  Previously the lcr rule table
>> was directly tied to the gateway.  Is this simply to enable N:1
>> relationships between lcr rules and gateways.
>>
>> Also - any idea how to reload the LCR configuration without restarting
>> kamailio?  I previously issued "kamctl fifo lcr_reload", but that doesn't
>> appear to work any longer.
>>
>> Thanks!
>>
>>
>> On Fri, Jun 28, 2013 at 4:44 PM, Gary Chen  wrote:
>>
>>> First thing to remember that lcr_id field is the one to link all three
>>> tables together. Let's say that you want to create a lcr to route
>>> international call starting with 011:
>>> 1) Create a row in lcr_gw table with id = 4, lcr_id = 3 and gateway IP
>>> etc.
>>> 2) Then create a row in lcr_rule table with id =2, lcr_id = 3 and prefix
>>> = 011
>>> 3) Then create a row in lcr_rule_target table to glue the gateway and
>>> prefix together like this: lcr_id =3, gw_id=4 (Match the id value in lcr_gw
>>> table), rule_id = 2 (Match the id in lcr_rule table)  also rest of the
>>> fields like priority etc.
>>>
>>> Hope this help.
>>>
>>> Gary
>>>
>>>
>>>
>>> On Fri, Jun 28, 2013 at 5:02 PM, Geoffrey Mina 
>>> wrote:
>>>
 Greetings,
 I am migrating some 1.5 servers to 4.0 and I have some questions about
 how the LCR module works now.

 I am familiar with the concept of the gw table and the lcr table.  This
 was pretty straight forward.  In the new version it looks like we have:

 LCR Gateway List
 LCR Rule List
 LCR Target List

 I read through the module documentation and it doesn't really speak to
 what the new architecture is intended to accomplish.  Anyone have a quick
 overview they would like to share which would help me understand the intent
 of the data structure?

 Thanks,
 Geoff

 ___
 SIP Express Router (SER) and Kamailio (OpenSER) - sr-users mailing list
 sr-users@lists.sip-router.org
 http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users


>>>
>>> ___
>>> SIP Express Router (SER) and Kamailio (OpenSER) - sr-users mailing list
>>> sr-users@lists.sip-router.org
>>> http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users
>>>
>>>
>>
>> ___
>> SIP Express Router (SER) and Kamailio (OpenSER) - sr-users mailing list
>> sr-users@lists.sip-router.org
>> http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users
>>
>>
>
> ___
> SIP Express Router (SER) and Kamailio (OpenSER) - sr-users mailing list
> sr-users@lists.sip-router.org
> http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users
>
>
___
SIP Express Router (SER) and Kamailio (OpenSER) - sr-users mailing list
sr-users@lists.sip-router.org
http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users

Re: [SR-Users] LCR in Kamailio 4.0

2013-06-28 Thread Gary Chen

lcr_rule_target is like a glue to link lcr_gw and lcr_rule tables together
through rule_id and gw_id as well as lcr_id.
In this case if you have several sets of lcr_id, you will end up with
several duplicate gateway and rulls. It is not the best design and is hard
to use.

To reload lcr you do this: sercmd lcr.reload

Gary Chen


On Fri, Jun 28, 2013 at 6:50 PM, Geoffrey Mina wrote:

> What is the value of the "target" table?  Previously the lcr rule table
> was directly tied to the gateway.  Is this simply to enable N:1
> relationships between lcr rules and gateways.
>
> Also - any idea how to reload the LCR configuration without restarting
> kamailio?  I previously issued "kamctl fifo lcr_reload", but that doesn't
> appear to work any longer.
>
> Thanks!
>
>
> On Fri, Jun 28, 2013 at 4:44 PM, Gary Chen  wrote:
>
>> First thing to remember that lcr_id field is the one to link all three
>> tables together. Let's say that you want to create a lcr to route
>> international call starting with 011:
>> 1) Create a row in lcr_gw table with id = 4, lcr_id = 3 and gateway IP
>> etc.
>> 2) Then create a row in lcr_rule table with id =2, lcr_id = 3 and prefix
>> = 011
>> 3) Then create a row in lcr_rule_target table to glue the gateway and
>> prefix together like this: lcr_id =3, gw_id=4 (Match the id value in lcr_gw
>> table), rule_id = 2 (Match the id in lcr_rule table)  also rest of the
>> fields like priority etc.
>>
>> Hope this help.
>>
>> Gary
>>
>>
>>
>> On Fri, Jun 28, 2013 at 5:02 PM, Geoffrey Mina wrote:
>>
>>> Greetings,
>>> I am migrating some 1.5 servers to 4.0 and I have some questions about
>>> how the LCR module works now.
>>>
>>> I am familiar with the concept of the gw table and the lcr table.  This
>>> was pretty straight forward.  In the new version it looks like we have:
>>>
>>> LCR Gateway List
>>> LCR Rule List
>>> LCR Target List
>>>
>>> I read through the module documentation and it doesn't really speak to
>>> what the new architecture is intended to accomplish.  Anyone have a quick
>>> overview they would like to share which would help me understand the intent
>>> of the data structure?
>>>
>>> Thanks,
>>> Geoff
>>>
>>> ___
>>> SIP Express Router (SER) and Kamailio (OpenSER) - sr-users mailing list
>>> sr-users@lists.sip-router.org
>>> http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users
>>>
>>>
>>
>> ___
>> SIP Express Router (SER) and Kamailio (OpenSER) - sr-users mailing list
>> sr-users@lists.sip-router.org
>> http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users
>>
>>
>
> ___
> SIP Express Router (SER) and Kamailio (OpenSER) - sr-users mailing list
> sr-users@lists.sip-router.org
> http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users
>
>
___
SIP Express Router (SER) and Kamailio (OpenSER) - sr-users mailing list
sr-users@lists.sip-router.org
http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users

Re: [SR-Users] LCR in Kamailio 4.0

2013-06-28 Thread Geoffrey Mina

What is the value of the "target" table?  Previously the lcr rule table was
directly tied to the gateway.  Is this simply to enable N:1 relationships
between lcr rules and gateways.

Also - any idea how to reload the LCR configuration without restarting
kamailio?  I previously issued "kamctl fifo lcr_reload", but that doesn't
appear to work any longer.

Thanks!


On Fri, Jun 28, 2013 at 4:44 PM, Gary Chen  wrote:

> First thing to remember that lcr_id field is the one to link all three
> tables together. Let's say that you want to create a lcr to route
> international call starting with 011:
> 1) Create a row in lcr_gw table with id = 4, lcr_id = 3 and gateway IP
> etc.
> 2) Then create a row in lcr_rule table with id =2, lcr_id = 3 and prefix =
> 011
> 3) Then create a row in lcr_rule_target table to glue the gateway and
> prefix together like this: lcr_id =3, gw_id=4 (Match the id value in lcr_gw
> table), rule_id = 2 (Match the id in lcr_rule table)  also rest of the
> fields like priority etc.
>
> Hope this help.
>
> Gary
>
>
>
> On Fri, Jun 28, 2013 at 5:02 PM, Geoffrey Mina wrote:
>
>> Greetings,
>> I am migrating some 1.5 servers to 4.0 and I have some questions about
>> how the LCR module works now.
>>
>> I am familiar with the concept of the gw table and the lcr table.  This
>> was pretty straight forward.  In the new version it looks like we have:
>>
>> LCR Gateway List
>> LCR Rule List
>> LCR Target List
>>
>> I read through the module documentation and it doesn't really speak to
>> what the new architecture is intended to accomplish.  Anyone have a quick
>> overview they would like to share which would help me understand the intent
>> of the data structure?
>>
>> Thanks,
>> Geoff
>>
>> ___
>> SIP Express Router (SER) and Kamailio (OpenSER) - sr-users mailing list
>> sr-users@lists.sip-router.org
>> http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users
>>
>>
>
> ___
> SIP Express Router (SER) and Kamailio (OpenSER) - sr-users mailing list
> sr-users@lists.sip-router.org
> http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users
>
>
___
SIP Express Router (SER) and Kamailio (OpenSER) - sr-users mailing list
sr-users@lists.sip-router.org
http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users

Re: [SR-Users] Siremis 4.0 with Kamailio 4.0

2013-06-28 Thread Geoffrey Mina

We use Siremis for configuration of our LCR, ACL and CDR, so I would like
to get it working.  The only thing not functioning now is the MI/XMLRPC
features.


The MI functions simply return no results, yet I can issue a kamctl fifo
Xand it works.


On Fri, Jun 28, 2013 at 3:52 PM, Ovidiu Sas  wrote:

> If you simply want a web interface for MI/RPC commands, take a look at
> the xhttp_rpc module:
> http://kamailio.org/docs/modules/devel/modules/xhttp_rpc
>
> Regards,
> Ovidiu Sas
>
> On Fri, Jun 28, 2013 at 5:09 PM, Geoffrey Mina 
> wrote:
> > I am having some trouble getting Siremis 4.0 to work with Kamailio 4.0.
>  The
> > PHP application is functioning fine and all the DB access is working as
> > intended.  Where I am having an issue is with the "Command Services"
> > section.  I am unclear weather I want the "MI" or "XMLRPC".  The basic
> > functions I want to use would be:
> >
> > sip_trace on/off
> > debug 
> > lcr_reload
> > address_reload
> >
> > I know they are going to be different coming from 1.5 to 4.0, but I am
> > hoping there is still a way to get Siremis to invoke these commands.
>  When I
> > click on the XMLRPC section, I get this error:
> >
> > [2013-06-28 21:09:16 (GMT)] An exception occurred while executing this
> > script:
> > Error message: #2, require_once(XML/RPC.php) [function.require-once]:
> failed
> > to open stream: No such file or directory
> > Script name and line number of error:
> >
> /var/www/siremis-4.0.0/siremis/modules/ser/service/asipto/libs/cmds/serxr.php:2
> >
> > function: errorHandler ( 2, "require_once(XML/RPC.php) [ > href='function.require-once'>funct...",
> > "/var/www/siremis-4.0.0/siremis/modules/ser/service/asipto/libs/c...", 2,
> > Array(12) ) @ /var/www/siremis-4.0.0/openbiz/bin/sysheader.inc 117
> > function: userErrorHandler ( 2, "require_once(XML/RPC.php) [ > href='function.require-once'>funct...",
> > "/var/www/siremis-4.0.0/siremis/modules/ser/service/asipto/libs/c...", 2,
> > Array(12) ) @
> > function: require_once ( ) @
> >
> /var/www/siremis-4.0.0/siremis/modules/ser/service/asipto/libs/cmds/serxr.php
> > 2
> > function: include_once (
> > "/var/www/siremis-4.0.0/siremis/modules/ser/service/asipto/libs/c..." ) @
> > /var/www/siremis-4.0.0/siremis/modules/ser/cms/form/XrcmdsForm.php 2
> > function: include_once (
> > "/var/www/siremis-4.0.0/siremis/modules/ser/cms/form/XrcmdsForm.p..." ) @
> > /var/www/siremis-4.0.0/openbiz/bin/ObjectFactory.php 162
> > function: constructObject ( "ser.cms.form.XrcmdsForm" ) @
> > /var/www/siremis-4.0.0/openbiz/bin/ObjectFactory.php 56
> > function: getObject ( "ser.cms.form.XrcmdsForm" ) @
> > /var/www/siremis-4.0.0/openbiz/bin/easy/EasyView.php 348
> > function: initAllForms ( ) @
> > /var/www/siremis-4.0.0/openbiz/bin/easy/EasyView.php 232
> > function: render ( ) @
> /var/www/siremis-4.0.0/openbiz/bin/BizController.php
> > 221
> > function: renderView ( "ser.view.XrcmdsView", "", "", Null, "" ) @
> > /var/www/siremis-4.0.0/openbiz/bin/BizController.php 107
> > function: dispatchRequest ( ) @
> > /var/www/siremis-4.0.0/openbiz/bin/BizController.php 32
> > function: include_once (
> > "/var/www/siremis-4.0.0/openbiz/bin/BizController.php" ) @
> > /var/www/siremis-4.0.0/siremis/bin/controller.php 6
> > function: include ( "/var/www/siremis-4.0.0/siremis/bin/controller.php"
> ) @
> > /var/www/siremis-4.0.0/siremis/bin/_forward.php 102
> > function: include ( "/var/www/siremis-4.0.0/siremis/bin/_forward.php" ) @
> > /var/www/siremis-4.0.0/siremis/index.php 3
> >
> >
> > ___
> > SIP Express Router (SER) and Kamailio (OpenSER) - sr-users mailing list
> > sr-users@lists.sip-router.org
> > http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users
> >
>
>
>
> --
> VoIP Embedded, Inc.
> http://www.voipembedded.com
>
> ___
> SIP Express Router (SER) and Kamailio (OpenSER) - sr-users mailing list
> sr-users@lists.sip-router.org
> http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users
>
___
SIP Express Router (SER) and Kamailio (OpenSER) - sr-users mailing list
sr-users@lists.sip-router.org
http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users

Re: [SR-Users] LCR in Kamailio 4.0

2013-06-28 Thread Gary Chen

First thing to remember that lcr_id field is the one to link all three
tables together. Let's say that you want to create a lcr to route
international call starting with 011:
1) Create a row in lcr_gw table with id = 4, lcr_id = 3 and gateway IP etc.
2) Then create a row in lcr_rule table with id =2, lcr_id = 3 and prefix =
011
3) Then create a row in lcr_rule_target table to glue the gateway and
prefix together like this: lcr_id =3, gw_id=4 (Match the id value in lcr_gw
table), rule_id = 2 (Match the id in lcr_rule table)  also rest of the
fields like priority etc.

Hope this help.

Gary

On Fri, Jun 28, 2013 at 5:02 PM, Geoffrey Mina wrote:

> Greetings,
> I am migrating some 1.5 servers to 4.0 and I have some questions about how
> the LCR module works now.
>
> I am familiar with the concept of the gw table and the lcr table.  This
> was pretty straight forward.  In the new version it looks like we have:
>
> LCR Gateway List
> LCR Rule List
> LCR Target List
>
> I read through the module documentation and it doesn't really speak to
> what the new architecture is intended to accomplish.  Anyone have a quick
> overview they would like to share which would help me understand the intent
> of the data structure?
>
> Thanks,
> Geoff
>
> ___
> SIP Express Router (SER) and Kamailio (OpenSER) - sr-users mailing list
> sr-users@lists.sip-router.org
> http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users
>
>
___
SIP Express Router (SER) and Kamailio (OpenSER) - sr-users mailing list
sr-users@lists.sip-router.org
http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users

Re: [SR-Users] Siremis 4.0 with Kamailio 4.0

2013-06-28 Thread Ovidiu Sas

If you simply want a web interface for MI/RPC commands, take a look at
the xhttp_rpc module:
http://kamailio.org/docs/modules/devel/modules/xhttp_rpc

Regards,
Ovidiu Sas

On Fri, Jun 28, 2013 at 5:09 PM, Geoffrey Mina  wrote:
> I am having some trouble getting Siremis 4.0 to work with Kamailio 4.0.  The
> PHP application is functioning fine and all the DB access is working as
> intended.  Where I am having an issue is with the "Command Services"
> section.  I am unclear weather I want the "MI" or "XMLRPC".  The basic
> functions I want to use would be:
>
> sip_trace on/off
> debug 
> lcr_reload
> address_reload
>
> I know they are going to be different coming from 1.5 to 4.0, but I am
> hoping there is still a way to get Siremis to invoke these commands.  When I
> click on the XMLRPC section, I get this error:
>
> [2013-06-28 21:09:16 (GMT)] An exception occurred while executing this
> script:
> Error message: #2, require_once(XML/RPC.php) [function.require-once]: failed
> to open stream: No such file or directory
> Script name and line number of error:
> /var/www/siremis-4.0.0/siremis/modules/ser/service/asipto/libs/cmds/serxr.php:2
>
> function: errorHandler ( 2, "require_once(XML/RPC.php) [ href='function.require-once'>funct...",
> "/var/www/siremis-4.0.0/siremis/modules/ser/service/asipto/libs/c...", 2,
> Array(12) ) @ /var/www/siremis-4.0.0/openbiz/bin/sysheader.inc 117
> function: userErrorHandler ( 2, "require_once(XML/RPC.php) [ href='function.require-once'>funct...",
> "/var/www/siremis-4.0.0/siremis/modules/ser/service/asipto/libs/c...", 2,
> Array(12) ) @
> function: require_once ( ) @
> /var/www/siremis-4.0.0/siremis/modules/ser/service/asipto/libs/cmds/serxr.php
> 2
> function: include_once (
> "/var/www/siremis-4.0.0/siremis/modules/ser/service/asipto/libs/c..." ) @
> /var/www/siremis-4.0.0/siremis/modules/ser/cms/form/XrcmdsForm.php 2
> function: include_once (
> "/var/www/siremis-4.0.0/siremis/modules/ser/cms/form/XrcmdsForm.p..." ) @
> /var/www/siremis-4.0.0/openbiz/bin/ObjectFactory.php 162
> function: constructObject ( "ser.cms.form.XrcmdsForm" ) @
> /var/www/siremis-4.0.0/openbiz/bin/ObjectFactory.php 56
> function: getObject ( "ser.cms.form.XrcmdsForm" ) @
> /var/www/siremis-4.0.0/openbiz/bin/easy/EasyView.php 348
> function: initAllForms ( ) @
> /var/www/siremis-4.0.0/openbiz/bin/easy/EasyView.php 232
> function: render ( ) @ /var/www/siremis-4.0.0/openbiz/bin/BizController.php
> 221
> function: renderView ( "ser.view.XrcmdsView", "", "", Null, "" ) @
> /var/www/siremis-4.0.0/openbiz/bin/BizController.php 107
> function: dispatchRequest ( ) @
> /var/www/siremis-4.0.0/openbiz/bin/BizController.php 32
> function: include_once (
> "/var/www/siremis-4.0.0/openbiz/bin/BizController.php" ) @
> /var/www/siremis-4.0.0/siremis/bin/controller.php 6
> function: include ( "/var/www/siremis-4.0.0/siremis/bin/controller.php" ) @
> /var/www/siremis-4.0.0/siremis/bin/_forward.php 102
> function: include ( "/var/www/siremis-4.0.0/siremis/bin/_forward.php" ) @
> /var/www/siremis-4.0.0/siremis/index.php 3
>
>
> ___
> SIP Express Router (SER) and Kamailio (OpenSER) - sr-users mailing list
> sr-users@lists.sip-router.org
> http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users
>



-- 
VoIP Embedded, Inc.
http://www.voipembedded.com

___
SIP Express Router (SER) and Kamailio (OpenSER) - sr-users mailing list
sr-users@lists.sip-router.org
http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users

[SR-Users] Siremis 4.0 with Kamailio 4.0

2013-06-28 Thread Geoffrey Mina

I am having some trouble getting Siremis 4.0 to work with Kamailio 4.0.
The PHP application is functioning fine and all the DB access is working as
intended.  Where I am having an issue is with the "Command Services"
section.  I am unclear weather I want the "MI" or "XMLRPC".  The basic
functions I want to use would be:

sip_trace on/off
debug 
lcr_reload
address_reload

I know they are going to be different coming from 1.5 to 4.0, but I am
hoping there is still a way to get Siremis to invoke these commands.  When
I click on the XMLRPC section, I get this error:

[2013-06-28 21:09:16 (GMT)] An exception occurred while executing this
script:
Error message: #2, require_once(XML/RPC.php)
[function.require-once]:
failed to open stream: No such file or directory
Script name and line number of error:
/var/www/siremis-4.0.0/siremis/modules/ser/service/asipto/libs/cmds/serxr.php:2

*function:* errorHandler ( 2, "require_once(XML/RPC.php) [funct...",
"/var/www/siremis-4.0.0/siremis/modules/ser/service/asipto/libs/c...", 2,
Array(12) ) @ /var/www/siremis-4.0.0/openbiz/bin/sysheader.inc 117
*function:* userErrorHandler ( 2, "require_once(XML/RPC.php) [funct...",
"/var/www/siremis-4.0.0/siremis/modules/ser/service/asipto/libs/c...", 2,
Array(12) ) @
*function:* require_once ( ) @
/var/www/siremis-4.0.0/siremis/modules/ser/service/asipto/libs/cmds/serxr.php
2
*function:* include_once (
"/var/www/siremis-4.0.0/siremis/modules/ser/service/asipto/libs/c..." ) @
/var/www/siremis-4.0.0/siremis/modules/ser/cms/form/XrcmdsForm.php 2
*function:* include_once (
"/var/www/siremis-4.0.0/siremis/modules/ser/cms/form/XrcmdsForm.p..." ) @
/var/www/siremis-4.0.0/openbiz/bin/ObjectFactory.php 162
*function:* constructObject ( "ser.cms.form.XrcmdsForm" ) @
/var/www/siremis-4.0.0/openbiz/bin/ObjectFactory.php 56
*function:* getObject ( "ser.cms.form.XrcmdsForm" ) @
/var/www/siremis-4.0.0/openbiz/bin/easy/EasyView.php 348
*function:* initAllForms ( ) @
/var/www/siremis-4.0.0/openbiz/bin/easy/EasyView.php 232
*function:* render ( ) @
/var/www/siremis-4.0.0/openbiz/bin/BizController.php 221
*function:* renderView ( "ser.view.XrcmdsView", "", "", Null, "" ) @
/var/www/siremis-4.0.0/openbiz/bin/BizController.php 107
*function:* dispatchRequest ( ) @
/var/www/siremis-4.0.0/openbiz/bin/BizController.php 32
*function:* include_once (
"/var/www/siremis-4.0.0/openbiz/bin/BizController.php" ) @
/var/www/siremis-4.0.0/siremis/bin/controller.php 6
*function:* include ( "/var/www/siremis-4.0.0/siremis/bin/controller.php" )
@ /var/www/siremis-4.0.0/siremis/bin/_forward.php 102
*function:* include ( "/var/www/siremis-4.0.0/siremis/bin/_forward.php" ) @
/var/www/siremis-4.0.0/siremis/index.php 3
___
SIP Express Router (SER) and Kamailio (OpenSER) - sr-users mailing list
sr-users@lists.sip-router.org
http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users

[SR-Users] LCR in Kamailio 4.0

2013-06-28 Thread Geoffrey Mina

Greetings,
I am migrating some 1.5 servers to 4.0 and I have some questions about how
the LCR module works now.

I am familiar with the concept of the gw table and the lcr table.  This was
pretty straight forward.  In the new version it looks like we have:

LCR Gateway List
LCR Rule List
LCR Target List

I read through the module documentation and it doesn't really speak to what
the new architecture is intended to accomplish.  Anyone have a quick
overview they would like to share which would help me understand the intent
of the data structure?

Thanks,
Geoff
___
SIP Express Router (SER) and Kamailio (OpenSER) - sr-users mailing list
sr-users@lists.sip-router.org
http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users

Re: [SR-Users] Consuming 300 Multiple Choices

2013-06-28 Thread Geoffrey Mina

Thanks!  I am actually taking this opportunity to upgrade to 4.0.  Looks
like there is a lot of good stuff here!


On Fri, Jun 28, 2013 at 7:14 AM, I.Pavlov  wrote:

> This should work in 1.5:
>
> *$ct* - reference to body of contact header 
>
> xlog("CONTCAT: rate=$(ct{param.value,rate})");
>
> acc_log_request(“RATE: $(ct{param.value,rate})”);
>
> ** **
>
> ** **
>
> *From:* sr-users-boun...@lists.sip-router.org [mailto:
> sr-users-boun...@lists.sip-router.org] *On Behalf Of *Geoffrey Mina
> *Sent:* Friday, June 28, 2013 4:38 PM
> *To:* Kamailio (SER) - Users Mailing List
> *Subject:* Re: [SR-Users] Consuming 300 Multiple Choices
>
> ** **
>
> I should have been more clear.  I am using Kamailio 1.5.  I would consider
> upgrading, but that isn't the ideal path here.
>
> Any other idea for 1.5?
>
> ** **
>
> On Fri, Jun 28, 2013 at 12:46 AM, I.Pavlov  wrote:
>
> Hi Geoff, to grab “rate”-attribute try to use
> “$sel(contact.params["rate"]);”-expression. For example, in my test with
> sipp, I used *Contact: sip:sipp@[local_ip]:[local_port];q=0.1;rate=0.002 *and
> 
>
>  
>
> $var(rate)=$sel(contact.params["rate"]);
>
> xlog("CONTACT URI PARAMS: $var(rate)");
>
>  
>
> /usr/sbin/kamailio[25909]: ERROR:

Re: [SR-Users] Consuming 300 Multiple Choices

2013-06-28 Thread I.Pavlov

This should work in 1.5:

$ct - reference to body of contact header 

xlog("CONTCAT: rate=$(ct{param.value,rate})");

acc_log_request("RATE: $(ct{param.value,rate})");

 

 

From: sr-users-boun...@lists.sip-router.org
[mailto:sr-users-boun...@lists.sip-router.org] On Behalf Of Geoffrey Mina
Sent: Friday, June 28, 2013 4:38 PM
To: Kamailio (SER) - Users Mailing List
Subject: Re: [SR-Users] Consuming 300 Multiple Choices

 

I should have been more clear.  I am using Kamailio 1.5.  I would consider
upgrading, but that isn't the ideal path here.

Any other idea for 1.5?

 

On Fri, Jun 28, 2013 at 12:46 AM, I.Pavlov  wrote:

Hi Geoff, to grab "rate"-attribute try to use
"$sel(contact.params["rate"]);"-expression. For example, in my test with
sipp, I used Contact: sip:sipp@[local_ip]:[local_port];q=0.1;rate=0.002 and 

 

$var(rate)=$sel(contact.params["rate"]);

xlog("CONTACT URI PARAMS: $var(rate)");

 

/usr/sbin/kamailio[25909]: ERROR:

Re: [SR-Users] Consuming 300 Multiple Choices

2013-06-28 Thread Geoffrey Mina

I should have been more clear.  I am using Kamailio 1.5.  I would consider
upgrading, but that isn't the ideal path here.

Any other idea for 1.5?

On Fri, Jun 28, 2013 at 12:46 AM, I.Pavlov  wrote:

> Hi Geoff, to grab “rate”-attribute try to use
> “$sel(contact.params["rate"]);”-expression. For example, in my test with
> sipp, I used *Contact: sip:sipp@[local_ip]:[local_port];q=0.1;rate=0.002 *and
> 
>
> ** **
>
> $var(rate)=$sel(contact.params["rate"]);
>
> xlog("CONTACT URI PARAMS: $var(rate)");
>
> ** **
>
> /usr/sbin/kamailio[25909]: ERROR:

[SR-Users] ASSISTANCE Required

2013-06-28 Thread Piyush . Bansal

Hi,
I am using SER iptel as a SIP proxy. I have few doubts regarding 
ser.cfg configuration file.

1. I am having two config variables, say $a and $b. Can't I do any 
comparison of the two in any if loop? e.g. [if ($a == $b)] or something 
similar.

2. I exported a function from a module say func1( ). It works perfectly 
fine if I pass a static value in it but corrupts the value if I pass a 
variable thru it.e.g. func1("11") will work fine but $a = '11' and 
func1("%$a") will not work.

3. I want to add a new header field in 200 OK response to REGISTER. How 
can I do that?
Please help.

Regards
--Piyush

Thanks and Regards,
--Piyush Bansal
NATT - I & T, Reliance Tech Services, Delhi, India
(M) +91-93502-30362

Enjoy the widest reach of 3G services across India only On Reliance
www.rcom.co.in/3G




The information contained in this electronic message (email) and any 
attachments to this email are intended for the exclusive use of the 
addressee(s) and access to this email by any one else is unauthorised. The 
email may contain proprietary, confidential or privileged information or 
information relating to Reliance Group. If you are not the intended recipient, 
please notify the sender by telephone, fax, or return email and delete this 
communication and any attachments thereto, immediately from your computer. Any 
dissemination, distribution, or copying of this communication and the 
attachments thereto (in whole or part), in any manner, is strictly prohibited 
and actionable at law. The recipient acknowledges that emails are susceptible 
to alteration and their integrity can not be guaranteed and that Company does 
not guarantee that any e-mail is virus-free and accept no liability for any 
damage caused by any virus transmitted by this email.
___
SIP Express Router (SER) and Kamailio (OpenSER) - sr-users mailing list
sr-users@lists.sip-router.org
http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users

[SR-Users] avpops error line number

2013-06-28 Thread Juha Heinanen

would it be possible to enhance avpops module to print config file line
number when error occurs?

now i just get:

Jun 24 14:13:43 host /usr/sbin/sip-proxy[29890]: ERROR: avpops
[avpops_impl.c:1170]: ops_check_avp(): value types don't match

-- juha

___
SIP Express Router (SER) and Kamailio (OpenSER) - sr-users mailing list
sr-users@lists.sip-router.org
http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users

Re: [SR-Users] Asterisk Gateway OPTIONS relay

2013-06-28 Thread Klaus Darilion

Does the routing of INVITE from Asterisk to the UA work? If yes, just 
make sure that you route the OPTIONS from Asterisk identical to the INVITE.


regards
Klaus

On 27.06.2013 15:28, Ian French wrote:

Hey list,
I've been trying the relay OPTIONS messages from an asterisk
server through kamailio to clients so to preserve the qualify feature in
asterisk. So


ASTERISK -OPTIONS> KAMAILIO > UA

UA OK-> KAMAILIO ---OK-> ASTERISK

But I'm seeing floods of OPTIONS messages between asterisk and kamailio
now. So much so that kamailio seems to deadlock introducing 10 -20
second delays in processing messages

firstly I've enabled the options.so but this is just enable remote
monitoring of the application and in my FROMASTERISK route

#!ifdef WITH_ASTERISK
# Test if coming from Asterisk
route[FROMASTERISK] {
#   if($si==$sel(cfg_get.asterisk.bindip)
#   && $sp==$sel(cfg_get.asterisk.bindport))

if ((method==OPTIONS) && (uri=~"sip:.*[@]+.*")) {
 xlog("L_INFO","Options Reply from $ru to $fu\r\n");
 return 1;
}

 if(ds_is_from_list("2")){
 $sht(forw=>$ft)=$si;
 xlog("L_INFO","INVITE: INVITE Passed From [$fu]
Asterisk Cluster To [$rm:$au].\n");
 return 1;
}
return -1;
}

I've included a debug below, stating *RFC3261 transaction matching
failed. *Can anyone help or advise on how I should solve this

Thanks in advance
Ian

KamP /usr/local/sbin/kamailio[19288]: DEBUG: 
[parser/msg_parser.c:630]: SIP Request:
KamP /usr/local/sbin/kamailio[19288]: DEBUG: 
[parser/msg_parser.c:632]:  method:  
KamP /usr/local/sbin/kamailio[19288]: DEBUG: 
[parser/msg_parser.c:634]:  uri: 
KamP /usr/local/sbin/kamailio[19288]: DEBUG: 
[parser/msg_parser.c:636]:  version: 
KamP /usr/local/sbin/kamailio[19288]: DEBUG: 
[parser/parse_via.c:1287]: Found param type 232,  =
; state=6
KamP /usr/local/sbin/kamailio[19288]: DEBUG: 
[parser/parse_via.c:1287]: Found param type 235,  = ; state=17
KamP /usr/local/sbin/kamailio[19288]: DEBUG: 
[parser/parse_via.c:2300]: end of header reached, state=5
KamP /usr/local/sbin/kamailio[19288]: DEBUG: 
[parser/msg_parser.c:515]: parse_headers: Via found, flags=2
KamP /usr/local/sbin/kamailio[19288]: DEBUG: 
[parser/msg_parser.c:517]: parse_headers: this is the first via
KamP /usr/local/sbin/kamailio[19288]: DEBUG:  [receive.c:145]:
After parse_msg...
KamP /usr/local/sbin/kamailio[19288]: DEBUG:  [receive.c:186]:
preparing to run routing scripts...
KamP /usr/local/sbin/kamailio[19288]: DEBUG:  [socket_info.c:501]:
grep_sock_info - checking if host==us: 10==10 &&  [P.P.P.P] == [P.P.P.P]
KamP /usr/local/sbin/kamailio[19288]: DEBUG:  [socket_info.c:504]:
grep_sock_info - checking if port 5060 matches port 5060
KamP /usr/local/sbin/kamailio[19288]: DEBUG:  [socket_info.c:501]:
grep_sock_info - checking if host==us: 10==10 &&  [A.A.A.A] == [P.P.P.P]
KamP /usr/local/sbin/kamailio[19288]: DEBUG:  [forward.c:446]:
check_self: host != me
KamP /usr/local/sbin/kamailio[19288]: DEBUG: 
[parser/parse_to.c:174]: DEBUG: add_param: tag=as2c63e7cc
KamP /usr/local/sbin/kamailio[19288]: DEBUG: 
[parser/parse_to.c:803]: end of header reached, state=29
KamP /usr/local/sbin/kamailio[19288]: DEBUG: 
[parser/parse_to.c:803]: end of header reached, state=10
KamP /usr/local/sbin/kamailio[19288]: DEBUG: 
[parser/msg_parser.c:187]: DEBUG: get_hdr_field:  [32];
uri=[sip:@P.P.P.P:5060]
KamP /usr/local/sbin/kamailio[19288]: DEBUG: 
[parser/msg_parser.c:167]: get_hdr_field: cseq : <102> 
KamP /usr/local/sbin/kamailio[19288]: DEBUG: maxfwd [mf_funcs.c:85]:
value = 70
KamP /usr/local/sbin/kamailio[19288]: DEBUG: 
[parser/msg_parser.c:201]: DEBUG: get_hdr_body : content_length=0
KamP /usr/local/sbin/kamailio[19288]: DEBUG: 
[parser/msg_parser.c:103]: found end of header
KamP /usr/local/sbin/kamailio[19288]: DEBUG: geoip [geoip_pv.c:395]:
attempt to match: A.A.A.A
KamP /usr/local/sbin/kamailio[19288]: DEBUG: geoip [geoip_pv.c:401]:
geoip PV updated for: A.A.A.A
KamP /usr/local/sbin/kamailio[19288]: INFO:

Re: [SR-Users] kamailio loadbalancer with TLS problem forwarding INVITE back to UA

2013-06-28 Thread Klaus Darilion


Hi Allen!

Again on-list, please do not use private emails unless you have to 
provide sensitive data.


On 28.06.2013 01:17, Allen Zhang wrote:

Hi Klaus,

I dived into it and found the problem:

When UA2 send a REGISTER to the load balancer, fix_nated_register() is called 
and source ip of the UA is stored in the connection hash by tcpconn_new(), 
instead of the port from the contact header field.
But when proxy tries to send the INVITE to UA2 via the load balancer, the load 
balancer calls tcpconn_find() with the port from the contact header field.
Hence can't match the connection stored in hash.


I do not understand that.

fix_nated_register stores both info: the original contact + 
src-ip:port:transport.


After lookup(), the Request-URI is filled with the original contact, but 
$du (destination URI, internally used by Kamailio for routing) is 
populated with src-ip:port:transport. Thus, Kamailio should use the $du 
to find the TCP connection.


Anyway, TLS debugging is always difficult. I suggest to try to make it 
running with TCP. If TCP works, TLS will work too.


regards
Klaus



I need to use fix_nated_register() because the UA will be behind NAT in the 
future. How do I let the LB use aliased port instead of the port from the 
contact header field?

Regards,

Allen


-Original Message-
From: Klaus Darilion [mailto:klaus.mailingli...@pernau.at]
Sent: Thursday, 27 June 2013 10:54 p.m.
To: Kamailio (SER) - Users Mailing List
Cc: Allen Zhang; Shane Harrison
Subject: Re: [SR-Users] kamailio loadbalancer with TLS problem forwarding 
INVITE back to UA

make sure to also use   handle_ruri_alias()
http://kamailio.org/docs/modules/4.0.x/modules/nathelper.html#idp16851488
for requests from the proxy->lb->client

see the default kamailio config for proper usage of handle_ruri_alias() and 
add_contact_alias()

regards
klaus


On 27.06.2013 02:34, Allen Zhang wrote:

Hi,

Our set up:

UA1 -

--  Proxy1


 \
   /

 Loadbalancer (dispatcher module)

 /  
  \

UA2-

--  Proxy2

Both proxies have registrar module loaded and share the same database.

REGISTERs work fine.

The problem is this:

  TLSTCP

UA1  --> LB > Proxy

  INVITE(to UA2)  INVITE(to UA2)

TLS   TCP

UA1  <- LB <- Proxy

100 Trying

TLS   TCP

UA1  <- LB <--- Proxy

   INVITE(to UA2)

TLS
TCP

UA1  <--- LB <--- Proxy

  100 Trying

All above worked fine. Below is what's expected but never happened:

TLS
TCP

UA2  <--- LB <--- Proxy

  INVITE(to UA2)

We'd like the LB to reuse the TLS connection initiated by UA2. But LB
can't find an open connection and tries to start a new TLS connection.
The new connection fails.

UAs are not behind NAT at the moment but will be in the future.

Tried this approaches on LB:

route(ADD_CONTACT_ALIAS);

If (not from proxy)

  t_relay();

else

  do load balancing

No luck.

Any help is appreciated.

Regards,

Allen



___
SIP Express Router (SER) and Kamailio (OpenSER) - sr-users mailing
list sr-users@lists.sip-router.org
http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users





___
SIP Express Router (SER) and Kamailio (OpenSER) - sr-users mailing list
sr-users@lists.sip-router.org
http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users

Re: [SR-Users] Siremis 4.0 with Kamailio 4.0

Re: [SR-Users] LCR in Kamailio 4.0

Re: [SR-Users] LCR in Kamailio 4.0

Re: [SR-Users] LCR in Kamailio 4.0

Re: [SR-Users] Siremis 4.0 with Kamailio 4.0

Re: [SR-Users] LCR in Kamailio 4.0

Re: [SR-Users] Siremis 4.0 with Kamailio 4.0

[SR-Users] Siremis 4.0 with Kamailio 4.0

[SR-Users] LCR in Kamailio 4.0

Re: [SR-Users] Consuming 300 Multiple Choices

Re: [SR-Users] Consuming 300 Multiple Choices

Re: [SR-Users] Consuming 300 Multiple Choices

[SR-Users] ASSISTANCE Required

[SR-Users] avpops error line number

Re: [SR-Users] Asterisk Gateway OPTIONS relay

Re: [SR-Users] kamailio loadbalancer with TLS problem forwarding INVITE back to UA

16 matches

Site Navigation

Mail list logo

Footer information