I'm kind of supprised that I'm the only one facing this problem ... Well, I figured out 2 possibilities to (hopefully) solve it: * merging the prepost branch into trunk * change a csv file (input for call) out of the registration scenario using the exec command
What were again the reasons that the prepost branch has never been merged into trunk? regards, Enrico Enrico Hartung wrote: > Hi, > > I wonder whether anybody has already faced the problem of a needed Route > header in the INVITE message like IMS demands it? > This means that the Service-Route header returned in the registration > process is supposed to be used as part of the Route header for all > following call initiations. Has anybody found a way to do this with SIPp? > > Thanks, > Enrico > > > ------------------------------------------------------------------------- > Take Surveys. Earn Cash. Influence the Future of IT > Join SourceForge.net's Techsay panel and you'll get the chance to share your > opinions on IT & business topics through brief surveys - and earn cash > http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV > _______________________________________________ > Sipp-users mailing list > [email protected] > https://lists.sourceforge.net/lists/listinfo/sipp-users > > ------------------------------------------------------------------------- Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT & business topics through brief surveys - and earn cash http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV _______________________________________________ Sipp-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/sipp-users
