Multiple contact information in 302 Moved Temporarily

Does SBC can manage 302 Moved Temporarily message received from Application Server AS?

I expect that AS will provide three contact headers or three valuses in one header. SBC should take the first value and should try to to route the call according to the first contact infornmation. In case of failure: when a call is rejected with some specified release cause, the second contact value should be taken into account.  If the second choice is rejected with some specified release cause, the third contact value should be taken into account.

Valuses returned in contact are different for different calls: i.e. it cannot be predefined SAG, because I cannot predict which elements shoulb be part of SAG and in which order.