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 > [email protected] > http://lists.opensips.org/cgi-bin/mailman/listinfo/users
_______________________________________________ Users mailing list [email protected] http://lists.opensips.org/cgi-bin/mailman/listinfo/users
