- Joined
- May 11, 2008
- Messages
- 17
- Reaction score
- 1
If this sounds familiar and you've any guidance, please let me know.
Using paid version 15.5 on Debian with Vitelity SIP on dedicated Intel NUC, 2 users, Polycom 335, 20 gigs of free space.
A generally stable system for 15 months with occassiona dropped call .
1 - Dial and successfully connect call.
2 - Call drops after several minutes.
3 - Redial and connect to other party and continue speaking for 5 minutes.
4 - Then I hear my 3CX voice message...."You've reached...." because the call had somehow been routed to my 'general mailbox'.
5 - Redial and connect to other party, resume conversation.
6 - Several minutes later, C3X announces that I had reached the end of the allowable space for recording and asked if I wanted to save the recording, delete it, or start over.
7 - Waited until that ended, everyone laughed, and I apologized for my phone’s misbehavior. Then we went on to finish the call within 5 – 10 minutes.
Any clues for me on where to begin diagnosing this?
Using paid version 15.5 on Debian with Vitelity SIP on dedicated Intel NUC, 2 users, Polycom 335, 20 gigs of free space.
A generally stable system for 15 months with occassiona dropped call .
1 - Dial and successfully connect call.
2 - Call drops after several minutes.
3 - Redial and connect to other party and continue speaking for 5 minutes.
4 - Then I hear my 3CX voice message...."You've reached...." because the call had somehow been routed to my 'general mailbox'.
5 - Redial and connect to other party, resume conversation.
6 - Several minutes later, C3X announces that I had reached the end of the allowable space for recording and asked if I wanted to save the recording, delete it, or start over.
7 - Waited until that ended, everyone laughed, and I apologized for my phone’s misbehavior. Then we went on to finish the call within 5 – 10 minutes.
Any clues for me on where to begin diagnosing this?