< Previous by Date | Date Index | Next by Date > |
< Previous in Thread | Thread Index | Next in Thread > |
I see nothing obvious in the dum code that would cause this.
Try a breakpoint on line 31 of InviteSessionCreator and then debugging – this is
the block of code where the SessionExpires header is set for a UAC invite.
getLastRequest()->header(h_SessionExpires).value() =
userProfile->getDefaultSessionTime(); Scott From:
resiprocate-users-bounces@xxxxxxxxxxxxxxx
[mailto:resiprocate-users-bounces@xxxxxxxxxxxxxxx] On Behalf Of Karlsson
On Tue, Dec 9, 2008 at 1:43 AM, Scott Godin <slgodin@xxxxxxxxxxxx>
wrote: Hmm strange…. If you only
use MasterProfile and do not pass a UserProfile to makeInviteSession then
everything should be fine – since it will use the MasterProfile as the
UserProfile. From: Karlsson [mailto:boost.regex@xxxxxxxxx]
thank you scott, I will try it, I do not using
user profile so far, just using the master profile only. On Mon, Dec 8, 2008 at 11:34 PM, Scott Godin <slgodin@xxxxxxxxxxxx>
wrote: Are you passing a user profile
to makeInviteSession? The session time will come from the user
profile. In general it's a good idea to create your user profiles using
the MasterProfile as a base profile. From: resiprocate-users-bounces@xxxxxxxxxxxxxxx [mailto:resiprocate-users-bounces@xxxxxxxxxxxxxxx]
On Behalf Of Karlsson Hi all, I'm using reSIProcate 1.4.1, I have wrote these code for the
session timer(RFC40280): |