[Spce-user] How to handle methode UPDATE

[Klaus Peter v. Friedeburg]

Dear Jon,

ok I have tested some different szenarios. I think the problem is the session-time-implementation in sems:
1. 
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

2.
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


Is there any way to change this behaviour?

Regards 
          Klaus Peter v. Friedeburg

-----Ursprüngliche Nachricht-----
Von: spce-user-bounces at lists.sipwise.com [mailto:spce-user-bounces at lists.sipwise.com] Im Auftrag von Jon Bonilla
Gesendet: Freitag, 28. Oktober 2011 00:50
An: spce-user at lists.sipwise.com
Betreff: Re: [Spce-user] How to handle methode UPDATE

El Fri, 28 Oct 2011 00:24:22 +0200
"Klaus Peter v. Friedeburg" <friedeburg at aco.de> escribió:

> Hello,
> 
> how is a way in sipwise CE to handle methode UPDATE? Do you have any script
> snippet for kamailio-proxy? Now the situation is that CE don't answer on an
> UPDATE Message so that the PBX-Gateway terminate the call with BYE
> 


Could you plase paste a ngrep capture?

The session timer negotiation is handled by sems and it sends or receives the
UPDATE requests to/from the UAs.

Please also make sure that you're running the latest version of the 2.2
templates by running "apt-get update && apt-get upgrade && ngcpcfg apply"