Hi Lonnie,
thanks for your immediate answer.
We have already integrated qualify, but it does not solve the problem.
I'll try with different timeouts offered by the DIAL-command
If this won't work I'll have to write a deamon, which checks the opened
channels, and terminates them from outside when they remain open too long.
Of course I appreciate each advice the community can give me to solve the
problem easier.
Best regards
Stefan Ulm
Technical Department | Research & Development
stefan....@divus.eu
DIVUS Headquarters Pillhof 51 . I-39057 Eppan (Südtirol) . Tel. +39 0471 633
662 . Fax. +39 0471 631 829
www.divus.eu . Privacy: http://www.divus.eu/media/DivusPrivacy.pdf
-----Ursprüngliche Nachricht-----
Von: Lonnie Abelbeck [mailto:li...@lonnie.abelbeck.com]
Gesendet: Donnerstag, 1. September 2016 16:00
An: AstLinux Users Mailing List <astlinux-users@lists.sourceforge.net>
Betreff: Re: [Astlinux-users] clean up SIP channels
Stefan,
Answering your question, AstLinux does not have any tools to externally
clean-up "ghost" SIP sessions.
Interesting problem, of course your 1 channel limit is at the heart of the
problem.
The SIP protocol will eventually clean-up these ghost sessions with the missing
BYE, possibly a SIP guru here would know what timer and timeout would effect
how long the session lives without a properly terminated BYE.
There may be some SIP timer setting in Asterisk that would shorten the recovery
time from a brokern SIP session, possibly if you added qualify=yes to your
client peers ? Not sure if that would work.
I assume you are using SIP over UDP, possibly if you used SIP over TCP the
network stack would terminate the session sooner, again just a guess.
Lonnie
On Sep 1, 2016, at 8:04 AM, Stefan Ulm <s....@divus.biz> wrote:
> Hi All,
>
> sometimes it happens, that SIP channels remain open, also if the call was
> already closed.
> There is one situation it can be reproduced quite well: power down the client
> during it is in communication (the sip stack is immediately powered off
> together with the client, normally by doing hard reset and it can't send a
> BYE to close the call correctly). The result is, that SIP channels remain
> open and since we use a limitation of one channel per client, this becomes
> problematic, since if the problem occurs, the corresponding client can't
> receive calls anymore, because of the reached limitation of 1 opened SIP
> channel.
> Sometimes this problem occurs also without powering down any client, but
> actually we don't know the cause for it.
> Our idea is to implement a cleanup of the SIP channels, if the problem occurs.
> Actually I make research to find a way to recognize such "ghost" SIP channels
> and to close them.
> Does astlinux offer any possibility to reach this target?
> My very last way will be to create a deamon which scans the opened SIP
> channels and with a timeout he can now if they are opened too long and force
> the closing; of course if there is a simplier solution will be welcome.
>
> Best regards
>
> Stefan Ulm
> Technical Department | Research & Development stefan....@divus.eu
>
>
>
>
> <image001.png>
>
> DIVUS Headquarters Pillhof 51 . I-39057 Eppan (Südtirol) . Tel. +39
> 0471 633 662 . Fax. +39 0471 631 829 www.divus.eu . Privacy:
> http://www.divus.eu/media/DivusPrivacy.pdf
------------------------------------------------------------------------------
_______________________________________________
Astlinux-users mailing list
Astlinux-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/astlinux-users
Donations to support AstLinux are graciously accepted via PayPal to
pay...@krisk.org.
------------------------------------------------------------------------------
_______________________________________________
Astlinux-users mailing list
Astlinux-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/astlinux-users
Donations to support AstLinux are graciously accepted via PayPal to
pay...@krisk.org.
