[Seagull-users] Handling new Session-Id in Seagull

[Jignesh P. <jp...@ul...>]

Hi,

I would like to implement following scenario. 

>From Seagull documentation it sounds as though(although I could be
wrong) Seagull MUST know

new call's Session-Id....... Which in my case not possible.

 

 

SUT                        Seagull

 

<-            CER

CEA        ->

                <-            UDR

(Session-Id A)

UDA       ->

UDR       ->            

(Session-Id B)    

 

 

How can I handle Session-Id B, Seagull does not know anything about
Session-Id B? What method should I implement to so Seagull responds with
UDA?

 

Thanks,

Jignesh.