[Spce-user] v2.8 - Session Timers

Wed Feb 1 02:46:07 EST 2017

I have a problem with session refresh with my VoIP Carrier: At 30 minutes my carrier needs to be the session refreshed, otherwise the carrier hangup the call. I have configured SST Params on Peering Server like this:

Sst_enable: yes
Sst_expires: 1800
Sst_min_timer: 90
sst_refresh_method: update

I have this problem only in outgoing calls.

Does someone know how to solve this problem? I have attached the SEMS log with level 3 debug where SPCE is is the UAC but it don't refesh the session at Session-Expires.
#012Session-Expires: 1800;refresher=uac#015

Thank you for your help!

Saludos, 
Robert Cuaresma
Dpto. Ingeniería de Clientes

c/Balmes, 8, plta.3 Dpcho. 6 D , 08291 Ripollet (Barcelona) 
Telf.:93.692.95.95  / Fax: 93.580.80.29
Email: rcuaresma at telcon.es
Web: www.telcon.es 

**AVIS**
Li informem que les seves dades personals que hi puguin constar en aquesta comunicació, estan incorporades en un fitxer propietat de TELCON, SA amb la finalitat de gestionar la relació negocial que ens vincula i informar-li dels nostres productes i serveis. Si desitja exercir els drets d’accés, rectificació, cancel·lació i oposició, es pot dirigir per escrit a: TELCON, SA, Carrer BALMES nº 8 Pis: 3 Pta.: 6, 08291, RIPOLLET, BARCELONA.
En el cas que no desitgin rebre més informació sobre els serveis que oferim pot enviar-nos un missatge a la següent adreça de correu electrònic: telcon at telcon.es  
Aquest missatges es dirigeix exclusivament al seu destinatari o pot contenir informació privilegiada o confidencial. Si vostè no és el destinatari indicat, resta notificat de que la utilització, divulgació i/o còpia sense autorització està prohibida en virtut de la legislació vigent.
Si ha rebut aquest missatge per error, preguem ens ho comuniqui immediatament per aquesta mateixa via i procedeixi a la seva destrucció.

-----Mensaje original-----
De: Robert Cuaresma 
Enviado el: miércoles, 25 de enero de 2017 8:19
Para: 'Jon Bonilla (Manwe)' <manwe at sipdoc.net>
CC: 'spce-user at lists.sipwise.com' <spce-user at lists.sipwise.com>
Asunto: RV: [Spce-user] v2.8 - Session Timers

Arrggg!! Sorry Jon, I had attached a Debug with incorrect data.... now, you have a complete debug call with an outgoing call session and a 200 OK with
#012Session-Expires: 1800;refresher=uac#015

Thanks!!

Saludos,
Robert Cuaresma

-----Mensaje original-----
De: Jon Bonilla (Manwe) [mailto:manwe at sipdoc.net] Enviado el: lunes, 23 de enero de 2017 11:43
Para: Robert Cuaresma <rcuaresma at telcon.es>
Asunto: Re: [Spce-user] v2.8 - Session Timers

El Mon, 23 Jan 2017 07:37:27 +0000
Robert Cuaresma <rcuaresma at telcon.es> escribió:

> Hi Jon,
> 
> I attached you the correct Sems Debug  that include the sip trace with 
> an outgoing call.
> 

Hi Robert

Again, in this capture I see "#012Session-Expires: 1800;refresher=uas#015" in te 200OK. It's te carrier the one who has to refresh the session.

You need an example with refresher=uac to check is sems does not refresh in outgoing calls.

If you do not receive an update or invite before the bye the carrier is doing wrong.

You could also try to disable session timers in your gateway configuration loose that functionality.

cheers,

Jon

> Saludos,
> Robert Cuaresma
> 
> -----Mensaje original-----
> De: Jon Bonilla (Manwe) [mailto:manwe at sipdoc.net] Enviado el: 
> miércoles, 18 de enero de 2017 10:00
> Para: Robert Cuaresma <rcuaresma at telcon.es>
> CC: spce-user at lists.sipwise.com
> Asunto: Re: [Spce-user] v2.8 - Session Timers
> 
> El Wed, 18 Jan 2017 08:15:12 +0000
> Robert Cuaresma <rcuaresma at telcon.es> escribió:
> 
> > Hello Jon, I have attached the log of sems at debug level and a 
> > screenshot of sngrep where you can see the times of the call.
> > 
> > Thanks for all.
> > 
> > Saludos,
> > Robert Cuaresma
> 
> 
> Hi Robert
> 
> When sending a capture please send the SIP headers, not a capture.
> 
> From the sems log of this particular call I can see this:
> 
> 
> Jan 18 08:09:09 softswitch sems[2317]: [#7f2d5fd8e700] [run, 
> udp_trsp.cpp:213]
> DEBUG: vv M [|] u recvd msg via UDP vv#012--++--#012SIP/2.0 200
> OK#015#012Record-Route:
> <sip:SIPWISE_PUBLIC_IP:5060;ngcplb=yes;r2=on;ftag=05EB3586-587F14920008B8C2-60394700;lr=on>#015#012Record-Route:
> <sip:127.0.0.1:5060;ngcplb=yes;r2=on;ftag=05EB3586-587F14920008B8C2-60394700;lr=on>#015#012Content-Type:
> application/sdp#015#012Allow: INVITE, ACK, CANCEL, BYE, OPTIONS, 
> NOTIFY,
> UPDATE#015#012Contact:
> <sip:192 at 192.168.2.18;alias=80.32.126.246~5060~1;transport=UDP;user=phone>#015#012Require:
> timer#015#012Supported: timer,from-change#015#012User-Agent: 
> OXO103/015.001
> GW_103/049.001#015#012Session-Expires:
> 1800;refresher=uas#015#012P-Asserted-Identity:
> <sip:192 at 192.168.2.18;user=phone>#015#012To:
> <sip:936407085 at SIPWISE_PUBLIC_IP>;tag=8c60ecbf6dad76a71fdab7b0196f7ba0#015#012From:
> <sip:972261252 at SIPWISE_PUBLIC_IP>;tag=05EB3586-587F14920008B8C2-60394700#015#012Call-ID:
> 336471704_25220249 at VOIP_CARRIER_IP_b2b-1#015#012CSeq: 10 INVITE#015#012Via:
> SIP/2.0/UDP
> 127.0.0.1:5080;branch=z9hG4bKG.Hmuavg;rport=5080#015#012Content-Length:
> 334#015#012P-NGCP-Src-Ip: 80.32.126.246#015#012P-NGCP-Src-Port:
> 5060#015#012P-NGCP-Src-Proto: udp#015#012P-NGCP-Src-Af:
> 4#015#012#015#012v=0#015#012o=OxO 1484723495 1484723495 IN IP4 
> 192.168.2.18#015#012s=Alcatel-Lucent OXO103/049.001#015#012c=IN IP4
> 80.32.126.246#015#012t=0 0#015#012m=audio 32000 RTP/AVP 8
> 100#015#012a=rtpmap:8 PCMA/8000#015#012a=rtpmap:100
> telephone-event/8000#015#012a=fmtp:100 0-15#015#012a=silenceSupp:off -
> - -
> -#015#012a=sendrecv#015#012a=ptime:20#015#012a=maxptime:90#015#012a=di
> rection:active#015#012a=oldmediaip:192.168.2.18#015#012--++--
> 
> 
> 
> In the 200 OK the refresher is set to "uas" which means that the one 
> receiving the call is responsible of updating it. This time sems is 
> not the one responsible as this is an outgoing call and the carrier should refresh.
> 
> On previous traces it was uac. We would need a sems debug and sip 
> trace where sems is responsible of updating the session.
> 
> 
> cheers,
> 
> Jon
> 
> 
> 
> 
> 
> 
> > 
> > 
> > -----Mensaje original-----
> > De: Jon Bonilla (Manwe) [mailto:manwe at sipdoc.net] Enviado el: 
> > martes, 17 de enero de 2017 21:04
> > Para: Robert Cuaresma <rcuaresma at telcon.es>
> > CC: spce-user at lists.sipwise.com
> > Asunto: Re: [Spce-user] v2.8 - Session Timers
> > 
> > El Tue, 17 Jan 2017 17:07:07 +0000
> > Robert Cuaresma <rcuaresma at telcon.es> escribió:
> > 
> > 
> > 
> > Hi Robert
> > 
> > That's not sems log at debug level. I can't promise anything will 
> > show but you need to enable it and set it lo 3.
> >   
-------------- next part --------------
An embedded and charset-unspecified text was scrubbed...
Name: Sems Log Debug Lebel.txt
URL: <http://lists.sipwise.com/mailman/private/spce-user_lists.sipwise.com/attachments/20170201/e25b5e61/attachment.txt>