Re: [OpenSIPS-Users] use of is_from_gw directive from drouting module.
Hello Bogdan-Andrei. With this patch it's working correcty. Thanyou very much. -- - Sus datos de carácter personal (nombre, apellidos, dirección postal y de correo electrónico, etc.) son tratados para la gestión de su relación con la Entidad, así como para el envío de información sobre nuestra actividad y la de terceros relacionadas con la actividad de Consulting Smartic Solutions, S.L., CIF: B85130037, C/Pº de la Castellana, 135, 7ª planta, 28046 Madrid. Usted puede ejercer sus derechos de acceso, rectificación, cancelación y oposición dirigiéndose por escrito, con copia de un documento que acredite su identidad, a la dirección info (arroba) smartic.es. Este mensaje puede contener información confidencial. Si usted no es su destinatario, no debe leerlo, copiarlo, distribuirlo, ni hacer uso de la información que contiene. En este caso, por favor, llámenos o comuníquenoslo por escrito y borre este mensaje de su sistema. - -Mensaje original- De: Bogdan-Andrei Iancu bog...@opensips.org Para: \Miguel J.\ López Valverde mjlo...@smartic.es Cc: OpenSIPS users mailling list users@lists.opensips.org Asunto: Re: [OpenSIPS-Users] use of is_from_gw directive from drouting module. Fecha: Mon, 20 May 2013 15:05:49 +0300 Hello Miguel, Please apply and attached patch (recompile + reinstall) with the is_from_gw(2,n) format. Regards, Bogdan-Andrei Iancu OpenSIPS Founder and Developer http://www.opensips-solutions.com On 05/20/2013 11:37 AM, Miguel J. López Valverde wrote: Hello Bogdan-Andrei, Thanyou very much for this information, I had not undertood the information give on manuals. Enyway, I tried also this forms and did no work correctly: dr_gateways have the next information: mysql select * from dr_gateways; ++-+--++---++---++---+ | id | gwid| type | address| strip | pri_prefix | attrs | probe_mode | description | ++-+--++---++---++---+ | 1 | Provider_0 |2 | xxx.xxx.xxx.xxx| 0 | NULL | NULL | 0 |Provider_0_incoming| With the is_from_gw(2,n) or dr_is_gw($si,2,n) directives did the same and do not identify the carrier correctly. With the dr_is_gw directive, the next information appeared in the log file: ERROR:drouting:_is_dr_uri_gw: invalid sip uri xxx.xxx.xxx.xxx Can I do some more testing?, Best Regards. -- - Sus datos de carácter personal (nombre, apellidos, dirección postal y de correo electrónico, etc.) son tratados para la gestión de su relación con la Entidad, así como para el envío de información sobre nuestra actividad y la de terceros relacionadas con la actividad de Consulting Smartic Solutions, S.L., CIF: B85130037, C/Pº de la Castellana, 135, 7ª planta, 28046 Madrid. Usted puede ejercer sus derechos de acceso, rectificación, cancelación y oposición dirigiéndose por escrito, con copia de un documento que acredite su identidad, a la dirección info (arroba) smartic.es. Este mensaje puede contener información confidencial. Si usted no es su destinatario, no debe leerlo, copiarlo, distribuirlo, ni hacer uso de la información que contiene. En este caso, por favor, llámenos o comuníquenoslo por escrito y borre este mensaje de su sistema. - -Mensaje original- De: Bogdan-Andrei Iancu bog...@opensips.org Para: \Miguel J.\ López Valverde mjlo...@smartic.es Cc: OpenSIPS users mailling list users@lists.opensips.org Asunto: Re: [OpenSIPS-Users] use of is_from_gw directive from drouting module. Fecha: Fri, 17 May 2013 13:57:38 +0300 Hello Miguel, The 3 from the is_from_gw() matches the type column from the dr_gateways table - it has nothing to do with the dr_group table. Regards, Bogdan-Andrei Iancu OpenSIPS Founder and Developer http://www.opensips-solutions.com On 05/16/2013 11:18 PM, Miguel J. López Valverde wrote: Dear Bogdan-Andrei I've tried to asign a new group for this providers, (group 3, I can't asign it to group 0 because this group is used by another type of users). I've filled dr_groups registers with this new information, (dr_gateways was filled before, on 1.8 release): select * from dr_gateways; ++-+--++---++---++---+ | id | gwid| type | address| strip | pri_prefix | attrs | probe_mode | description | ++-+--++---++---++---+ | 1 | Provider_0 |2 | XXX.XXX.XXX.XXX| 0 | NULL | NULL | 0 | Provider0_incoming| select * from dr_groups; ++---+-+-+---+ | id | username
Re: [OpenSIPS-Users] use of is_from_gw directive from drouting module.
Hello Miguel, Thanks for testing - the fix was uploaded on GIT and it will be part of the next minor releases. Regards, Bogdan-Andrei Iancu OpenSIPS Founder and Developer http://www.opensips-solutions.com On 05/22/2013 12:01 PM, Miguel J. López Valverde wrote: Hello Bogdan-Andrei. With this patch it's working correcty. Thanyou very much. -- - Sus datos de carácter personal (nombre, apellidos, dirección postal y de correo electrónico, etc.) son tratados para la gestión de su relación con la Entidad, así como para el envío de información sobre nuestra actividad y la de terceros relacionadas con la actividad de Consulting Smartic Solutions, S.L., CIF: B85130037, C/Pº de la Castellana, 135, 7ª planta, 28046 Madrid. Usted puede ejercer sus derechos de acceso, rectificación, cancelación y oposición dirigiéndose por escrito, con copia de un documento que acredite su identidad, a la dirección info (arroba) smartic.es. Este mensaje puede contener información confidencial. Si usted no es su destinatario, no debe leerlo, copiarlo, distribuirlo, ni hacer uso de la información que contiene. En este caso, por favor, llámenos o comuníquenoslo por escrito y borre este mensaje de su sistema. - -Mensaje original- De: Bogdan-Andrei Iancu bog...@opensips.org Para: "\"Miguel J.\" López Valverde" mjlo...@smartic.es Cc: OpenSIPS users mailling list users@lists.opensips.org Asunto: Re: [OpenSIPS-Users] use of is_from_gw directive from drouting module. Fecha: Mon, 20 May 2013 15:05:49 +0300 Hello Miguel, Please apply and attached patch (recompile + reinstall) with the is_from_gw("2","n") format. Regards, Bogdan-Andrei Iancu OpenSIPS Founder and Developer http://www.opensips-solutions.com On 05/20/2013 11:37 AM, Miguel J. López Valverde wrote: Hello Bogdan-Andrei, Thanyou very much for this information, I had not undertood the information give on manuals. Enyway, I tried also this forms and did no work correctly: dr_gateways have the next information: mysql select * from dr_gateways; ++-+--++---++---++---+ | id | gwid | type | address | strip | pri_prefix | attrs | probe_mode | description | ++-+--++---++---++---+ | 1 | Provider_0 | 2 | xxx.xxx.xxx.xxx| 0 | NULL | NULL | 0 |Provider_0_incoming| With the is_from_gw("2","n") or dr_is_gw("$si","2","n") directives did the same and do not identify the carrier correctly. With the dr_is_gw directive, the next information appeared in the log file: ERROR:drouting:_is_dr_uri_gw: invalid sip uri xxx.xxx.xxx.xxx Can I do some more testing?, Best Regards. -- - Sus datos de carácter personal (nombre, apellidos, dirección postal y de correo electrónico, etc.) son tratados para la gestión de su relación con la Entidad, así como para el envío de información sobre nuestra actividad y la de terceros relacionadas con la actividad de Consulting Smartic Solutions, S.L., CIF: B85130037, C/Pº de la Castellana, 135, 7ª planta, 28046 Madrid. Usted puede ejercer sus derechos de acceso, rectificación, cancelación y oposición dirigiéndose por escrito, con copia de un documento que acredite su identidad, a la dirección info (arroba) smartic.es. Este mensaje puede contener información confidencial. Si usted no es su destinatario, no debe leerlo, copiarlo, distribuirlo
Re: [OpenSIPS-Users] use of is_from_gw directive from drouting module.
Hello Bogdan-Andrei, Thanyou very much for this information, I had not undertood the information give on manuals. Enyway, I tried also this forms and did no work correctly: dr_gateways have the next information: mysql select * from dr_gateways; ++-+--++---++---++---+ | id | gwid| type | address| strip | pri_prefix | attrs | probe_mode | description | ++-+--++---++---++---+ | 1 | Provider_0 |2 | xxx.xxx.xxx.xxx| 0 | NULL | NULL | 0 |Provider_0_incoming| With the is_from_gw(2,n) or dr_is_gw($si,2,n) directives did the same and do not identify the carrier correctly. With the dr_is_gw directive, the next information appeared in the log file: ERROR:drouting:_is_dr_uri_gw: invalid sip uri xxx.xxx.xxx.xxx Can I do some more testing?, Best Regards. -- - Sus datos de carácter personal (nombre, apellidos, dirección postal y de correo electrónico, etc.) son tratados para la gestión de su relación con la Entidad, así como para el envío de información sobre nuestra actividad y la de terceros relacionadas con la actividad de Consulting Smartic Solutions, S.L., CIF: B85130037, C/Pº de la Castellana, 135, 7ª planta, 28046 Madrid. Usted puede ejercer sus derechos de acceso, rectificación, cancelación y oposición dirigiéndose por escrito, con copia de un documento que acredite su identidad, a la dirección info (arroba) smartic.es. Este mensaje puede contener información confidencial. Si usted no es su destinatario, no debe leerlo, copiarlo, distribuirlo, ni hacer uso de la información que contiene. En este caso, por favor, llámenos o comuníquenoslo por escrito y borre este mensaje de su sistema. - -Mensaje original- De: Bogdan-Andrei Iancu bog...@opensips.org Para: \Miguel J.\ López Valverde mjlo...@smartic.es Cc: OpenSIPS users mailling list users@lists.opensips.org Asunto: Re: [OpenSIPS-Users] use of is_from_gw directive from drouting module. Fecha: Fri, 17 May 2013 13:57:38 +0300 Hello Miguel, The 3 from the is_from_gw() matches the type column from the dr_gateways table - it has nothing to do with the dr_group table. Regards, Bogdan-Andrei Iancu OpenSIPS Founder and Developer http://www.opensips-solutions.com On 05/16/2013 11:18 PM, Miguel J. López Valverde wrote: Dear Bogdan-Andrei I've tried to asign a new group for this providers, (group 3, I can't asign it to group 0 because this group is used by another type of users). I've filled dr_groups registers with this new information, (dr_gateways was filled before, on 1.8 release): select * from dr_gateways; ++-+--++---++---++---+ | id | gwid| type | address| strip | pri_prefix | attrs | probe_mode | description | ++-+--++---++---++---+ | 1 | Provider_0 |2 | XXX.XXX.XXX.XXX| 0 | NULL | NULL | 0 | Provider0_incoming| select * from dr_groups; ++---+-+-+---+ | id | username | domain | groupid | description | ++---+-+-+---+ | 24 | Provider_0| XXX.XXX.XXX.XXX| 3 | Provider0_incoming| And the new configuration: } else if (is_from_gw()) { # request comes from gw setflag(21); } else if (is_from_gw(3,n)) { # request comes from gw with strange udp-ports setflag(21); } With this configuration, the is_from_gw() directive is working right for providers without dr_groups db information and using 5060 port, but the is_from_gw(3,n) aren't working, it don't match with providers of group 3 and working with ports diferents of 5060. ¿Are this configuration wrong?. Thankyou very much for your help. -- - Sus datos de carácter personal (nombre, apellidos, dirección postal y de correo electrónico, etc.) son tratados para la gestión de su relación con la Entidad, así como para el envío de información sobre nuestra actividad y la de terceros relacionadas con la actividad de Consulting Smartic Solutions, S.L., CIF: B85130037, C/Pº de la Castellana, 135, 7ª planta, 28046 Madrid. Usted puede ejercer sus derechos de acceso, rectificación, cancelación y oposición dirigiéndose por escrito, con copia de un documento que acredite su identidad, a la dirección info (arroba) smartic.es. Este mensaje puede contener información confidencial. Si usted no es su destinatario, no debe leerlo, copiarlo, distribuirlo, ni hacer uso de la información que
Re: [OpenSIPS-Users] use of is_from_gw directive from drouting module.
Hello Miguel, Please apply and attached patch (recompile + reinstall) with the is_from_gw("2","n") format. Regards, Bogdan-Andrei Iancu OpenSIPS Founder and Developer http://www.opensips-solutions.com On 05/20/2013 11:37 AM, Miguel J. López Valverde wrote: Hello Bogdan-Andrei, Thanyou very much for this information, I had not undertood the information give on manuals. Enyway, I tried also this forms and did no work correctly: dr_gateways have the next information: mysql select * from dr_gateways; ++-+--++---++---++---+ | id | gwid | type | address | strip | pri_prefix | attrs | probe_mode | description | ++-+--++---++---++---+ | 1 | Provider_0 | 2 | xxx.xxx.xxx.xxx| 0 | NULL | NULL | 0 |Provider_0_incoming| With the is_from_gw("2","n") or dr_is_gw("$si","2","n") directives did the same and do not identify the carrier correctly. With the dr_is_gw directive, the next information appeared in the log file: ERROR:drouting:_is_dr_uri_gw: invalid sip uri xxx.xxx.xxx.xxx Can I do some more testing?, Best Regards. -- - Sus datos de carácter personal (nombre, apellidos, dirección postal y de correo electrónico, etc.) son tratados para la gestión de su relación con la Entidad, así como para el envío de información sobre nuestra actividad y la de terceros relacionadas con la actividad de Consulting Smartic Solutions, S.L., CIF: B85130037, C/Pº de la Castellana, 135, 7ª planta, 28046 Madrid. Usted puede ejercer sus derechos de acceso, rectificación, cancelación y oposición dirigiéndose por escrito, con copia de un documento que acredite su identidad, a la dirección info (arroba) smartic.es. Este mensaje puede contener información confidencial. Si usted no es su destinatario, no debe leerlo, copiarlo, distribuirlo, ni hacer uso de la información que contiene. En este caso, por favor, llámenos o comuníquenoslo por escrito y borre este mensaje de su sistema. - -Mensaje original- De: Bogdan-Andrei Iancu bog...@opensips.org Para: "\"Miguel J.\" López Valverde" mjlo...@smartic.es Cc: OpenSIPS users mailling list users@lists.opensips.org Asunto: Re: [OpenSIPS-Users] use of is_from_gw directive from drouting module. Fecha: Fri, 17 May 2013 13:57:38 +0300 Hello Miguel, The "3" from the is_from_gw() matches the "type" column" from the dr_gateways table - it has nothing to do with the dr_group table. Regards, Bogdan-Andrei Iancu OpenSIPS Founder and Developer http://www.opensips-solutions.com On 05/16/2013 11:18 PM, Miguel J. López Valverde wrote: Dear Bogdan-Andrei I've tried to asign a new group for this providers, (group 3, I can't asign it to group 0 because this group is used by another type of users). I've filled dr_groups registers with this new information, (dr_gateways was filled before, on 1.8 release): select * from dr_gateways; ++-+--++---++---++---+ | id | gwid | type | address | strip | pri_prefix | attrs | probe_mode | description | ++-+--++---++---++---+ | 1 | Provider_0 | 2 | XXX.XXX.XXX.XXX| 0 | NULL | NULL | 0 | Provider0_incoming| select * from dr_groups; ++---+-+-+---+ | id | username | domain | groupid | description | ++---+-+-+---+ | 24 | Provider_0 | XXX.XXX.XXX.XXX| 3 | Provider0_in
Re: [OpenSIPS-Users] use of is_from_gw directive from drouting module.
Hello Miguel, The "3" from the is_from_gw() matches the "type" column" from the dr_gateways table - it has nothing to do with the dr_group table. Regards, Bogdan-Andrei Iancu OpenSIPS Founder and Developer http://www.opensips-solutions.com On 05/16/2013 11:18 PM, Miguel J. López Valverde wrote: Dear Bogdan-Andrei I've tried to asign a new group for this providers, (group 3, I can't asign it to group 0 because this group is used by another type of users). I've filled dr_groups registers with this new information, (dr_gateways was filled before, on 1.8 release): select * from dr_gateways; ++-+--++---++---++---+ | id | gwid | type | address | strip | pri_prefix | attrs | probe_mode | description | ++-+--++---++---++---+ | 1 | Provider_0 | 2 | XXX.XXX.XXX.XXX| 0 | NULL | NULL | 0 | Provider0_incoming| select * from dr_groups; ++---+-+-+---+ | id | username | domain | groupid | description | ++---+-+-+---+ | 24 | Provider_0 | XXX.XXX.XXX.XXX| 3 | Provider0_incoming | And the new configuration: } else if (is_from_gw()) { # request comes from gw setflag(21); } else if (is_from_gw("3","n")) { # request comes from gw with strange udp-ports setflag(21); } With this configuration, the is_from_gw() directive is working right for providers without dr_groups db information and using 5060 port, but the is_from_gw("3","n") aren't working, it don't match with providers of group 3 and working with ports diferents of 5060. ¿Are this configuration wrong?. Thankyou very much for your help. -- - Sus datos de carácter personal (nombre, apellidos, dirección postal y de correo electrónico, etc.) son tratados para la gestión de su relación con la Entidad, así como para el envío de información sobre nuestra actividad y la de terceros relacionadas con la actividad de Consulting Smartic Solutions, S.L., CIF: B85130037, C/Pº de la Castellana, 135, 7ª planta, 28046 Madrid. Usted puede ejercer sus derechos de acceso, rectificación, cancelación y oposición dirigiéndose por escrito, con copia de un documento que acredite su identidad, a la dirección info (arroba) smartic.es. Este mensaje puede contener información confidencial. Si usted no es su destinatario, no debe leerlo, copiarlo, distribuirlo, ni hacer uso de la información que contiene. En este caso, por favor, llámenos o comuníquenoslo por escrito y borre este mensaje de su sistema. - -Mensaje original- De: Bogdan-Andrei Iancu bog...@opensips.org Para: OpenSIPS users mailling list users@lists.opensips.org Cc: "\"Miguel J.\" López Valverde" mjlo...@smartic.es Asunto: Re: [OpenSIPS-Users] use of is_from_gw directive from drouting module. Fecha: Wed, 15 May 2013 20:59:47 +0300 Hello Miguel, Starting with 1.9, DR module does SIP wise resolving of the destination (in order to find all the IPs behind the a FQDN, via NATPR, SRV and A lookups). A side effect is that according to SIP, no port means 5060. In your case, the "n" flag should do the trick - but I understand that when using it, your problem is what group to use (by the way, "" group is translated to group 0 ) . Are your GWs in various groups? Regards, Bogdan-Andrei Iancu OpenSIPS Founder and Developer http://www.opensips-solutions.com On 05/15/2013 04:16 AM, Miguel J. López Valverde wrote: Dear UserList Opensips: I used drouting with OpenSips 1.8.0 release, the gatew
Re: [OpenSIPS-Users] use of is_from_gw directive from drouting module.
Dear Bogdan-Andrei I've tried to asign a new group for this providers, (group 3, I can't asign it to group 0 because this group is used by another type of users). I've filled dr_groups registers with this new information, (dr_gateways was filled before, on 1.8 release): select * from dr_gateways; ++-+--++---++---++---+ | id | gwid| type | address| strip | pri_prefix | attrs | probe_mode | description | ++-+--++---++---++---+ | 1 | Provider_0 |2 | XXX.XXX.XXX.XXX| 0 | NULL | NULL | 0 | Provider0_incoming| select * from dr_groups; ++---+-+-+---+ | id | username | domain | groupid | description | ++---+-+-+---+ | 24 | Provider_0| XXX.XXX.XXX.XXX| 3 | Provider0_incoming| And the new configuration: } else if (is_from_gw()) { # request comes from gw setflag(21); } else if (is_from_gw(3,n)) { # request comes from gw with strange udp-ports setflag(21); } With this configuration, the is_from_gw() directive is working right for providers without dr_groups db information and using 5060 port, but the is_from_gw(3,n) aren't working, it don't match with providers of group 3 and working with ports diferents of 5060. ¿Are this configuration wrong?. Thankyou very much for your help. -- - Sus datos de carácter personal (nombre, apellidos, dirección postal y de correo electrónico, etc.) son tratados para la gestión de su relación con la Entidad, así como para el envío de información sobre nuestra actividad y la de terceros relacionadas con la actividad de Consulting Smartic Solutions, S.L., CIF: B85130037, C/Pº de la Castellana, 135, 7ª planta, 28046 Madrid. Usted puede ejercer sus derechos de acceso, rectificación, cancelación y oposición dirigiéndose por escrito, con copia de un documento que acredite su identidad, a la dirección info (arroba) smartic.es. Este mensaje puede contener información confidencial. Si usted no es su destinatario, no debe leerlo, copiarlo, distribuirlo, ni hacer uso de la información que contiene. En este caso, por favor, llámenos o comuníquenoslo por escrito y borre este mensaje de su sistema. - -Mensaje original- De: Bogdan-Andrei Iancu bog...@opensips.org Para: OpenSIPS users mailling list users@lists.opensips.org Cc: \Miguel J.\ López Valverde mjlo...@smartic.es Asunto: Re: [OpenSIPS-Users] use of is_from_gw directive from drouting module. Fecha: Wed, 15 May 2013 20:59:47 +0300 Hello Miguel, Starting with 1.9, DR module does SIP wise resolving of the destination (in order to find all the IPs behind the a FQDN, via NATPR, SRV and A lookups). A side effect is that according to SIP, no port means 5060. In your case, the n flag should do the trick - but I understand that when using it, your problem is what group to use (by the way, group is translated to group 0 ) . Are your GWs in various groups? Regards, Bogdan-Andrei Iancu OpenSIPS Founder and Developer http://www.opensips-solutions.com On 05/15/2013 04:16 AM, Miguel J. López Valverde wrote: Dear UserList Opensips: I used drouting with OpenSips 1.8.0 release, the gateways list was in the dr_gateways table and no ports where configurated in it. For incoming calls wasn't necesary. Now, I upgrade OpenSips to 1.9.1 release and for incoming calls from a few providers, I can't do match they whith the is_from_gw() directive. I tried in this diferents forms: is_from_gw(), OpenSips start and providers with 5060-udp port match fine, but a few providers who employ other random ports haven't match. is_from_gw(, n), OpenSips start but incoming calls haven't match with the gateways on dr_gateways table. is_from_gw(-1, n), OpenSips don't start. is_from_gw(diferents_formats, n), OpenSips start but incoming calls haven't match with the gateways on dr_gateways table. Then I need to ask you... ¿How I have to use the is_from_gw directive with n parameter and dr_gateways table with the list of incoming calls providers?. ¿Which is the field on the dr_gateways table where i can make match with type parameter on the is_from_gw directive?. Thanyou very much and best regards. Miguel J. López. ___ Users mailing list Users@lists.opensips.org http://lists.opensips.org/cgi-bin/mailman/listinfo/users attachment: firma_miguel_230x85.gif___ Users mailing list Users@lists.opensips.org http://lists.opensips.org/cgi-bin/mailman/listinfo/users
Re: [OpenSIPS-Users] use of is_from_gw directive from drouting module.
Try to use dr_is_gw(): http://www.opensips.org/html/docs/modules/1.9.x/drouting.html#id294057 Regards, Ovidiu Sas On Tue, May 14, 2013 at 9:16 PM, Miguel J. mjlo...@smartic.es wrote: Dear UserList Opensips: I used drouting with OpenSips 1.8.0 release, the gateways list was in the dr_gateways table and no ports where configurated in it. For incoming calls wasn't necesary. Now, I upgrade OpenSips to 1.9.1 release and for incoming calls from a few providers, I can't do match they whith the is_from_gw() directive. I tried in this diferents forms: is_from_gw(), OpenSips start and providers with 5060-udp port match fine, but a few providers who employ other random ports haven't match. is_from_gw(, n), OpenSips start but incoming calls haven't match with the gateways on dr_gateways table. is_from_gw(-1, n), OpenSips don't start. is_from_gw(diferents_formats, n), OpenSips start but incoming calls haven't match with the gateways on dr_gateways table. Then I need to ask you... ¿How I have to use the is_from_gw directive with n parameter and dr_gateways table with the list of incoming calls providers?. ¿Which is the field on the dr_gateways table where i can make match with type parameter on the is_from_gw directive?. Thanyou very much and best regards. Miguel J. López. ___ Users mailing list Users@lists.opensips.org http://lists.opensips.org/cgi-bin/mailman/listinfo/users -- VoIP Embedded, Inc. http://www.voipembedded.com ___ Users mailing list Users@lists.opensips.org http://lists.opensips.org/cgi-bin/mailman/listinfo/users
Re: [OpenSIPS-Users] use of is_from_gw directive from drouting module.
Hello Miguel, Starting with 1.9, DR module does SIP wise resolving of the destination (in order to find all the IPs behind the a FQDN, via NATPR, SRV and A lookups). A side effect is that according to SIP, no port means 5060. In your case, the n flag should do the trick - but I understand that when using it, your problem is what group to use (by the way, group is translated to group 0 ) . Are your GWs in various groups? Regards, Bogdan-Andrei Iancu OpenSIPS Founder and Developer http://www.opensips-solutions.com On 05/15/2013 04:16 AM, Miguel J. López Valverde wrote: Dear UserList Opensips: I used drouting with OpenSips 1.8.0 release, the gateways list was in the dr_gateways table and no ports where configurated in it. For incoming calls wasn't necesary. Now, I upgrade OpenSips to 1.9.1 release and for incoming calls from a few providers, I can't do match they whith the is_from_gw() directive. I tried in this diferents forms: is_from_gw(), OpenSips start and providers with 5060-udp port match fine, but a few providers who employ other random ports haven't match. is_from_gw(, n), OpenSips start but incoming calls haven't match with the gateways on dr_gateways table. is_from_gw(-1, n), OpenSips don't start. is_from_gw(diferents_formats, n), OpenSips start but incoming calls haven't match with the gateways on dr_gateways table. Then I need to ask you... ¿How I have to use the is_from_gw directive with n parameter and dr_gateways table with the list of incoming calls providers?. ¿Which is the field on the dr_gateways table where i can make match with type parameter on the is_from_gw directive?. Thanyou very much and best regards. Miguel J. López. ___ Users mailing list Users@lists.opensips.org http://lists.opensips.org/cgi-bin/mailman/listinfo/users ___ Users mailing list Users@lists.opensips.org http://lists.opensips.org/cgi-bin/mailman/listinfo/users
[OpenSIPS-Users] use of is_from_gw directive from drouting module.
Dear UserList Opensips: I used drouting with OpenSips 1.8.0 release, the gateways list was in the dr_gateways table and no ports where configurated in it. For incoming calls wasn't necesary. Now, I upgrade OpenSips to 1.9.1 release and for incoming calls from a few providers, I can't do match they whith the is_from_gw() directive. I tried in this diferents forms: is_from_gw(), OpenSips start and providers with 5060-udp port match fine, but a few providers who employ other random ports haven't match. is_from_gw(, n), OpenSips start but incoming calls haven't match with the gateways on dr_gateways table. is_from_gw(-1, n), OpenSips don't start. is_from_gw(diferents_formats, n), OpenSips start but incoming calls haven't match with the gateways on dr_gateways table. Then I need to ask you... ¿How I have to use the is_from_gw directive with n parameter and dr_gateways table with the list of incoming calls providers?. ¿Which is the field on the dr_gateways table where i can make match with type parameter on the is_from_gw directive?. Thanyou very much and best regards. Miguel J. López. ___ Users mailing list Users@lists.opensips.org http://lists.opensips.org/cgi-bin/mailman/listinfo/users