Hey folks, Just wanted to say thanks and provide an update in case others have this issue.
The problem was essentially that the ip address was in the domain table. I removed it from the domain table, adding it as an alias in the cfg and added an additional uri==myself when determining if an incoming call was local for a local host. Thanks again, -Daniel On Tue, Oct 16, 2012 at 4:33 AM, Andrew Pogrebennyk < [email protected]> wrote: > Daniel, > have you added perhaps your IP address to the domain table? > It is not supposed to be there and should be removed, otherwise opensips > thinks 192.168.117.4:5070 is itself as others pointed out. > > Also, if you have any checks in your script like: > if ( !is_from_local() && !is_uri_host_local() ) > you should replace them with the version which doesn't use domain table: > if ( from_uri != myself && uri != myself ) > > HTH. > Andrew > > On 10/16/2012 02:33 AM, Ali Pey wrote: > > What do you have for alias in your opensips.cfg? Opensips seems to > > think 192.168.117.4:5070 <http://192.168.117.4:5070> is itself. > > > > Regards, > > Ali Pey > > > > > > On Mon, Oct 15, 2012 at 6:33 PM, Daniel Eiland <[email protected] > > <mailto:[email protected]>> wrote: > > > > Hi folks, > > > > I've got an issue with ACK messages being looped when they are sent > > to an endpoint that is co-located with my OpenSIPS proxy. > > > > I've got OpenSIPS located on server A @ port 5060 and two conference > > endpoints: C01 on server A @ port 5070 and C02 on a separate server. > > > > When my client calls into C01, the ACK message is continually routed > > by OpenSIPS back into itself instead of the conference endpoint > > listening on port 5070. This doesn't happened when I call into C02, > > OpenSIPS properly routes it to the right destination. > > > > When I compare the two ACKs, they are fairly similar and when I > > looked at some OpenSIPS logs both messages are being routed in a > > similar fashion namely loose_route is true. The only difference > > (which I'm sure if the problem, I'm just not sure why) is that the > > ACK to C01 has Destination User ($du) of 192.168.117.4 while the ACK > > to C02 has a $du of NULL. > > > > If anyone has any suggestions, I'd be grateful. > > > > Thanks, > > Daniel > > > > Also here are the two ACKs for comparison: > > > > ACK sip:[email protected]:5070;transport=udp SIP/2.0 > > Via: SIP/2.0/UDP > > > QWE.RTY.XYZ.ABC:2453;rport;branch=z9hG4bKPjca04290517874935af64a839e6bf9701 > > Max-Forwards: 70 > > From: "deiland" <sip:[email protected] > > <mailto:sip%[email protected] > >>;tag=d02a111d4a064b05a7cf987b006bd001 > > To: <sip:[email protected] > > <mailto:sip%[email protected]>>;tag=ma94e0688avFj > > Call-ID: 5c35c0a5dcb442a9afd324c988bd0a3c > > CSeq: 24503 ACK > > Route: <sip:192.168.117.4;lr> > > User-Agent: Blink 0.2.7 (Windows) > > Content-Length: 0 > > > > > > ACK sip:[email protected]:5070;transport=udp SIP/2.0 > > Via: SIP/2.0/UDP > > > QWE.RTY.XYZ.ABC:2122;rport;branch=z9hG4bKPj5318936898454066944aadf64ad846d0 > > Max-Forwards: 70 > > From: "deiland" <sip:[email protected] > > <mailto:sip%[email protected] > >>;tag=ff6fb0856e264e7f96601529148bb206 > > To: <sip:[email protected] > > <mailto:sip%[email protected]>>;tag=54aZ48KZ7a9Xj > > Call-ID: afddb9bea6714f95bd84dff2159e2b14 > > CSeq: 11988 ACK > > Route: <sip:192.168.117.4;lr> > > User-Agent: Blink 0.2.7 (Windows) > > Content-Length: 0 > > > > > > > > _______________________________________________ > > Users mailing list > > [email protected] <mailto:[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 > > > > > _______________________________________________ > 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
