21 Jun
2005
21 Jun
'05
12:59 a.m.
Hi All.
I just need a sanity check regarding avp_pushto() for serial forking.
Someone please correct me if I'm wrong here.
When processing an INVITE message which results in a 486 Busy status my
failure_route[] gets invoked.
In the failure route I use avp_pushto() to load the next leg of the call in
to the $ruri and then call append_branch() and lookup(location) prior to
t_relay()ing the message.
Using ngrep I do see the R-URI being changed to the value used in the
avp_pushto() call, but the IP address that the INVITE is then sent to is the
same as the IP address of the SIP router, which I cannot understand because
I do call lookup("location") before t_relay()
In otherwords, if my sip router,
sip.mycompany.com<http://sip.mycompany.com>has an IP of
71.72.73.74 <http://71.72.73.74> and I use avp_pushto() to set the R-URI to
1001_at_sip.mycompany.com, lookup(location) does return TRUE, but ngrep
still shows the INVITE leaving the SIP router and going to
71.72.73.74<http://71.72.73.74>(ie, itself) rather than the IP address
in usrloc.
Is there anything obvious that I'm not doing that would cause
lookup(location) to return TRUE, but not change the R-URI accordingly?
Regards,
Paul