[Spce-user] v2.8 - Session Timers

[Robert Cuaresma]

Hi Jon,


This is the SEMS log. The call was hangup at 13:38:23 (you can see in capture of sngrep), but the sems log didn't displayed any message at this time.


Jan 16 13:38:12 softswitch sems[2317]: [#7f2d5fe8f700] [handleSipMsg, AmSipDispatcher.cpp:51] INFO: unhandled SIP reply: BYE [code:100;phrase:[Trying];i:f4205573f8ebc4c6b89f5b0a8d

cce3ed at 192.168.0.246;cseq:10;cseq meth:BYE;l-tag:3B9A0E31-587CBE730002DD8C-5FE8F700;r-tag:8ccf0e2c35f04a967692f46e342d9b92;hdr:[Server: Sipwise NGCP Proxy 2.X#015#012];]


Jan 16 13:38:13 softswitch sems[2317]: [#7f2d5fb8c700] [handleSipMsg, AmSipDispatcher.cpp:51] INFO: unhandled SIP reply: BYE [code:100;phrase:[Trying];i:f4205573f8ebc4c6b89f5b0a8d

cce3ed at 192.168.0.246;cseq:10;cseq meth:BYE;l-tag:3B9A0E31-587CBE730002DD8C-5FE8F700;r-tag:8ccf0e2c35f04a967692f46e342d9b92;hdr:[Server: Sipwise NGCP Proxy 2.X#015#012];]


Jan 16 13:38:17 softswitch sems[2317]: [#7f2d5fd8e700] [handleSipMsg, AmSipDispatcher.cpp:51] INFO: unhandled SIP reply: BYE [code:100;phrase:[Trying];i:f4205573f8ebc4c6b89f5b0a8d

cce3ed at 192.168.0.246;cseq:10;cseq meth:BYE;l-tag:3B9A0E31-587CBE730002DD8C-5FE8F700;r-tag:8ccf0e2c35f04a967692f46e342d9b92;hdr:[Server: Sipwise NGCP Proxy 2.X#015#012];]


Jan 16 13:38:18 softswitch sems[2317]: [#7f2d5ff90700] [handleSipMsg, AmSipDispatcher.cpp:54] WARNING: unhandled SIP reply: BYE [code:408;phrase:[Timeout];i:f4205573f8ebc4c6b89f5b

0a8dcce3ed at 192.168.0.246;cseq:10;cseq meth:BYE;l-tag:3B9A0E31-587CBE730002DD8C-5FE8F700;r-tag:8ccf0e2c35f04a967692f46e342d9b92;]


Jan 16 13:43:37 softswitch sems[2317]: [#7f2d5fd8e700] [handleSipMsg, AmSipDispatcher.cpp:51] INFO: unhandled SIP reply: BYE [code:100;phrase:[Trying];i:b3a53d258dbcc29b6800609d41

d399ba at 192.168.0.246;cseq:10;cseq meth:BYE;l-tag:26CF0477-587CBE4C00014E26-5FB8C700;r-tag:a111bb6e630e2bdfec726f5aa088bf91;hdr:[Server: Sipwise NGCP Proxy 2.X#015#012];]


Jan 16 13:43:41 softswitch sems[2317]: [#7f2d5fc8d700] [handleSipMsg, AmSipDispatcher.cpp:51] INFO: unhandled SIP reply: BYE [code:100;phrase:[Trying];i:b3a53d258dbcc29b6800609d41

d399ba at 192.168.0.246;cseq:10;cseq meth:BYE;l-tag:26CF0477-587CBE4C00014E26-5FB8C700;r-tag:a111bb6e630e2bdfec726f5aa088bf91;hdr:[Server: Sipwise NGCP Proxy 2.X#015#012];]


Jan 16 13:43:42 softswitch sems[2317]: [#7f2d5ff90700] [handleSipMsg, AmSipDispatcher.cpp:54] WARNING: unhandled SIP reply: BYE [code:408;phrase:[Timeout];i:b3a53d258dbcc29b680060

9d41d399ba at 192.168.0.246;cseq:10;cseq meth:BYE;l-tag:26CF0477-587CBE4C00014E26-5FB8C700;r-tag:a111bb6e630e2bdfec726f5aa088bf91;]



Thanks again for your time.


Saludos,
Robert Cuaresma

________________________________
De: Jon Bonilla (Manwe) <manwe at sipdoc.net>
Enviado: lunes, 16 de enero de 2017 19:15
Para: Robert Cuaresma
Cc: spce-user at lists.sipwise.com
Asunto: Re: [Spce-user] v2.8 - Session Timers

El Mon, 16 Jan 2017 12:57:49 +0000
Robert Cuaresma <rcuaresma at telcon.es> escribió:

> Hi Jon!
>
> Thanks you for your help. I attach the trace that I have captured and a
> snapshot of sngrep.

Hi Robert

Yes, your spce sends invite to your carrier and the carrier sends a sst line in
the 200ok

        Session-Expires: 1800;refresher=uac


You spce should send a REINVITE or an UPDATE (UPDATE according to your config)
between 900 and 1800 seconds later. But it does not. You should check sems log
and check if there's anything related there.

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.sipwise.com/mailman/private/spce-user_lists.sipwise.com/attachments/20170116/0719c6d8/attachment.html>