bubblestar

I have been using the 1st option for several months by settings 60/120 for rtptimeout and rtpholdtimeout in sip.conf respectively.  So far no problem.

As I am using Telephony card in the server, I think the chan_dahdi.conf has its own mechanism for similar effect with the optional use of the busydetect and busycount.

bubblestar

This is my chan_dahdi.conf settings.  The busycount varies from case to case and also depending on your telecom operator.  Default is 4 but shorter is not recommended by DAHDI manufacturer.  Despite of their advise, setting to 2 works for me.

1. [trunkgroups]
   
2. 
   
3. [channels]
   
4. language=en
   
5. ;switchtype=national
   
6. ;rxwink=300                                ; Atlas seems to use long (250ms) winks
   
7. usecallerid=yes
   
8. hidecallerid=no
   
9. hidecalleridname=no
   
10. callwaiting=yes
    
11. usecallingpres=yes
    
12. callwaitingcallerid=yes
    
13. threewaycalling=yes
    
14. transfer=yes
    
15. canpark=yes
    
16. cancallforward=yes
    
17. callreturn=yes
    
18. echocancel=yes
    
19. echocancelwhenbridged=yes
    
20. echotraining=800
    
21. relaxdtmf=yes
    
22. rxgain=0.0
    
23. txgain=0.0
    
24. ;callgroup=1
    
25. ;pickupgroup=1
    
26. immediate=no
    
27. busydetect=yes                        ; Uncomment these lines if you have problems with the disconection of your analog lines
    
28. busycount=2
    
29. faxdetect=incoming
    
30. 
    
31. #include /etc/asterisk/dahdi-channels.conf

複製代碼