Hi, as I said in other mail, I've tested auth_b2b module and checked that SEMS becomes a perfect transparent B2BUA:
If SEMS receives an in-dialog request with custom headers it respects them when creating the same in-dialog request in leg B. It just changes From tag, To tag and Call-ID (that is of course required in a B2BUA). I've tested it sending in-dialog OPTIONS, INFO, re-INVITE, BYE, REFER... it seems to work perfectly, but I would like to know if there could be any issue that I can't imagine now. For example: my aim is SEMS being a transparent B2BUA and using Session Timers in both legs. So if caller or callee starts by itself a Session Timer (by sending UPDATE/re-INVITE) how could SEMS handle it instead of "forwarding" it to the other leg as any other in-dialog request? Thanks a lot. -- Iñaki Baz Castillo _______________________________________________ Sems mailing list [email protected] http://lists.iptel.org/mailman/listinfo/sems
