I have taken your initial suggestions and mofied by deployment. You were a great help in assisting me to see some loop holes in my configuration.
The updated configuration, based on your suggestions is attached. There is also a debug=10 trace attached for both a scenario where my asterisk server was shutdown (read: internal 408 response) and one where my server answered properly. It appears the failover routing/marking is working as desired. (Community) Thank you much for your engagement here. I understand we got off to a rocky start :) -Geoff On Wed, Feb 11, 2009 at 5:20 PM, Iñaki Baz Castillo <[email protected]> wrote: > El Miércoles, 11 de Febrero de 2009, Geoffrey Mina escribió: >> ## If we are in-dialog loose_route() should return true and we should >> ## end up here. I am not sure the subsequent check of has_totag() is >> ## necessary, but I could be wrong. > > Yes, you should do it. In your actual config, if an in-dialog request (To tag) > with no Route headers arrives, your OpenSIPS will accept it (loose_route > returns false since there is no Route headers). > > An in-dialog request with no Route header should never arrive toa proxy, since > a proxy only remains in the dialog path if it added Record-Route header, so > in-dialog requests would have Route header. If not, they are invalid/spoofed. > > > -- > Iñaki Baz Castillo > > _______________________________________________ > Users mailing list > [email protected] > http://lists.opensips.org/cgi-bin/mailman/listinfo/users >
Feb 11 17:58:46 atl-sipgateway1 /usr/local/sbin/opensips[376]: New request - M=INVITE RURI=sip:[email protected]:5060;transport=udp F=sip:[email protected] T=sip:[email protected]:5060 IP=216.82.224.202 [email protected] Feb 11 17:58:46 atl-sipgateway1 /usr/local/sbin/opensips[376]: Recording Route info Feb 11 17:58:46 atl-sipgateway1 /usr/local/sbin/opensips[376]: Method is an INVITE, fetching next from dispatcher Feb 11 17:58:51 atl-sipgateway1 /usr/local/sbin/opensips[414]: Failure route, trying again Feb 11 17:58:51 atl-sipgateway1 /usr/local/sbin/opensips[414]: Got a 408 Timeout, flagging dest as invalid Feb 11 17:58:51 atl-sipgateway1 /usr/local/sbin/opensips[352]: Reply - S=100 D=Trying F=sip:[email protected] T=sip:[email protected]:5060 IP=XX.XX.XX.186 [email protected] Feb 11 17:58:51 atl-sipgateway1 /usr/local/sbin/opensips[355]: Reply - S=200 D=OK F=sip:[email protected] T=sip:[email protected]:5060 IP=XX.XX.XX.186 [email protected] Feb 11 17:58:51 atl-sipgateway1 /usr/local/sbin/opensips[351]: New request - M=ACK RURI=sip:[email protected] F=sip:[email protected] T=sip:[email protected]:5060 IP=216.82.224.202 [email protected] Feb 11 17:58:51 atl-sipgateway1 /usr/local/sbin/opensips[351]: Recording Route info Feb 11 17:58:51 atl-sipgateway1 /usr/local/sbin/opensips[351]: Loose route has returned true, attempting routing. Feb 11 17:58:51 atl-sipgateway1 /usr/local/sbin/opensips[351]: Setting up reply handler and relaying request Feb 11 17:58:56 atl-sipgateway1 /usr/local/sbin/opensips[376]: New request - M=BYE RURI=sip:[email protected]:5060;transport=udp F=sip:[email protected]:5060 T=sip:[email protected] IP=XX.XX.XX.186 [email protected] Feb 11 17:58:56 atl-sipgateway1 /usr/local/sbin/opensips[376]: Recording Route info Feb 11 17:58:56 atl-sipgateway1 /usr/local/sbin/opensips[376]: Loose route has returned true, attempting routing. Feb 11 17:58:56 atl-sipgateway1 /usr/local/sbin/opensips[376]: Setting up reply handler and relaying request Feb 11 17:58:56 atl-sipgateway1 /usr/local/sbin/opensips[348]: Reply - S=200 D=OK F=sip:[email protected]:5060 T=sip:[email protected] IP=216.82.224.202 [email protected]
opensips.cfg
Description: Binary data
Feb 11 17:58:32 atl-sipgateway1 /usr/local/sbin/opensips[347]: New request - M=INVITE RURI=sip:[email protected]:5060;transport=udp F=sip:[email protected] T=sip:[email protected]:5060 IP=216.82.224.202 [email protected] Feb 11 17:58:32 atl-sipgateway1 /usr/local/sbin/opensips[347]: Recording Route info Feb 11 17:58:32 atl-sipgateway1 /usr/local/sbin/opensips[347]: Method is an INVITE, fetching next from dispatcher Feb 11 17:58:32 atl-sipgateway1 /usr/local/sbin/opensips[350]: Reply - S=100 D=Trying F=sip:[email protected] T=sip:[email protected]:5060 IP=XX.XX.XX.186 [email protected] Feb 11 17:58:32 atl-sipgateway1 /usr/local/sbin/opensips[353]: Reply - S=200 D=OK F=sip:[email protected] T=sip:[email protected]:5060 IP=XX.XX.XX.186 [email protected] Feb 11 17:58:32 atl-sipgateway1 /usr/local/sbin/opensips[352]: New request - M=ACK RURI=sip:[email protected] F=sip:[email protected] T=sip:[email protected]:5060 IP=216.82.224.202 [email protected] Feb 11 17:58:32 atl-sipgateway1 /usr/local/sbin/opensips[352]: Recording Route info Feb 11 17:58:32 atl-sipgateway1 /usr/local/sbin/opensips[352]: Loose route has returned true, attempting routing. Feb 11 17:58:32 atl-sipgateway1 /usr/local/sbin/opensips[352]: Setting up reply handler and relaying request Feb 11 17:58:36 atl-sipgateway1 /usr/local/sbin/opensips[351]: New request - M=BYE RURI=sip:[email protected] F=sip:[email protected] T=sip:[email protected]:5060 IP=216.82.224.202 [email protected] Feb 11 17:58:36 atl-sipgateway1 /usr/local/sbin/opensips[351]: Recording Route info Feb 11 17:58:36 atl-sipgateway1 /usr/local/sbin/opensips[351]: Loose route has returned true, attempting routing. Feb 11 17:58:36 atl-sipgateway1 /usr/local/sbin/opensips[351]: Setting up reply handler and relaying request Feb 11 17:58:36 atl-sipgateway1 /usr/local/sbin/opensips[372]: Reply - S=200 D=OK F=sip:[email protected] T=sip:[email protected]:5060 IP=XX.XX.XX.186 [email protected]
_______________________________________________ Users mailing list [email protected] http://lists.opensips.org/cgi-bin/mailman/listinfo/users
