[Spce-user] v2.8 - Session Timers

[Jon Bonilla (Manwe)]

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=direction: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 --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 833 bytes
Desc: Firma digital OpenPGP
URL: <http://lists.sipwise.com/pipermail/spce-user_lists.sipwise.com/attachments/20170118/655d2e50/attachment-0001.sig>