Nextiva is a cloud based VoIP phone system, hosting lots of small and medium sized businesses nationwide. the provides
UNLIMITED business calling for only $19.95 a month!!
Click here for the detail about this promotion!!
Rear one to all,
I have the following problem.
I have several festgestetze Messages for a number such as INVITE and cancel. With which Message can one this kicken?
This problem arose at one time. For several months I now already develop at my VOIP Client. Have already thousands of INVITES dispatches which always probemlos with cancel or BYE to terminate left themselves and now eggs this as corpses in the system and prevent my Telefonie.
I can register myself still problem-free however as soon as I try to telephone get I 488 Temporarily a Unavailable back.
Also after I deregistriert myself correctly get I this error.
Can me possibly. someone explain as sowas happened?
Greeting
Even if with cancel o.a. which goes wrong, you would have to get messages in the CLI at least like “Scheduling destruction OF dialogue… in…. MSEC "
That is the clearing up function of the Asterisk. What do you see that still parts of the dialogue are attaching? You would have to apply a few Screenshots or Logs, because your problem does not seem to be a standard problem…
Thus we looked into the CONSOLE of the Asterisk and the whole open Invites and Cancels there found. In addition, we have yet not found out like one these to shoot could.
… and those do not disappear again automatically after few seconds (at the latest minutes)??
With me then (SET BOSE 99) at least messages appear la
Code:
Really destroying SIP dialogue “15dfb7d8780c0002744052773a331726@…” Method: OPTION
Really destroying SIP dialogue “3c26701b15cc-7k1sph41l2cf” Method: REGISTER
No they do not disappear unfortunately automatically.
Achso I by the way wrote a wrong error number. It is the 480 and with additive (call limit).
… and, you set limit in sip.conf? How many are hanging connections like that per Client?
Are some hanging connections. so 5 or 6.
Call limit was adjusted to 2. Stands now on 10. Funzt first times however those
still there hanging connections are.
There is to lock a possibility server-laterally and/or. to shoot?
Code:
rtptimeout=60 ; Terminate call if 60 seconds OF NO RTP activity
; when we're emergency on hold
rtpholdtimeout=300 ; Terminate call if 300 seconds OF NO RTP activity
; when we're on hold (must > rtptimeout)
… would have to help.