#170 Issue in handling response to request sent after redirection
Hi,
When the diameter client gets a redirect response (E
bit set , result code DIAMETER_REDIRECT_INDICATION, and
Redirect-Host AVP's) it correctly creates a new
request and sends it to the host mentioned in the
Redirect-Host AVP's. However the diameter response
received to this
redirected messages is dropped by the diameter client.
Has anyone faced a similar problem ? OR Has anyone
been successful in executing the above scenario ?
After digging into the code I "suspect" that this
could be because the pending request information is
getting removed on getting the first response from the
redirect server. Hence when the second response comes
there is no matching pending request to match using
the hop-by-hop
identifier . The open diameter stack seems to keep the
hop-by-hop identifier same for the first request as
well as the second. The RFC is not clear whether is
should either be same or different. Does anyone have
any inputs on the same.
