SCZ10.0p2 incorrectly processes two Diversion headers.

Hello fellows.

Have you ever seen such behavior on SBC? An INVITE with two Diversion headers arrive. First (topmost) Diversion contains number XXXXXX51637. Second (bottomost) Diversion contains number xxxxxx03758.

SBC applies a sip-manipulation with two header-rules: first header rule "stDiv" stores Diversion header. Second header rule "modDiv" modifies the previously stored number if a certain condition has been met. What I see in debug, is that SBC stores the bottomost Diversion header twice, and then performs the same modification twice (see the fragment below).

I made a simple test: at first i stored the Diversion header, then I removed DIversion header and then restored only $stDiv