[Spce-user] peer timeouts and

[Matthew Ogden]

Thanks Andrew

In the manual it says about using ngcpcfg apply: Be aware that this will
force SEMS to restart, which will drop running conference calls

Does this mean only conference calls (all other routed calls currently
going will NOT be dropped?)

Does this also mean you can do an upgrade then without dropping calls
(obviously this is not advisable, but more of an interest).

Regards


-----Original Message-----
From: Andrew Pogrebennyk [mailto:apogrebennyk at sipwise.com]
Sent: 30 April 2012 11:33 AM
To: Matthew Ogden
Cc: Andreas Granig; spce-user at lists.sipwise.com
Subject: Re: [Spce-user] peer timeouts and

Hi Matthew,

On 04/30/2012 09:02 AM, Matthew Ogden wrote:
> Is this now resolved?

We have pushed the updated sems version into 2.5 repository. Please run
apt-get update && apt-get upgrade.

Then you can configure SIP timers B and F:
cp /etc/ngcp-config/templates/etc/sems/sems.conf.tt2
/etc/ngcp-config/templates/etc/sems/sems.conf.customtt.tt2
Edit /etc/ngcp-config/templates/etc/sems/sems.conf.customtt.tt2

Add two lines:
sip_timer_b=3500
sip_timer_f=3500
and run ngcpcfg apply.
If the peer doesn't respond within 3.5 seconds with 100 Trying system will
move onto the next peer. Of course you may adjust these values as needed.

HTH.
Andrew