[Spce-user] How to handle methode UPDATE

[Klaus Peter v. Friedeburg]

Hi,

> -----Ursprüngliche Nachricht-----
> Von: spce-user-bounces at lists.sipwise.com [mailto:spce-user-bounces at lists.sipwise.com] Im Auftrag von
> Andreas Granig
> Gesendet: Montag, 31. Oktober 2011 22:48
> An: spce-user at lists.sipwise.com
> Betreff: Re: [Spce-user] How to handle methode UPDATE
> 
> Hi,
> 
> On 10/31/2011 09:01 PM, Klaus Peter v. Friedeburg wrote:
> > When I configure the session-timer in sems to 600 the PSTN-Gateway give us a reply on our INVITE-
> Message:
> > 	422 Session Intervall too small, with Min-SE 1800
> > Then our ngcp-sems send a new INVITE with Session-Expires: 1800
> > But after exactly 600 second sems terminate the call with BYE
> > No reINVITE is sending from sems
> > The mistake is that sems don't switch the internal Session-timer to the handshaked Session-Expire: 1800
> 
> Anything on the second call leg towards the client?


Yes the next packet from ce to client is the 200 ok with Session-Expires 600, so that different session-timers are active.  600 from Client to ce and 1800 from ce to pstn-gateway

> 
> > When I configure the session time in sems to 1800 or greater we get from the PST-Gateway after 1800 second
> a reINVITE, with:
> > 	Session-Expires: 1800;refresher=uac
> > The answer from sems is:
> > 	200 OK with Session-Expires: 1800;refresher=uas
> > This is not correct!! Sems must answer with the whole Text from the reINVITE in this example with
> > 	200 OK Session-Expires: 1800;refresher=uac
> 
> I think I've seen this behavior before and discussed it with the Sems
> devs, but we didn't follow up on that because it was related to another
> issue.
> @Stefan, what do you think of that?
> 
> Andreas

Klaus Peter