From: Sylvain M. <24...@gm...> - 2011-10-21 21:19:32
|
Hi, > (2) Have sipauthserve return Kc and the sequence number in an optional header in the final 200 OK. Sipauthserve would still store Kc in the sip_buddies table for future reference via a sequence number, but OpenBTS would not need to access that table directly since it received a copy of Kc via SIP. Since OpenBTS does *not* directly access sip_buddies in the current design, this approach would not introduce any new interfaces or interaction paths among the components, just a few more lines of code somewhere in SIPEngine to grab Kc and put it in the transaction table. This approach does assume a reasonable degree of security in the SIP path, but we assume that already. And so, do you issue a REGISTER from OpenBTS at each time you get a new channel ? (So, PAGING RESPONSE, LOC UPD and CM SERV REQ are the three possible messages that have a key_seq in them). Cheers, Sylvain Munaut |