Somewhere in 3261 are rules for resolving addresses, including the processing of received 3xx responses. When an address is translated (typically by a proxy), there may be a number of candidates to be tried. These can be tried in any order, but there is a requirement that any given alternative be tried only once. If one of the tries results in a 3xx response, the contacts in that response may be considered as additional alternatives to try. But there remains the requirement not to try an alternative more than once.
I don't recall if it says so, but a UAC processing 3xx responses ought to follow the same algorithm.
If you follow this algorithm, then you won't have a problem with looping in the case you cite.
Paul
Ashir Ahmed wrote:
Hi,
Would be glad if someone can help me understand how to get rid of the following loop.
A Redirect server at example1.com domain has Bob's redirection information as follows: sip:[EMAIL PROTECTED]>sip:[EMAIL PROTECTED]
Redirect server at example2.com domain is configured as: sip:[EMAIL PROTECTED]>sip:[EMAIL PROTECTED]
In this scenario, an INVITE to sip:[EMAIL PROTECTED] will be redirected to example2.com domain. The redirect server at example2.com domain will transfer the call to example1.com. I see an endless loop will occur.
If the redirect servers are somehow misconfigured as above, how the loop can be detected or ended?
Thanks. Ashir
_______________________________________________ Sip-implementors mailing list [EMAIL PROTECTED] http://lists.cs.columbia.edu/mailman/listinfo/sip-implementors
_______________________________________________ Sip-implementors mailing list [EMAIL PROTECTED] http://lists.cs.columbia.edu/mailman/listinfo/sip-implementors
