when doing more testing, i noticed that when sems sbc is sending session timer update request, it does not include refresher in Session-Expires header. example from rfc:
UPDATE sips:[email protected] SIP/2.0 ... Session-Expires: 4000;refresher=uac the text goes like this: If the session refresh request is not the initial one, it is RECOMMENDED that the refresher parameter be set to 'uac' if the element sending the request is currently performing refreshes, and to 'uas' if its peer is performing the refreshes. This way, the role of refresher does not change on each refresh. in this particular test, sems used refresher=uas in its 200 ok response to the initial invite, i.e., sems had decided to be the refresher. so when sems sends update, it is recommended that also there sems writes ;refresher=uas. any pointers on how to fix this? i assume that somewhere sbc keeps track which role it has and it should be pretty easy to add the param based on than when it sends the update. this came up, because it looks like a commercial sip phone gets confused if refresher param is missing. -- juha _______________________________________________ Semsdev mailing list [email protected] http://lists.iptel.org/mailman/listinfo/semsdev
