New Rhino R4FXO-EC install
Submitted by dhallman on Sat, 02/09/2008 - 11:30am.
Hi All.
Thank you to everyone that has posted recently to this forum.
By reading your posts I have my new Rhino R4FXO-EC working in trixbox 2.4.
One small newbie issue.
In incoming routes if I set the match to any/any I can ring the set extension.
I have the line in the first port (I think) but setting the Zap line to channel 1 (just entering "1" in the space) I get "number not in service". I have tried 01 as well. I have also set up all 4 ports in case I had the line in the wrong port.
So I am wondering what the correct entry is to designate channel 1.
I do want to put additional lines in the route differently.
Thanks for any help.
Dwayne
mine works like this:
Sat, 02/09/2008 - 4:23pm
No go....
Sat, 02/09/2008 - 7:51pm
Thank you for the lead.
I checked the trunk was set to 1. (I had g0 before)
The changed the Zap channel to 1 in inboud routes set to ring at 101
I still get "number not in service" when I call in. FOP is showing Zap 1 active when the call is mode. But not routed.
Here is a debug:
-- Executing [s@from-pstn:1] NoOp("Zap/1-1", "No DID or CID Match") in new stack
-- Executing [s@from-pstn:2] Answer("Zap/1-1", "") in new stack
-- Executing [s@from-pstn:3] Wait("Zap/1-1", "2") in new stack
-- Executing [s@from-pstn:4] Playback("Zap/1-1", "ss-noservice") in new stack
--
I tried 1-1 (long shot). No difference.
I tried setting the incoming to DID match. Same result (no I did not have a CID this time!)
What am I missing?
Thanks for the reply
to route based on zap
Sat, 02/09/2008 - 8:24pm
to route based on zap channel your context must be from-zaptel
config
Sat, 02/09/2008 - 8:41pm
I do have from-zaptel in my zapata.conf. Is there another place this is required?
zapata.conf--------------
;
; Zapata telephony interface
;
; Configuration file
[trunkgroups]
[channels]
language=en
context=from-zaptel
signalling=fxs_ks
rxwink=300 ; Atlas seems to use long (250ms) winks
;
; Whether or not to do distinctive ring detection on FXO lines
;
;usedistinctiveringdetection=yes
usecallerid=yes
hidecallerid=no
callwaiting=yes
usecallingpres=yes
callwaitingcallerid=yes
threewaycalling=yes
transfer=yes
cancallforward=yes
callreturn=yes
echocancel=yes
echocancelwhenbridged=no
echotraining=800
rxgain=0.0
txgain=0.0
group=0
callgroup=1
pickupgroup=1
immediate=no
;faxdetect=both
faxdetect=incoming
;faxdetect=outgoing
;faxdetect=no
;Include genzaptelconf configs
#include zapata-auto.conf
group=1
;Include AMP configs
#include zapata_additional.conf
look in zapata-auto or
Sat, 02/09/2008 - 8:44pm
look in zapata-auto or zapata-channels
fixed...
Sat, 02/09/2008 - 9:30pm
Thank you James, that got it.
I have also noticed the channel gets stuck open from time to time. I can kill it in FOP, but until I notice the line is open normally recording a long voicemail.
Is there something I can adjust to recognize the call termination?
Thanks again,
Dwayne
hang up....
Sun, 02/10/2008 - 7:03am
I found this on your troubleshooting blog, I don't know that it applies. But I am trying it:
"If your telco does not provide far end disconnect supervision or if they just dont do it well you may need to “fake” supervision in order for your lines to disconnect properly. You may fake supervision by adding a few lines to your zapata.conf .
Add the following to your /etc/asterisk/zapata.conf
callprogress=yes
busydetect=yes"
Dwayne
Look om the blog there are
Sun, 02/10/2008 - 12:58pm
Look om the blog there are firmware upgrade instructions try that first
Stuck pots lines
Thu, 03/06/2008 - 6:14pm
Just a quick note to give others a hint of what I have found out using Bell Canada lines with trixbox 2.4
In my area Bell sells 2 types of lines. They refer to them as standard and advanced. The standard line has no features by default but you can purchase individual features as you go. The advanced line has all normal calling features and you can not have any dissabled.
In my area (God's country) both lines cost the same per month. Most people do not have that issue. I am using 2 standard lines as I do not want call waiting and there is no way to dissable the feature (other then per call) on the line.
I have found the basic pots line does not hang up a call that is connected to voicemail or IVR after the caller exits even with Rhino's new firmware (I expect this is a line issue not a Rhino issue as my tests with Bell's advanced lines shows no issue. This all may chage with trixbox 2.6 and zaptel 1.4.9.1??). But there is a work around that keeps things going:
1. In the IVR settings add the 't' and 'i' functions (invalid responce and no responce) to some result. I set them to end the call. You may require another action.
2. In vm_general.inc add the line maxmessage=180. That forces to system to hang up on a voicemail over 3 mins long.
In both cases trixbox is forcing the call to end rather then the proper situation where the line signals the call is over to the PBX. But since adding these settings my system is reliably available to answer calls.
I hope this saves some trouble for other Bell Canada users.
Dwayne
Member Since:
2007-01-03