Koozali.org: home of the SME Server
Obsolete Releases => SME VoIP (Asterisk, SAIL etc) => Topic started by: SARK devs on April 24, 2009, 02:07:43 PM
-
We've noticed a lot of you downloading 2.3. We aren't seeing a lot of error reports so either you aren't actually installing it or it is running OK ( :) )
Please let us know if you have any problems because we want to move towards declaring it production ready.
Best
S
-
Hi S,
I'm using it with a TDM400 on a test server, and so far so good.
My production server still runs 2.2.1 and I'm almost ready to go to the latest.
Thanks,
-
I just updated my home installation yesterday to 2.3
Did some recordings etc.
I had a problem with the previous install where I couldn't record messages etc ... all works now though ... I'm sure is was a bad or mixed install I had.
I uninstalled all asterisk/sail etc just to make sure and installed 2.3 from scratch.
2.3 picked up all my previous data base settings no prob.
Haven't found anything amiss as yet.
Will be setting up queues etc in the next few days ... and will also install my openvox card.
Regards,
Tib
-
Hello selintra!
First of all I should say that the speed you develop sail is very impressive! Keep on the good work!
I also moved to sail 2.3.1 and it works well. The only thing .... I've got a problem with call pickup.
As could be seen, there is a bug in 1.4.23:
http://bugs.digium.com/view.php?id=14206
So may be it's better to advice to use 1.4.24 release of asterisk. It could be also downloaded from Atrpms. Just my thoughts..... Certainly you guys knew better what package more stable
Sincerely,
Kirill
-
Hi Iam,
Please go ahead and test with 1.4.24. 1.4.23 has several reported/known bugs, some of which are quite critical.
Ley us know hwo you get on with 1.4.24 and thanks for reporting
Best
S
-
Call pick up works fine with 1.4.24
I've got another question with sail-2.3.1-4
I have tdm400 card with 1 fxs and 1 fxo ports
The problem is that it detects both ports, but only trunk line appears in web interface.
And nothing appears in Extension menu table
Sincerely
#############################################################
PCI Telephony Cards found on this system...
PCI Card: pci:0000:06:00.0 wctdm+ e159:0001 Wildcard TDM400P REV E/F
#############################################################
# Autogenerated by /usr/sbin/dahdi_genconf on Tue Apr 28 00:46:03 2009 -- do not hand edit
# Dahdi Configuration File
#
# This file is parsed by the Dahdi Configurator, dahdi_cfg
#
# Span 1: WCTDM/4 "Wildcard TDM400P REV E/F Board 5" (MASTER)
fxoks=1
echocanceller=mg2,1
fxsks=2
echocanceller=mg2,2
# channel 3, WCTDM/4/2, no module.
# channel 4, WCTDM/4/3, no module.
# Global data
loadzone = ru
defaultzone = ru
################################################################
; Autogenerated by /usr/sbin/dahdi_genconf on Tue Apr 28 00:46:03 2009 -- do not hand edit
; Dahdi Channels Configurations (chan_dahdi.conf)
;
; This is not intended to be a complete chan_dahdi.conf. Rather, it is intended
; to be #include-d by /etc/asterisk/chan_dahdi.conf that will include the global settings
;
; Span 1: WCTDM/4 "Wildcard TDM400P REV E/F Board 5" (MASTER)
;;; line="1 WCTDM/4/0 FXOKS (EC: MG2)"
signalling=fxo_ks
callerid="Channel 1" <4001>
mailbox=4001
group=1
context=internal
channel => 1
callerid=
mailbox=
group=
context=default
;;; line="2 WCTDM/4/1 FXSKS (EC: MG2)"
signalling=fxs_ks
callerid=asreceived
group=2
context=mainmenu
channel => 2
callerid=
group=
context=default
###############################################################
-
That's odd because it has created the extension in dahdi (4001),
Did you run genconf from the PCI Cards menu item in SAIL or did you run it separately?
Best
S
-
Call pick up works fine with 1.4.24
I've got another question with sail-2.3.1-4
I have tdm400 card with 1 fxs and 1 fxo ports
The problem is that it detects both ports, but only trunk line appears in web interface.
And nothing appears in Extension menu table
Sincerely
File /etc/asterisk/dhadi-channels.conf wasn't automaticaly created. Since I created it manually, DAHDI Ext(FXS)1 appears in Ext table
-
That's odd because it has created the extension in dahdi (4001),
Did you run genconf from the PCI Cards menu item in SAIL or did you run it separately?
Best
S
As far as I remember, I worked from web interface, but may be yesterday night, during my fighting with 1.4.23, I've run something manually
-
Hi again!
I bag your pardon in advance, but could you explain what's the difference between dahdi and dhadi?
Isn't it a typo?
Sincerely
Sorry again if its stupid question :)
-
just a typo
no difference :)
I'will run some tests here against 400 and 410 cards to see if we can replicate what you are seeing
Best
S
-
Hi S
sail-2.3.1-4
asterisk-1.4.24.1-75.el4
We had a problem with a DiD from WDP, which we managed to get sorted. But lost it again when we loaded 2.3.1-4. The settings are as they were when working in the Trunks screen. The Headers Sip.conf general section lost the useragent=PAP2T. Reinserting that entry has not so far worked.
Sip debug shows the call trying to come in but is never answered. From a VOIP or PSTN line goes to engaged signal after some time, from a mobile just drops off (could be a time out).
Internet --> WDP2 (trunk definition) --> 61740840650 (DiD group)
Is there something obviously wrong and we are just not seeing it?
From the extensions.conf file
[mainmenu]
exten => 61740840650,1,agi(selintra,Inbound,${EXTEN})
exten => DAHDI1-1,1,agi(selintra,Inbound,${EXTEN})
exten => DAHDI2-1,1,agi(selintra,Inbound,${EXTEN})
exten => WDP2,1,agi(selintra,Inbound,${EXTEN})
exten => atp,1,agi(selintra,Inbound,${EXTEN})
exten => wdp_out,1,agi(selintra,Inbound,${EXTEN})
-
Hi compsos,
I have noticed that if you don't do a commit to ripple the setting through after an update the settings for where itcoming calls are directed tend to get lost.
Check your settings for the trunk where open and closed inbound routes are going.
If that doesn't work start a new thread and post a log of whats happening when an incoming call lands so we can try and see where it is going.
That way we are not hijacking this thread....
-
Hi Gippsweb
Not meaning to modify the thread. Dahdi is closely related to the trunks.
Have done lots of commits and stop starts. The setting was in the conf but not after the upgrade.