Kapanga - The Media over IP Softphone

I set up Kapanga with session timers and for the UAS to be the refresher.  The initial invite (from Kapanga) included:

Session-Expires: 180;refresher=uas

The UAS responded with 200 OK with:

Session-Expires: 180;refresher=uas


All is good until the first refresh (in this case it was an INVITE) is received from the UAS, which contains:

Session-Expires: 180;refresher=uac

Kapanga sent 200 OK with:

Session-Expires: 180;refresher=uas, which in essence is Kapanga stating it will be the refresher.

--------------

The session went basically like this:

UAC (kapanga) ----------> INVITE with UAS as refresher

UAS ----------------------->  200 OK, agreeing to be refresher

Now UAS is refresher so updates/invites will be sent as the UAS is now UAC and Kapanga is the UAS.

UAC -----------------------> INVITE (refresh) to kapanga, with UAC as refresher.  In this case the UAS and UAC (kapanga) trade places, being that the refresh came from the UAS, it now is considered the UAC.  Thus kapanga should agree with 200 OK with Session-Expires: 180; refresher=uac.

See RFC-4028 section 7. 


Hopefully I was clear enough.