[Spce-user] Peering rules problem
Daniel Grotti
dgrotti at sipwise.com
Tue Jan 13 05:43:55 EST 2015
Better:
1) cp /etc/ngcp-config/templates/etc/cron.d/ngcp-fraud-daily-lock.tt2
/etc/ngcp-config/templates/etc/cron.d/ngcp-fraud-daily-lock.customtt.tt2
2) vim
/etc/ngcp-config/templates/etc/cron.d/ngcp-fraud-daily-lock.customtt.tt2
#######*/30 * * * * root if /usr/sbin/ngcp-check_active -q; then
/usr/sbin/ngcp-fraud-daily-lock; fi
Daniel
On 01/13/2015 11:42 AM, Daniel Grotti wrote:
> Hi,
> that's strange, but if you don't use it and you don't want it to run,
> just comment out the following:
>
> vim /etc/ngcp-config/templates/etc/cron.d/ngcp-fraud-daily-lock.tt2
>
> #######*/30 * * * * root if /usr/sbin/ngcp-check_active -q; then
> /usr/sbin/ngcp-fraud-daily-lock; fi
>
>
>
> and then apply the change with "ngcpcfg apply".
>
> The script won't run anymore.
>
> Daniel
>
>
> On 01/13/2015 11:37 AM, Jorge Fresneda - Ibersontel wrote:
>> Hi,
>>
>> I don't use fraud-limit service in Sipwise, so Why can it happen this?
>>
>> Thanks Daniel,
>> Regards,
>> Jorge
>>
>>
>> Este mensaje es privado y confidencial y se dirige exclusivamente a su destinatario. Si usted ha recibido este mensaje por error, le rogamos que, si es posible, nos lo comunique respondiendo a este correo. "De conformidad con lo establecido en la Ley Orgánica 15/1999, de 13 de diciembre, de Protección de Datos de Carácter Personal, y en la Ley 34/2002, de 11 de julio, de Servicios de la Sociedad de la Información y de Comercio Electrónico, usted queda informado de la incorporación de sus datos en los ficheros correspondientes debidamente registrados en la Agencia Española de Protección de Datos y del tratamiento de los mismos para las finalidades de gestión de los usuarios, clientes y contactos comerciales de la compañía. El Responsable de dicho fichero es: IBERSONTEL, S.L., con domicilio a estos efectos en c/ Socuéllamos, 81 Pj Local 1, 13700 Tomelloso. Ust
>> ed podrá ejercitar sus derechos de acceso, rectificación, cancelación y oposición enviándonos un email a borrame at ibersontel.es "
>> El 13/01/2015 11:12, Daniel Grotti escribió:
>>> Hi,
>>> frankly I don't see the relationship.
>>> Fraud lock works on billing database.
>>>
>>> Daniel
>>>
>>>
>>>
>>> On 01/13/2015 11:07 AM, Jorge Fresneda - Ibersontel wrote:
>>>> Hi Daniel,
>>>>
>>>> Since I changed xmlhosts table, I see every half hour, the
>>>> ngcp-fraud-dail service overhead system (130% CPU). Why?
>>>>
>>>> Thanks,
>>>> Regards,
>>>> Jorge
>>>> Este mensaje es privado y confidencial y se dirige exclusivamente a su destinatario. Si usted ha recibido este mensaje por error, le rogamos que, si es posible, nos lo comunique respondiendo a este correo. "De conformidad con lo establecido en la Ley Orgánica 15/1999, de 13 de diciembre, de Protección de Datos de Carácter Personal, y en la Ley 34/2002, de 11 de julio, de Servicios de la Sociedad de la Información y de Comercio Electrónico, usted queda informado de la incorporación de sus datos en los ficheros correspondientes debidamente registrados en la Agencia Española de Protección de Datos y del tratamiento de los mismos para las finalidades de gestión de los usuarios, clientes y contactos comerciales de la compañía. El Responsable de dicho fichero es: IBERSONTEL, S.L., con domicilio a estos efectos en c/ Socuéllamos, 81 Pj Local 1, 13700 Tomelloso.
>>>> Ust
>>>> ed podrá ejercitar sus derechos de acceso, rectificación, cancelación y oposición enviándonos un email a borrame at ibersontel.es "
>>>> El 13/01/2015 11:03, Daniel Grotti escribió:
>>>>> Hi,
>>>>> looks good for a 2.8.
>>>>>
>>>>> Daniel
>>>>>
>>>>>
>>>>> On 01/13/2015 10:53 AM, Jorge Fresneda - Ibersontel wrote:
>>>>>> Hi Daniel,
>>>>>>
>>>>>> Ok, I will do it.
>>>>>>
>>>>>> This is the output of mysql_values.cfg:
>>>>>>
>>>>>> IADDRESS='127.0.0.1'
>>>>>> ASTERISK_PORT='5070'
>>>>>> SEMS_PORT='5080'
>>>>>> SEMS_XMLRPCPORT='8090'
>>>>>> KAMAILIO_LB_PORT='5060'
>>>>>> KAMAILIO_PROXY_PORT='5062'
>>>>>>
>>>>>> It's correct?
>>>>>>
>>>>>> Jorge
>>>>>>
>>>>>> Este mensaje es privado y confidencial y se dirige exclusivamente a su destinatario. Si usted ha recibido este mensaje por error, le rogamos que, si es posible, nos lo comunique respondiendo a este correo. "De conformidad con lo establecido en la Ley Orgánica 15/1999, de 13 de diciembre, de Protección de Datos de Carácter Personal, y en la Ley 34/2002, de 11 de julio, de Servicios de la Sociedad de la Información y de Comercio Electrónico, usted queda informado de la incorporación de sus datos en los ficheros correspondientes debidamente registrados en la Agencia Española de Protección de Datos y del tratamiento de los mismos para las finalidades de gestión de los usuarios, clientes y contactos comerciales de la compañía. El Responsable de dicho fichero es: IBERSONTEL, S.L., con domicilio a estos efectos en c/ Socuéllamos, 81 Pj Local 1, 13700 Tomell
>>>>>> oso.
>>>>>> Ust
>>>>>> ed podrá ejercitar sus derechos de acceso, rectificación, cancelación y oposición enviándonos un email a borrame at ibersontel.es "
>>>>>> El 13/01/2015 10:36, Daniel Grotti escribió:
>>>>>>> Hi,
>>>>>>> it shouldn't affect the service.
>>>>>>> You can run it on low load if you want.
>>>>>>>
>>>>>>> One more thing, what's the output of:
>>>>>>>
>>>>>>> # cat /etc/ngcp-ossbss/mysql_values.cfg
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>> Daniel
>>>>>>>
>>>>>>>
>>>>>>> On 01/13/2015 10:30 AM, Jorge Fresneda - Ibersontel wrote:
>>>>>>>> Hi Daniel,
>>>>>>>>
>>>>>>>> The changes have working correctly. It was the problem.
>>>>>>>>
>>>>>>>> The server is in production. The "bash" command, will stop service?
>>>>>>>>
>>>>>>>> Thank you so much,
>>>>>>>> Regards,
>>>>>>>> Jorge
>>>>>>>> Este mensaje es privado y confidencial y se dirige exclusivamente a su destinatario. Si usted ha recibido este mensaje por error, le rogamos que, si es posible, nos lo comunique respondiendo a este correo. "De conformidad con lo establecido en la Ley Orgánica 15/1999, de 13 de diciembre, de Protección de Datos de Carácter Personal, y en la Ley 34/2002, de 11 de julio, de Servicios de la Sociedad de la Información y de Comercio Electrónico, usted queda informado de la incorporación de sus datos en los ficheros correspondientes debidamente registrados en la Agencia Española de Protección de Datos y del tratamiento de los mismos para las finalidades de gestión de los usuarios, clientes y contactos comerciales de la compañía. El Responsable de dicho fichero es: IBERSONTEL, S.L., con domicilio a estos efectos en c/ Socuéllamos, 81 Pj Local 1, 13700 To
>>>>>>>> mell
>>>>>>>> oso.
>>>>>>>> Ust
>>>>>>>> ed podrá ejercitar sus derechos de acceso, rectificación, cancelación y oposición enviándonos un email a borrame at ibersontel.es "
>>>>>>>> El 13/01/2015 10:22, Daniel Grotti escribió:
>>>>>>>>> After the changes, please run the following command:
>>>>>>>>>
>>>>>>>>> # bash
>>>>>>>>> /etc/ngcp-config/templates/etc/ngcp-ossbss/mysql_values.cfg.services
>>>>>>>>>
>>>>>>>>> Daniel
>>>>>>>>>
>>>>>>>>>
>>>>>>>>> On 01/13/2015 10:06 AM, Daniel Grotti wrote:
>>>>>>>>>> Hi,
>>>>>>>>>> so please change the ip into xmlhosts, with localhost.
>>>>>>>>>> This should solve the problem.
>>>>>>>>>>
>>>>>>>>>> Daniel
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>> On 01/13/2015 10:03 AM, Jorge Fresneda - Ibersontel wrote:
>>>>>>>>>>> Hi Daniel,
>>>>>>>>>>>
>>>>>>>>>>> Yes, I think there is a mistake. This is the output:
>>>>>>>>>>>
>>>>>>>>>>> netstat -anp | grep 5062
>>>>>>>>>>> tcp 0 0 127.0.0.1:5062
>>>>>>>>>>> 0.0.0.0:* LISTEN 20799/kamailio
>>>>>>>>>>> udp 0 0 127.0.0.1:5062
>>>>>>>>>>> 0.0.0.0:* 20780/kamailio
>>>>>>>>>>> Este mensaje es privado y confidencial y se dirige exclusivamente a su destinatario. Si usted ha recibido este mensaje por error, le rogamos que, si es posible, nos lo comunique respondiendo a este correo. "De conformidad con lo establecido en la Ley Orgánica 15/1999, de 13 de diciembre, de Protección de Datos de Carácter Personal, y en la Ley 34/2002, de 11 de julio, de Servicios de la Sociedad de la Información y de Comercio Electrónico, usted queda informado de la incorporación de sus datos en los ficheros correspondientes debidamente registrados en la Agencia Española de Protección de Datos y del tratamiento de los mismos para las finalidades de gestión de los usuarios, clientes y contactos comerciales de la compañía. El Responsable de dicho fichero es: IBERSONTEL, S.L., con domicilio a estos efectos en c/ Socuéllamos, 81 Pj Local 1, 13
>>>>>>>>>>> 700
>>>>>>>>>>> Tome
>>>>>>>>>>> llos
>>>>>>>>>>> o. Ust
>>>>>>>>>>> ed podrá ejercitar sus derechos de acceso, rectificación, cancelación y oposición enviándonos un email a borrame at ibersontel.es "
>>>>>>>>>>> El 13/01/2015 10:01, Daniel Grotti escribió:
>>>>>>>>>>>> Yes,
>>>>>>>>>>>> but the 5062 should listen on localhost, not on your
>>>>>>>>>>>> virtual IP.
>>>>>>>>>>>> Please share the output of :
>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>> netstat -anp | grep 5062
>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>> Daniel
>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>> On 01/13/2015 09:58 AM, Jorge Fresneda - Ibersontel wrote:
>>>>>>>>>>>>> Hi Daniel,
>>>>>>>>>>>>>
>>>>>>>>>>>>> I'm sorry, the ip is 149.12.68.36. the log is:
>>>>>>>>>>>>>
>>>>>>>>>>>>> {'callee_pattern' =>
>>>>>>>>>>>>> '^sip:.+661457009@*149.12.68.36*$','callee_prefix' =>
>>>>>>>>>>>>> '34','caller_pattern' => '','description' => '','id' =>
>>>>>>>>>>>>> '189'}]}
>>>>>>>>>>>>>
>>>>>>>>>>>>> The Ip 1.1.1.1 is a test server.
>>>>>>>>>>>>>
>>>>>>>>>>>>> Thank you,
>>>>>>>>>>>>>
>>>>>>>>>>>>> Regards,
>>>>>>>>>>>>> Jorge
>>>>>>>>>>>>> Este mensaje es privado y confidencial y se dirige exclusivamente a su destinatario. Si usted ha recibido este mensaje por error, le rogamos que, si es posible, nos lo comunique respondiendo a este correo. "De conformidad con lo establecido en la Ley Orgánica 15/1999, de 13 de diciembre, de Protección de Datos de Carácter Personal, y en la Ley 34/2002, de 11 de julio, de Servicios de la Sociedad de la Información y de Comercio Electrónico, usted queda informado de la incorporación de sus datos en los ficheros correspondientes debidamente registrados en la Agencia Española de Protección de Datos y del tratamiento de los mismos para las finalidades de gestión de los usuarios, clientes y contactos comerciales de la compañía. El Responsable de dicho fichero es: IBERSONTEL, S.L., con domicilio a estos efectos en c/ Socuéllamos, 81 Pj Local 1
>>>>>>>>>>>>> , 13
>>>>>>>>>>>>> 700
>>>>>>>>>>>>> Tome
>>>>>>>>>>>>> lloso.
>>>>>>>>>>>>> Usted podrá ejercitar sus derechos de acceso, rectificación, cancelación y oposición en
>>>>>>>>>>>>>
>>>>>>>>>>>>> viándonos un email a borrame at ibersontel.es "
>>>>>>>>>>>>> El 13/01/2015 9:39, Daniel Grotti escribió:
>>>>>>>>>>>>>> Hi,
>>>>>>>>>>>>>> did you change the loopback interface with a dummy interface 149.12.68.36 ?
>>>>>>>>>>>>>> Is kamailio actually listening on 149.12.68.36:5062 ?
>>>>>>>>>>>>>>
>>>>>>>>>>>>>>
>>>>>>>>>>>>>> Daniel
>>>>>>>>>>>>>>
>>>>>>>>>>>>>>
>>>>>>>>>>>>>>
>>>>>>>>>>>>>> On 01/13/2015 09:32 AM, Jorge Fresneda - Ibersontel wrote:
>>>>>>>>>>>>>>> Hi Daniel
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>> Yes, my xmlhosts table has four lines:
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>> +----+--------------+------+-------+----------+--------------+
>>>>>>>>>>>>>>> | id | ip | port | path | sip_port | description |
>>>>>>>>>>>>>>> +----+--------------+------+-------+----------+--------------+
>>>>>>>>>>>>>>> | 1 | 149.12.68.36 | 8000 | /RPC2 | 5062 | Kamailio |
>>>>>>>>>>>>>>> | 2 | 149.12.68.36 | 8090 | / | NULL | Sems |
>>>>>>>>>>>>>>> | 3 | 149.12.68.36 | 5062 | / | NULL | Kamailio-SR |
>>>>>>>>>>>>>>> | 4 | 149.12.68.36 | 5060 | / | NULL | Loadbalancer |
>>>>>>>>>>>>>>> +----+--------------+------+-------+----------+--------------+
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>> Also,I have verified that the new rule that I added is in the oss log
>>>>>>>>>>>>>>> but then not apply. This is:
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>> {'callee_pattern' => '^sip:.+661457009 at 1.1.1.1$','callee_prefix' =>
>>>>>>>>>>>>>>> '34','caller_pattern' => '','description' => '','id' => '189'}]}
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>> Then, when I put ngcp-sercmd proxy lcr.dump_rules, the rule isn't.
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>> Why?
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>> Regards,
>>>>>>>>>>>>>>> Jorge
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>> Este mensaje es privado y confidencial y se dirige exclusivamente a su
>>>>>>>>>>>>>>> destinatario. Si usted ha recibido este mensaje por error, le rogamos
>>>>>>>>>>>>>>> que, si es posible, nos lo comunique respondiendo a este correo. "De
>>>>>>>>>>>>>>> conformidad con lo establecido en la Ley Orgánica 15/1999, de 13 de
>>>>>>>>>>>>>>> diciembre, de Protección de Datos de Carácter Personal, y en la Ley
>>>>>>>>>>>>>>> 34/2002, de 11 de julio, de Servicios de la Sociedad de la Información
>>>>>>>>>>>>>>> y de Comercio Electrónico, usted queda informado de la incorporación
>>>>>>>>>>>>>>> de sus datos en los ficheros correspondientes debidamente registrados
>>>>>>>>>>>>>>> en la Agencia Española de Protección de Datos y del tratamiento de los
>>>>>>>>>>>>>>> mismos para las finalidades de gestión de los usuarios, clientes y
>>>>>>>>>>>>>>> contactos comerciales de la compañía. El Responsable de dicho fichero
>>>>>>>>>>>>>>> es: IBERSONTEL, S.L., con domicilio a estos efectos en c/ Socuéllamos,
>>>>>>>>>>>>>>> 81 Pj Local 1, 13700 Tomelloso. Usted podrá ejercitar sus derechos de
>>>>>>>>>>>>>>> acceso, rectificación, cancelación y oposición enviándonos un email a
>>>>>>>>>>>>>>> borrame at ibersontel.es "
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>> El 12/01/2015 10:10, Jorge Fresneda - Ibersontel escribió:
>>>>>>>>>>>>>>>> Hello Daniel,
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>> Yes, my xmlhosts table has four lines:
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>> +----+--------------+------+-------+----------+--------------+
>>>>>>>>>>>>>>>> | id | ip | port | path | sip_port | description |
>>>>>>>>>>>>>>>> +----+--------------+------+-------+----------+--------------+
>>>>>>>>>>>>>>>> | 1 | 149.12.68.36 | 8000 | /RPC2 | 5062 | Kamailio |
>>>>>>>>>>>>>>>> | 2 | 149.12.68.36 | 8090 | / | NULL | Sems |
>>>>>>>>>>>>>>>> | 3 | 149.12.68.36 | 5062 | / | NULL | Kamailio-SR |
>>>>>>>>>>>>>>>> | 4 | 149.12.68.36 | 5060 | / | NULL | Loadbalancer |
>>>>>>>>>>>>>>>> +----+--------------+------+-------+----------+--------------+
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>> In oss log, I get following it:
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>> Jan 12 10:06:00 INTXSIPCLPR02 apache2: [info] [client
>>>>>>>>>>>>>>>> 149.12.69.2] Connection to child 0 established (server myserver:443)
>>>>>>>>>>>>>>>> Jan 12 10:06:00 INTXSIPCLPR02 apache2: [info] Seeding PRNG with 656
>>>>>>>>>>>>>>>> bytes of entropy
>>>>>>>>>>>>>>>> Jan 12 10:06:01 INTXSIPCLPR02 apache2: [info] [client 149.12.69.2]
>>>>>>>>>>>>>>>> (70014)End of file found: SSL input filter read failed.
>>>>>>>>>>>>>>>> Jan 12 10:06:01 INTXSIPCLPR02 apache2: [info] [client 149.12.69.2]
>>>>>>>>>>>>>>>> Connection closed to child 0 with standard shutdown (server
>>>>>>>>>>>>>>>> myserver:443)
>>>>>>>>>>>>>>>> Jan 12 10:06:01 INTXSIPCLPR02 apache2: [info] [client 149.12.69.2]
>>>>>>>>>>>>>>>> Connection to child 2 established (server myserver:443)
>>>>>>>>>>>>>>>> Jan 12 10:06:01 INTXSIPCLPR02 apache2: [info] Seeding PRNG with 656
>>>>>>>>>>>>>>>> bytes of entropy
>>>>>>>>>>>>>>>> Jan 12 10:06:01 INTXSIPCLPR02 apache2: [info] Initial (No.1) HTTPS
>>>>>>>>>>>>>>>> request received for child 2 (server myserver:443)
>>>>>>>>>>>>>>>> Jan 12 10:06:01 INTXSIPCLPR02 provisioning:
>>>>>>>>>>>>>>>> Sipwise::Provisioning::_log_xmldata: get_peer_group_details called
>>>>>>>>>>>>>>>> with: {'authentication' => {'password' => '********','type' =>
>>>>>>>>>>>>>>>> 'admin','username' => 'administrator'},'parameters' => {'id' => '7'}}
>>>>>>>>>>>>>>>> Jan 12 10:06:01 INTXSIPCLPR02 provisioning:
>>>>>>>>>>>>>>>> Sipwise::Provisioning::handle_request: calling function
>>>>>>>>>>>>>>>> 'get_peer_group_details' for admin 'administrator'
>>>>>>>>>>>>>>>> Jan 12 10:06:01 INTXSIPCLPR02 provisioning:
>>>>>>>>>>>>>>>> Sipwise::Provisioning::_log_xmldata: get_peer_group_details returned
>>>>>>>>>>>>>>>> with: {'group' => {'description' => 'RUTA1','id' => '7','name' =>
>>>>>>>>>>>>>>>> 'RUTA1_A','peering_contract_id' => '2','priority' => '4'},'peers' =>
>>>>>>>>>>>>>>>> [{'group_id' => '7','host' => undef,'id' => '7','ip' =>
>>>>>>>>>>>>>>>> '212.106.213.37','name' => 'BL0I002MAD01X','port' =>
>>>>>>>>>>>>>>>> '5060','transport' => 'UDP','weight' => '1'}],'rules' =>
>>>>>>>>>>>>>>>> [{'callee_pattern' => '^sip:.+912773274 at 1.1.1.1$','callee_prefix' =>
>>>>>>>>>>>>>>>> '34','caller_pattern' => '','description' => '','id' =>
>>>>>>>>>>>>>>>> '111'},{'callee_pattern' =>
>>>>>>>>>>>>>>>> '^sip:.+902401402 at 1.1.1.1$','callee_prefix' => '34','caller_pattern'
>>>>>>>>>>>>>>>> => '','description' => '','id' => '152'},{'callee_pattern' =>
>>>>>>>>>>>>>>>> '','callee_prefix' => '','caller_pattern' =>
>>>>>>>>>>>>>>>> '926514350','description' => 'Dataf','id' => '156'},{'callee_pattern'
>>>>>>>>>>>>>>>> => '','callee_prefix' => '','caller_pattern' =>
>>>>>>>>>>>>>>>> '926610724','description' => 'Fax','id' => '174'},{'callee_pattern'
>>>>>>>>>>>>>>>> => '^sip:.+926274000 at 1.1.1.1$','callee_prefix' =>
>>>>>>>>>>>>>>>> '34','caller_pattern' => '','description' => 'Ser','id' =>
>>>>>>>>>>>>>>>> '185'},{'callee_pattern' =>
>>>>>>>>>>>>>>>> '^sip:.+661457009 at 1.1.1.1$','callee_prefix' => '34','caller_pattern'
>>>>>>>>>>>>>>>> => '','description' => '','id' => '189'}]}
>>>>>>>>>>>>>>>> Jan 12 10:06:01 INTXSIPCLPR02 /usr/sbin/apache2:
>>>>>>>>>>>>>>>> ***Provisioning::call_prov calling 'voip::get_peer_group_details'
>>>>>>>>>>>>>>>> Jan 12 10:06:01 INTXSIPCLPR02 oss: 149.12.69.2 - -
>>>>>>>>>>>>>>>> [12/Jan/2015:10:06:01 +0100] "GET
>>>>>>>>>>>>>>>> /peering/detail?group_id=7&reditid=189 HTTP/1.1" 200 5399
>>>>>>>>>>>>>>>> "https://1.1.1.1:1443/peering/detail?group_id=7" "Mozilla/5.0
>>>>>>>>>>>>>>>> (Windows NT 6.1; WOW64) AppleWebKit/537.36 (KHTML, like Gecko)
>>>>>>>>>>>>>>>> Chrome/39.0.2171.95 Safari/537.36"
>>>>>>>>>>>>>>>> Jan 12 10:06:09 INTXSIPCLPR02 apache2: [info] Subsequent (No.2) HTTPS
>>>>>>>>>>>>>>>> request received for child 2 (server myserver:443)
>>>>>>>>>>>>>>>> Jan 12 10:06:09 INTXSIPCLPR02 provisioning:
>>>>>>>>>>>>>>>> Sipwise::Provisioning::_log_xmldata: check_sip_uri_prefix called
>>>>>>>>>>>>>>>> with: {'authentication' => {'password' => '********','type' =>
>>>>>>>>>>>>>>>> 'admin','username' => 'administrator'},'parameters' => {'prefix' =>
>>>>>>>>>>>>>>>> '34'}}
>>>>>>>>>>>>>>>> Jan 12 10:06:09 INTXSIPCLPR02 provisioning:
>>>>>>>>>>>>>>>> Sipwise::Provisioning::handle_request: calling function
>>>>>>>>>>>>>>>> 'check_sip_uri_prefix' for admin 'administrator'
>>>>>>>>>>>>>>>> Jan 12 10:06:09 INTXSIPCLPR02 provisioning:
>>>>>>>>>>>>>>>> Sipwise::Provisioning::_log_xmldata: check_sip_uri_prefix returned
>>>>>>>>>>>>>>>> with: 1
>>>>>>>>>>>>>>>> Jan 12 10:06:09 INTXSIPCLPR02 provisioning:
>>>>>>>>>>>>>>>> Sipwise::Provisioning::_log_xmldata: check_sip_uri_pattern called
>>>>>>>>>>>>>>>> with: {'authentication' => {'password' => '********','type' =>
>>>>>>>>>>>>>>>> 'admin','username' => 'administrator'},'parameters' => {'pattern' =>
>>>>>>>>>>>>>>>> '^sip:.+661457007 at 1.1.1.1$'}}
>>>>>>>>>>>>>>>> Jan 12 10:06:09 INTXSIPCLPR02 provisioning:
>>>>>>>>>>>>>>>> Sipwise::Provisioning::handle_request: calling function
>>>>>>>>>>>>>>>> 'check_sip_uri_pattern' for admin 'administrator'
>>>>>>>>>>>>>>>> Jan 12 10:06:09 INTXSIPCLPR02 provisioning:
>>>>>>>>>>>>>>>> Sipwise::Provisioning::_log_xmldata: check_sip_uri_pattern returned
>>>>>>>>>>>>>>>> with: 1
>>>>>>>>>>>>>>>> Jan 12 10:06:09 INTXSIPCLPR02 provisioning:
>>>>>>>>>>>>>>>> Sipwise::Provisioning::_log_xmldata: check_sip_uri_pattern called
>>>>>>>>>>>>>>>> with: {'authentication' => {'password' => '********','type' =>
>>>>>>>>>>>>>>>> 'admin','username' => 'administrator'},'parameters' => {'pattern' =>
>>>>>>>>>>>>>>>> ''}}
>>>>>>>>>>>>>>>> Jan 12 10:06:09 INTXSIPCLPR02 provisioning:
>>>>>>>>>>>>>>>> Sipwise::Provisioning::handle_request: calling function
>>>>>>>>>>>>>>>> 'check_sip_uri_pattern' for admin 'administrator'
>>>>>>>>>>>>>>>> Jan 12 10:06:09 INTXSIPCLPR02 provisioning:
>>>>>>>>>>>>>>>> Sipwise::Provisioning::_log_xmldata: check_sip_uri_pattern returned
>>>>>>>>>>>>>>>> with: 1
>>>>>>>>>>>>>>>> Jan 12 10:06:09 INTXSIPCLPR02 provisioning:
>>>>>>>>>>>>>>>> Sipwise::Provisioning::_log_xmldata: get_peer_group_details called
>>>>>>>>>>>>>>>> with: {'authentication' => {'password' => '********','type' =>
>>>>>>>>>>>>>>>> 'admin','username' => 'administrator'},'parameters' => {'id' => '7'}}
>>>>>>>>>>>>>>>> Jan 12 10:06:09 INTXSIPCLPR02 provisioning:
>>>>>>>>>>>>>>>> Sipwise::Provisioning::handle_request: calling function
>>>>>>>>>>>>>>>> 'get_peer_group_details' for admin 'administrator'
>>>>>>>>>>>>>>>> Jan 12 10:06:09 INTXSIPCLPR02 provisioning:
>>>>>>>>>>>>>>>> Sipwise::Provisioning::_log_xmldata: get_peer_group_details returned
>>>>>>>>>>>>>>>> with: {'group' => {'description' => 'RUTA1','id' => '7','name' =>
>>>>>>>>>>>>>>>> 'RUTA1_A','peering_contract_id' => '2','priority' => '4'},'peers' =>
>>>>>>>>>>>>>>>> [{'group_id' => '7','host' => undef,'id' => '7','ip' =>
>>>>>>>>>>>>>>>> '212.106.213.37','name' => 'BL0I002MAD01X','port' =>
>>>>>>>>>>>>>>>> '5060','transport' => 'UDP','weight' => '1'}],'rules' =>
>>>>>>>>>>>>>>>> [{'callee_pattern' => '^sip:.+912773274 at 1.1.1.1$','callee_prefix' =>
>>>>>>>>>>>>>>>> '34','caller_pattern' => '','description' => '','id' =>
>>>>>>>>>>>>>>>> '111'},{'callee_pattern' =>
>>>>>>>>>>>>>>>> '^sip:.+902401402 at 1.1.1.1$','callee_prefix' => '34','caller_pattern'
>>>>>>>>>>>>>>>> => '','description' => '','id' => '152'},{'callee_pattern' =>
>>>>>>>>>>>>>>>> '','callee_prefix' => '','caller_pattern' =>
>>>>>>>>>>>>>>>> '926514350','description' => 'Dataf','id' => '156'},{'callee_pattern'
>>>>>>>>>>>>>>>> => '','callee_prefix' => '','caller_pattern' =>
>>>>>>>>>>>>>>>> '926610724','description' => 'Fax','id' => '174'},{'callee_pattern'
>>>>>>>>>>>>>>>> => '^sip:.+926274000 at 1.1.1.1$','callee_prefix' =>
>>>>>>>>>>>>>>>> '34','caller_pattern' => '','description' => 'Ser','id' =>
>>>>>>>>>>>>>>>> '185'},{'callee_pattern' =>
>>>>>>>>>>>>>>>> '^sip:.+661457009 at 1.1.1.1$','callee_prefix' => '34','caller_pattern'
>>>>>>>>>>>>>>>> => '','description' => '','id' => '189'}]}
>>>>>>>>>>>>>>>> Jan 12 10:06:09 INTXSIPCLPR02 provisioning:
>>>>>>>>>>>>>>>> Sipwise::Provisioning::_log_xmldata: update_peer_rule called with:
>>>>>>>>>>>>>>>> {'authentication' => {'password' => '********','type' =>
>>>>>>>>>>>>>>>> 'admin','username' => 'administrator'},'parameters' => {'data' =>
>>>>>>>>>>>>>>>> {'callee_pattern' => '^sip:.+661457007 at 1.1.1.1$','callee_prefix' =>
>>>>>>>>>>>>>>>> '34','caller_pattern' => '','description' => ''},'id' => '189'}}
>>>>>>>>>>>>>>>> Jan 12 10:06:09 INTXSIPCLPR02 provisioning:
>>>>>>>>>>>>>>>> Sipwise::Provisioning::handle_request: calling function
>>>>>>>>>>>>>>>> 'update_peer_rule' for admin 'administrator'
>>>>>>>>>>>>>>>> Jan 12 10:06:09 INTXSIPCLPR02 provisioning:
>>>>>>>>>>>>>>>> Sipwise::Provisioning::Config::new: using config file
>>>>>>>>>>>>>>>> "/etc/ngcp-ossbss/provisioning.conf"
>>>>>>>>>>>>>>>> Jan 12 10:06:09 INTXSIPCLPR02 provisioning:
>>>>>>>>>>>>>>>> Sipwise::Provisioning::new: Sipwise::Provisioning::XMLDispatcher
>>>>>>>>>>>>>>>> object initialized
>>>>>>>>>>>>>>>> Jan 12 10:06:09 INTXSIPCLPR02 provisioning:
>>>>>>>>>>>>>>>> Sipwise::Provisioning::XMLDispatcher::dispatch: dispatching xmlrpc
>>>>>>>>>>>>>>>> proxy-ng request to 1.1.1.1:5062/
>>>>>>>>>>>>>>>> Jan 12 10:06:09 INTXSIPCLPR02 provisioning:
>>>>>>>>>>>>>>>> Sipwise::Provisioning::_log_xmldata: update_peer_rule returned with:
>>>>>>>>>>>>>>>> undef
>>>>>>>>>>>>>>>> Jan 12 10:06:09 INTXSIPCLPR02 /usr/sbin/apache2:
>>>>>>>>>>>>>>>> ***Provisioning::call_prov calling 'voip::check_sip_uri_prefix'
>>>>>>>>>>>>>>>> Jan 12 10:06:09 INTXSIPCLPR02 /usr/sbin/apache2:
>>>>>>>>>>>>>>>> ***Provisioning::call_prov calling 'voip::check_sip_uri_pattern'
>>>>>>>>>>>>>>>> Jan 12 10:06:09 INTXSIPCLPR02 /usr/sbin/apache2:
>>>>>>>>>>>>>>>> ***Provisioning::call_prov calling 'voip::check_sip_uri_pattern'
>>>>>>>>>>>>>>>> Jan 12 10:06:09 INTXSIPCLPR02 /usr/sbin/apache2:
>>>>>>>>>>>>>>>> ***Provisioning::call_prov calling 'voip::get_peer_group_details'
>>>>>>>>>>>>>>>> Jan 12 10:06:09 INTXSIPCLPR02 /usr/sbin/apache2:
>>>>>>>>>>>>>>>> ***Provisioning::call_prov calling 'voip::update_peer_rule'
>>>>>>>>>>>>>>>> Jan 12 10:06:09 INTXSIPCLPR02 oss: 149.12.69.2 - -
>>>>>>>>>>>>>>>> [12/Jan/2015:10:06:09 +0100] "POST /peering/save_rule HTTP/1.1" 302
>>>>>>>>>>>>>>>> 786 "https://1.1.1.1:1443/peering/detail?group_id=7&reditid=189"
>>>>>>>>>>>>>>>> "Mozilla/5.0 (Windows NT 6.1; WOW64) AppleWebKit/537.36 (KHTML, like
>>>>>>>>>>>>>>>> Gecko) Chrome/39.0.2171.95 Safari/537.36"
>>>>>>>>>>>>>>>> Jan 12 10:06:09 INTXSIPCLPR02 apache2: [info] Subsequent (No.3) HTTPS
>>>>>>>>>>>>>>>> request received for child 2 (server myserver:443)
>>>>>>>>>>>>>>>> Jan 12 10:06:09 INTXSIPCLPR02 provisioning:
>>>>>>>>>>>>>>>> Sipwise::Provisioning::_log_xmldata: get_peer_group_details called
>>>>>>>>>>>>>>>> with: {'authentication' => {'password' => '********','type' =>
>>>>>>>>>>>>>>>> 'admin','username' => 'administrator'},'parameters' => {'id' => '7'}}
>>>>>>>>>>>>>>>> Jan 12 10:06:09 INTXSIPCLPR02 provisioning:
>>>>>>>>>>>>>>>> Sipwise::Provisioning::handle_request: calling function
>>>>>>>>>>>>>>>> 'get_peer_group_details' for admin 'administrator'
>>>>>>>>>>>>>>>> Jan 12 10:06:09 INTXSIPCLPR02 provisioning:
>>>>>>>>>>>>>>>> Sipwise::Provisioning::_log_xmldata: get_peer_group_details returned
>>>>>>>>>>>>>>>> with: {'group' => {'description' => 'RUTA1','id' => '7','name' =>
>>>>>>>>>>>>>>>> 'RUTA1_A','peering_contract_id' => '2','priority' => '4'},'peers' =>
>>>>>>>>>>>>>>>> [{'group_id' => '7','host' => undef,'id' => '7','ip' =>
>>>>>>>>>>>>>>>> '212.106.213.37','name' => 'BL0I002MAD01X','port' =>
>>>>>>>>>>>>>>>> '5060','transport' => 'UDP','weight' => '1'}],'rules' =>
>>>>>>>>>>>>>>>> [{'callee_pattern' => '^sip:.+912773274 at 1.1.1.1$','callee_prefix' =>
>>>>>>>>>>>>>>>> '34','caller_pattern' => '','description' => '','id' =>
>>>>>>>>>>>>>>>> '111'},{'callee_pattern' =>
>>>>>>>>>>>>>>>> '^sip:.+902401402 at 1.1.1.1$','callee_prefix' => '34','caller_pattern'
>>>>>>>>>>>>>>>> => '','description' => '','id' => '152'},{'callee_pattern' =>
>>>>>>>>>>>>>>>> '','callee_prefix' => '','caller_pattern' =>
>>>>>>>>>>>>>>>> '926514350','description' => 'Dataf','id' => '156'},{'callee_pattern'
>>>>>>>>>>>>>>>> => '','callee_prefix' => '','caller_pattern' =>
>>>>>>>>>>>>>>>> '926610724','description' => 'Fax','id' => '174'},{'callee_pattern'
>>>>>>>>>>>>>>>> => '^sip:.+926274000 at 1.1.1.1$','callee_prefix' =>
>>>>>>>>>>>>>>>> '34','caller_pattern' => '','description' => 'Ser','id' =>
>>>>>>>>>>>>>>>> '185'},{'callee_pattern' =>
>>>>>>>>>>>>>>>> '^sip:.+661457007 at 1.1.1.1$','callee_prefix' => '34','caller_pattern'
>>>>>>>>>>>>>>>> => '','description' => '','id' => '189'}]}
>>>>>>>>>>>>>>>> Jan 12 10:06:09 INTXSIPCLPR02 provisioning:
>>>>>>>>>>>>>>>> Sipwise::Provisioning::_log_xmldata: get_localized_string called
>>>>>>>>>>>>>>>> with: {'authentication' => {'password' => '********','type' =>
>>>>>>>>>>>>>>>> 'admin','username' => 'administrator'},'parameters' => {'code' =>
>>>>>>>>>>>>>>>> 'Server.Voip.SavedSettings','language' => 'en'}}
>>>>>>>>>>>>>>>> Jan 12 10:06:09 INTXSIPCLPR02 provisioning:
>>>>>>>>>>>>>>>> Sipwise::Provisioning::handle_request: calling function
>>>>>>>>>>>>>>>> 'get_localized_string' for admin 'administrator'
>>>>>>>>>>>>>>>> Jan 12 10:06:09 INTXSIPCLPR02 provisioning:
>>>>>>>>>>>>>>>> Sipwise::Provisioning::_log_xmldata: get_localized_string returned
>>>>>>>>>>>>>>>> with: 'Your settings have been saved.'
>>>>>>>>>>>>>>>> Jan 12 10:06:09 INTXSIPCLPR02 /usr/sbin/apache2:
>>>>>>>>>>>>>>>> ***Provisioning::call_prov calling 'voip::get_peer_group_details'
>>>>>>>>>>>>>>>> Jan 12 10:06:09 INTXSIPCLPR02 /usr/sbin/apache2:
>>>>>>>>>>>>>>>> ***Provisioning::call_prov calling 'voip::get_localized_string'
>>>>>>>>>>>>>>>> Jan 12 10:06:09 INTXSIPCLPR02 oss: 149.12.69.2 - -
>>>>>>>>>>>>>>>> [12/Jan/2015:10:06:09 +0100] "GET /peering/detail?group_id=7
>>>>>>>>>>>>>>>> HTTP/1.1" 200 4066
>>>>>>>>>>>>>>>> "https://1.1.1.1:1443/peering/detail?group_id=7&reditid=189"
>>>>>>>>>>>>>>>> "Mozilla/5.0 (Windows NT 6.1; WOW64) AppleWebKit/537.36 (KHTML, like
>>>>>>>>>>>>>>>> Gecko) Chrome/39.0.2171.95 Safari/537.36"
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>> It's correct?
>>>>>>>>>>>>>>>> Regards
>>>>>>>>>>>>>>>> Jorge
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>> Este mensaje es privado y confidencial y se dirige exclusivamente a
>>>>>>>>>>>>>>>> su destinatario. Si usted ha recibido este mensaje por error, le
>>>>>>>>>>>>>>>> rogamos que, si es posible, nos lo comunique respondiendo a este
>>>>>>>>>>>>>>>> correo. "De conformidad con lo establecido en la Ley Orgánica
>>>>>>>>>>>>>>>> 15/1999, de 13 de diciembre, de Protección de Datos de Carácter
>>>>>>>>>>>>>>>> Personal, y en la Ley 34/2002, de 11 de julio, de Servicios de la
>>>>>>>>>>>>>>>> Sociedad de la Información y de Comercio Electrónico, usted queda
>>>>>>>>>>>>>>>> informado de la incorporación de sus datos en los ficheros
>>>>>>>>>>>>>>>> correspondientes debidamente registrados en la Agencia Española de
>>>>>>>>>>>>>>>> Protección de Datos y del tratamiento de los mismos para las
>>>>>>>>>>>>>>>> finalidades de gestión de los usuarios, clientes y contactos
>>>>>>>>>>>>>>>> comerciales de la compañía. El Responsable de dicho fichero es:
>>>>>>>>>>>>>>>> IBERSONTEL, S.L., con domicilio a estos efectos en c/ Socuéllamos, 81
>>>>>>>>>>>>>>>> Pj Local 1, 13700 Tomelloso. Usted podrá ejercitar sus derechos de
>>>>>>>>>>>>>>>> acceso, rectificación, cancelación y oposición enviándonos un email a
>>>>>>>>>>>>>>>> borrame at ibersontel.es "
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>> El 09/01/2015 9:58, Daniel Grotti escribió:
>>>>>>>>>>>>>>>>> Hi,
>>>>>>>>>>>>>>>>> please check the following:
>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>> mysql> select * from provisioning.xmlhosts;
>>>>>>>>>>>>>>>>> +----+-----------+------+-------+----------+--------------+
>>>>>>>>>>>>>>>>> | id | ip | port | path | sip_port | description |
>>>>>>>>>>>>>>>>> +----+-----------+------+-------+----------+--------------+
>>>>>>>>>>>>>>>>> | 1 | 127.0.0.1 | 8000 | /RPC2 | 5062 | Kamailio |
>>>>>>>>>>>>>>>>> | 2 | 127.0.0.1 | 8090 | / | NULL | Sems |
>>>>>>>>>>>>>>>>> | 3 | 127.0.0.1 | 5062 | / | NULL | Kamailio-SR |
>>>>>>>>>>>>>>>>> | 4 | 127.0.0.1 | 5060 | / | NULL | Loadbalancer |
>>>>>>>>>>>>>>>>> +----+-----------+------+-------+----------+--------------+
>>>>>>>>>>>>>>>>> 4 rows in set (0.00 sec)
>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>> Also, when you add the rule from web interface, please check the
>>>>>>>>>>>>>>>>> /var/log/ngcp/oss.log, you should see the XMLRPC call to reloead the
>>>>>>>>>>>>>>>>> kamilio lcr module:
>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>> Example
>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>> Jan 9 09:55:50 sp1 provisioning:
>>>>>>>>>>>>>>>>> Sipwise::Provisioning::handle_request:
>>>>>>>>>>>>>>>>> calling function 'get_peer_group_details' for admin 'administrator'
>>>>>>>>>>>>>>>>> Jan 9 09:55:50 sp1 provisioning: Sipwise::Provisioning::_log_xmldata:
>>>>>>>>>>>>>>>>> get_peer_group_details returned with: {'group' => {'description' =>
>>>>>>>>>>>>>>>>> '','id' => '1','name' => 'test','peering_contract_id' =>
>>>>>>>>>>>>>>>>> '41','priority'
>>>>>>>>>>>>>>>>> => '1'},'peers' => [{'group_id' => '1','host' => undef,'id' => '1','ip'
>>>>>>>>>>>>>>>>> => '1.1.1.1','name' => 'test ','port' => '5060','transport' =>
>>>>>>>>>>>>>>>>> 'UDP','weight' => '1'}],'rules' => []}
>>>>>>>>>>>>>>>>> Jan 9 09:55:50 sp1 provisioning: Sipwise::Provisioning::_log_xmldata:
>>>>>>>>>>>>>>>>> create_peer_rule called with: {'authentication' => {'password' =>
>>>>>>>>>>>>>>>>> '********','type' => 'admin','username' =>
>>>>>>>>>>>>>>>>> 'administrator'},'parameters'
>>>>>>>>>>>>>>>>> => {'data' => {'callee_pattern' => '','callee_prefix' =>
>>>>>>>>>>>>>>>>> '34','caller_pattern' => '','description' => ''},'group_id' => '1'}}
>>>>>>>>>>>>>>>>> Jan 9 09:55:50 sp1 provisioning:
>>>>>>>>>>>>>>>>> Sipwise::Provisioning::handle_request:
>>>>>>>>>>>>>>>>> calling function 'create_peer_rule' for admin 'administrator'
>>>>>>>>>>>>>>>>> Jan 9 09:55:50 sp1 provisioning: Sipwise::Provisioning::Config::new:
>>>>>>>>>>>>>>>>> using config file "/etc/ngcp-ossbss/provisioning.conf"
>>>>>>>>>>>>>>>>> Jan 9 09:55:50 sp1 provisioning: Sipwise::Provisioning::new:
>>>>>>>>>>>>>>>>> Sipwise::Provisioning::XMLDispatcher object initialized
>>>>>>>>>>>>>>>>> Jan 9 09:55:50 sp1 provisioning:
>>>>>>>>>>>>>>>>> Sipwise::Provisioning::XMLDispatcher::dispatch: dispatching xmlrpc
>>>>>>>>>>>>>>>>> proxy-ng request to 127.0.0.1:5062/
>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>> Daniel
>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>> On 01/08/2015 01:30 PM, Jorge Fresneda - Ibersontel wrote:
>>>>>>>>>>>>>>>>>> Hi Daniel,
>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>> When I check command "ngcp-sercmd proxy lcr.dump_rules", this
>>>>>>>>>>>>>>>>>> rule
>>>>>>>>>>>>>>>>>> NOT appear, only when reload kamailio-proxy. I have to reload
>>>>>>>>>>>>>>>>>> something?
>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>> Thanks Daniel,
>>>>>>>>>>>>>>>>>> Regards,
>>>>>>>>>>>>>>>>>> Jorge
>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>> Este mensaje es privado y confidencial y se dirige exclusivamente a su
>>>>>>>>>>>>>>>>>> destinatario. Si usted ha recibido este mensaje por error, le rogamos
>>>>>>>>>>>>>>>>>> que, si es posible, nos lo comunique respondiendo a este correo. "De
>>>>>>>>>>>>>>>>>> conformidad con lo establecido en la Ley Orgánica 15/1999, de 13 de
>>>>>>>>>>>>>>>>>> diciembre, de Protección de Datos de Carácter Personal, y en la Ley
>>>>>>>>>>>>>>>>>> 34/2002, de 11 de julio, de Servicios de la Sociedad de la Información
>>>>>>>>>>>>>>>>>> y de Comercio Electrónico, usted queda informado de la incorporación
>>>>>>>>>>>>>>>>>> de sus datos en los ficheros correspondientes debidamente registrados
>>>>>>>>>>>>>>>>>> en la Agencia Española de Protección de Datos y del tratamiento de los
>>>>>>>>>>>>>>>>>> mismos para las finalidades de gestión de los usuarios, clientes y
>>>>>>>>>>>>>>>>>> contactos comerciales de la compañía. El Responsable de dicho fichero
>>>>>>>>>>>>>>>>>> es: IBERSONTEL, S.L., con domicilio a estos efectos en c/ Socuéllamos,
>>>>>>>>>>>>>>>>>> 81 Pj Local 1, 13700 Tomelloso. Usted podrá ejercitar sus derechos de
>>>>>>>>>>>>>>>>>> acceso, rectificación, cancelación y oposición enviándonos un email a
>>>>>>>>>>>>>>>>>> borrame at ibersontel.es "
>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>> El 08/01/2015 12:59, Daniel Grotti escribió:
>>>>>>>>>>>>>>>>>>> Hi,
>>>>>>>>>>>>>>>>>>> please try to add a rules and then check:
>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>> ngcp-sercmd proxy lcr.dump_rules
>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>> you should see your rule there.
>>>>>>>>>>>>>>>>>>> I tried but I can't reproduce it.
>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>> Daniel
>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>> On 01/08/2015 12:51 PM, Jorge Fresneda - Ibersontel wrote:
>>>>>>>>>>>>>>>>>>>> Hello Daniel,
>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>> Yes, always on 2.8 version. Also, I have a 2.4 on other
>>>>>>>>>>>>>>>>>>>> server and
>>>>>>>>>>>>>>>>>>>> working correctly here.
>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>> I go to "System Administration" -- Sip Peerings --
>>>>>>>>>>>>>>>>>>>> PEERENG_1 and I
>>>>>>>>>>>>>>>>>>>> add a Peering rule such as 34 (on callee prefix),
>>>>>>>>>>>>>>>>>>>> ^sip:.+911112 at domain$ (on callee Pattern). This peering has more
>>>>>>>>>>>>>>>>>>>> priority than "default route" in other peering.
>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>> Then, I do a call and don't working. The call does through
>>>>>>>>>>>>>>>>>>>> another
>>>>>>>>>>>>>>>>>>>> carrier. When I reload kamailio-proxy service, the rule works
>>>>>>>>>>>>>>>>>>>> correctly.
>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>> Why?
>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>> Thanks you so much,
>>>>>>>>>>>>>>>>>>>> Regards,
>>>>>>>>>>>>>>>>>>>> Jorge
>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>> Este mensaje es privado y confidencial y se dirige exclusivamente
>>>>>>>>>>>>>>>>>>>> a su
>>>>>>>>>>>>>>>>>>>> destinatario. Si usted ha recibido este mensaje por error, le
>>>>>>>>>>>>>>>>>>>> rogamos
>>>>>>>>>>>>>>>>>>>> que, si es posible, nos lo comunique respondiendo a este correo. "De
>>>>>>>>>>>>>>>>>>>> conformidad con lo establecido en la Ley Orgánica 15/1999, de 13 de
>>>>>>>>>>>>>>>>>>>> diciembre, de Protección de Datos de Carácter Personal, y en la Ley
>>>>>>>>>>>>>>>>>>>> 34/2002, de 11 de julio, de Servicios de la Sociedad de la
>>>>>>>>>>>>>>>>>>>> Información
>>>>>>>>>>>>>>>>>>>> y de Comercio Electrónico, usted queda informado de la incorporación
>>>>>>>>>>>>>>>>>>>> de sus datos en los ficheros correspondientes debidamente
>>>>>>>>>>>>>>>>>>>> registrados
>>>>>>>>>>>>>>>>>>>> en la Agencia Española de Protección de Datos y del tratamiento
>>>>>>>>>>>>>>>>>>>> de los
>>>>>>>>>>>>>>>>>>>> mismos para las finalidades de gestión de los usuarios, clientes y
>>>>>>>>>>>>>>>>>>>> contactos comerciales de la compañía. El Responsable de dicho
>>>>>>>>>>>>>>>>>>>> fichero
>>>>>>>>>>>>>>>>>>>> es: IBERSONTEL, S.L., con domicilio a estos efectos en c/
>>>>>>>>>>>>>>>>>>>> Socuéllamos,
>>>>>>>>>>>>>>>>>>>> 81 Pj Local 1, 13700 Tomelloso. Usted podrá ejercitar sus
>>>>>>>>>>>>>>>>>>>> derechos de
>>>>>>>>>>>>>>>>>>>> acceso, rectificación, cancelación y oposición enviándonos un
>>>>>>>>>>>>>>>>>>>> email a
>>>>>>>>>>>>>>>>>>>> borrame at ibersontel.es "
>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>> El 08/01/2015 12:16, Daniel Grotti escribió:
>>>>>>>>>>>>>>>>>>>>> Hi,
>>>>>>>>>>>>>>>>>>>>> it shouldn't happen.
>>>>>>>>>>>>>>>>>>>>> Is it happening always or sometimes ?
>>>>>>>>>>>>>>>>>>>>> Are you able to reproduce the problem and tell us how ?
>>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>> Daniel
>>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>> On 01/07/2015 09:27 AM, Jorge Fresneda - Ibersontel wrote:
>>>>>>>>>>>>>>>>>>>>>> Hello everyone,
>>>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>>> I have changed a peering rules and I see that I have to reload
>>>>>>>>>>>>>>>>>>>>>> kamailio services because if I don't reload kamailio-proxy
>>>>>>>>>>>>>>>>>>>>>> service,
>>>>>>>>>>>>>>>>>>>>>> not working. Why?
>>>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>>> Thank you very much,
>>>>>>>>>>>>>>>>>>>>>> Regards,
>>>>>>>>>>>>>>>>>>>>>> Jorge
>>>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>>> Este mensaje es privado y confidencial y se dirige exclusivamente
>>>>>>>>>>>>>>>>>>>>>> a su
>>>>>>>>>>>>>>>>>>>>>> destinatario. Si usted ha recibido este mensaje por error, le
>>>>>>>>>>>>>>>>>>>>>> rogamos
>>>>>>>>>>>>>>>>>>>>>> que, si es posible, nos lo comunique respondiendo a este
>>>>>>>>>>>>>>>>>>>>>> correo. "De
>>>>>>>>>>>>>>>>>>>>>> conformidad con lo establecido en la Ley Orgánica 15/1999, de
>>>>>>>>>>>>>>>>>>>>>> 13 de
>>>>>>>>>>>>>>>>>>>>>> diciembre, de Protección de Datos de Carácter Personal, y en la
>>>>>>>>>>>>>>>>>>>>>> Ley
>>>>>>>>>>>>>>>>>>>>>> 34/2002, de 11 de julio, de Servicios de la Sociedad de la
>>>>>>>>>>>>>>>>>>>>>> Información
>>>>>>>>>>>>>>>>>>>>>> y de Comercio Electrónico, usted queda informado de la
>>>>>>>>>>>>>>>>>>>>>> incorporación
>>>>>>>>>>>>>>>>>>>>>> de sus datos en los ficheros correspondientes debidamente
>>>>>>>>>>>>>>>>>>>>>> registrados
>>>>>>>>>>>>>>>>>>>>>> en la Agencia Española de Protección de Datos y del tratamiento de
>>>>>>>>>>>>>>>>>>>>>> los
>>>>>>>>>>>>>>>>>>>>>> mismos para las finalidades de gestión de los usuarios, clientes y
>>>>>>>>>>>>>>>>>>>>>> contactos comerciales de la compañía. El Responsable de dicho
>>>>>>>>>>>>>>>>>>>>>> fichero
>>>>>>>>>>>>>>>>>>>>>> es: IBERSONTEL, S.L., con domicilio a estos efectos en c/
>>>>>>>>>>>>>>>>>>>>>> Socuéllamos,
>>>>>>>>>>>>>>>>>>>>>> 81 Pj Local 1, 13700 Tomelloso. Usted podrá ejercitar sus
>>>>>>>>>>>>>>>>>>>>>> derechos de
>>>>>>>>>>>>>>>>>>>>>> acceso, rectificación, cancelación y oposición enviándonos un
>>>>>>>>>>>>>>>>>>>>>> email a
>>>>>>>>>>>>>>>>>>>>>> borrame at ibersontel.es "
>>>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>>> _______________________________________________
>>>>>>>>>>>>>>>>>>>>>> Spce-user mailing list
>>>>>>>>>>>>>>>>>>>>>> Spce-user at lists.sipwise.com
>>>>>>>>>>>>>>>>>>>>>> https://lists.sipwise.com/listinfo/spce-user
>>>>>>>>>>>>>>>>>>>>> _______________________________________________
>>>>>>>>>>>>>>>>>>>>> Spce-user mailing list
>>>>>>>>>>>>>>>>>>>>> Spce-user at lists.sipwise.com
>>>>>>>>>>>>>>>>>>>>> https://lists.sipwise.com/listinfo/spce-user
>>>>>>>>>>>>>>>>>>>> _______________________________________________
>>>>>>>>>>>>>>>>>>>> Spce-user mailing list
>>>>>>>>>>>>>>>>>>>> Spce-user at lists.sipwise.com
>>>>>>>>>>>>>>>>>>>> https://lists.sipwise.com/listinfo/spce-user
>>>>>>>>>>>>>>>>>>> _______________________________________________
>>>>>>>>>>>>>>>>>>> Spce-user mailing list
>>>>>>>>>>>>>>>>>>> Spce-user at lists.sipwise.com
>>>>>>>>>>>>>>>>>>> https://lists.sipwise.com/listinfo/spce-user
>>>>>>>>>>>>>>>>>> _______________________________________________
>>>>>>>>>>>>>>>>>> Spce-user mailing list
>>>>>>>>>>>>>>>>>> Spce-user at lists.sipwise.com
>>>>>>>>>>>>>>>>>> https://lists.sipwise.com/listinfo/spce-user
>>>>>>>>>>>>>>>>> _______________________________________________
>>>>>>>>>>>>>>>>> Spce-user mailing list
>>>>>>>>>>>>>>>>> Spce-user at lists.sipwise.com
>>>>>>>>>>>>>>>>> https://lists.sipwise.com/listinfo/spce-user
>>>>>>>>>>>>>>>> _______________________________________________
>>>>>>>>>>>>>>>> Spce-user mailing list
>>>>>>>>>>>>>>>> Spce-user at lists.sipwise.com
>>>>>>>>>>>>>>>> https://lists.sipwise.com/listinfo/spce-user
>>>>>>>>>>>>>>> _______________________________________________
>>>>>>>>>>>>>>> Spce-user mailing list
>>>>>>>>>>>>>>> Spce-user at lists.sipwise.com
>>>>>>>>>>>>>>> https://lists.sipwise.com/listinfo/spce-user
>>>>>>>>>>>>>> _______________________________________________
>>>>>>>>>>>>>> Spce-user mailing list
>>>>>>>>>>>>>> Spce-user at lists.sipwise.com
>>>>>>>>>>>>>> https://lists.sipwise.com/listinfo/spce-user
>>>>>>>>>>>>>
>>>>>>>>>>>>>
>>>>>>>>>>>>>
>>>>>>>>>>>>> _______________________________________________
>>>>>>>>>>>>> Spce-user mailing list
>>>>>>>>>>>>> Spce-user at lists.sipwise.com
>>>>>>>>>>>>> https://lists.sipwise.com/listinfo/spce-user
>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>> _______________________________________________
>>>>>>>>>>>> Spce-user mailing list
>>>>>>>>>>>> Spce-user at lists.sipwise.com
>>>>>>>>>>>> https://lists.sipwise.com/listinfo/spce-user
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>> _______________________________________________
>>>>>>>>>>> Spce-user mailing list
>>>>>>>>>>> Spce-user at lists.sipwise.com
>>>>>>>>>>> https://lists.sipwise.com/listinfo/spce-user
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>> _______________________________________________
>>>>>>>>>> Spce-user mailing list
>>>>>>>>>> Spce-user at lists.sipwise.com
>>>>>>>>>> https://lists.sipwise.com/listinfo/spce-user
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>> _______________________________________________
>>>>>>>>> Spce-user mailing list
>>>>>>>>> Spce-user at lists.sipwise.com
>>>>>>>>> https://lists.sipwise.com/listinfo/spce-user
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>> _______________________________________________
>>>>>>>> Spce-user mailing list
>>>>>>>> Spce-user at lists.sipwise.com
>>>>>>>> https://lists.sipwise.com/listinfo/spce-user
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>> _______________________________________________
>>>>>>> Spce-user mailing list
>>>>>>> Spce-user at lists.sipwise.com
>>>>>>> https://lists.sipwise.com/listinfo/spce-user
>>>>>>
>>>>>>
>>>>>>
>>>>>> _______________________________________________
>>>>>> Spce-user mailing list
>>>>>> Spce-user at lists.sipwise.com
>>>>>> https://lists.sipwise.com/listinfo/spce-user
>>>>>
>>>>>
>>>>>
>>>>> _______________________________________________
>>>>> Spce-user mailing list
>>>>> Spce-user at lists.sipwise.com
>>>>> https://lists.sipwise.com/listinfo/spce-user
>>>>
>>>>
>>>>
>>>> _______________________________________________
>>>> Spce-user mailing list
>>>> Spce-user at lists.sipwise.com
>>>> https://lists.sipwise.com/listinfo/spce-user
>>>
>>>
>>>
>>> _______________________________________________
>>> Spce-user mailing list
>>> Spce-user at lists.sipwise.com
>>> https://lists.sipwise.com/listinfo/spce-user
>>
>>
>>
>> _______________________________________________
>> Spce-user mailing list
>> Spce-user at lists.sipwise.com
>> https://lists.sipwise.com/listinfo/spce-user
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.sipwise.com/pipermail/spce-user_lists.sipwise.com/attachments/20150113/125f0ace/attachment-0001.html>
More information about the Spce-user
mailing list