|
List Info
Thread: RE: Zaptel
|
|
| RE: Zaptel |
 
United States |
2007-05-31 10:18:44 |
|
Hi Simpson,
I’ve tried it both ways, with
callerid = asreceived and without, both to no avail.
I started asterisk as you suggested below
and called into the pbx, but did not see any caller id information in the cli.
Should I be?
Also regarding my last message on how I
fixed it the lines, I remembered one additional item that was causing problems,
I had the following set in my /etc/rc.conf file:
kern_securelevel_enable="YES"
kern_securelevel="1"
And had to disable this to allow the device
to load properly, then I re-enabled it.
Thanks again,
From: Simpson Chua
[mailto:strain17 yahoo.com]
Sent: Wednesday, May 30, 2007
11:17 pm
To: John S. Strock
Subject: RE: Zaptel
John,
Depending on how the extensions.conf is configured, your callerID will or will
not be displayed. Without doing any troubleshooting, I can't say this with
certainty.
see if adding this string in your zapata.conf will help:
callerid = asreceived
To troubleshoot - login to the asterisk cli with higher verbosity
"asterisk -rvvvvvvvvvvvvc"
Make and inbound call and see if the Calling Party number is displayed. You can
trace it from there and see which context it was sent to and how it is being
manipulated before it reaches your extension.
Of course we're also talking about caller id delivery on FXO, I'll have to look
into this a little more as my experience is primarily with FXS on PRI/CAS
trunks.
Eitherways, do let me know how it goes.
Thanks,
Simpson
"John S.
Strock" <jstrockbatc.edu>
wrote:
I do have the options you’ve
specificed in my Zapata.conf file. ; You mention the extenions.conf file
for outbound, does that also affect inbound? Outbound callerid is fine,
it’s the inbound caller id that’;s not working. I tested to
see if caller id information was being sent (and not being blocked) by our
phone provider by calling from one phone to another, then calling from that
same phone into the asterisk pbx, but when it gets into the pbx, it displays
“unknown”.
Regarding fixing my original problem, I
think most of the issue had to do with not having
zaptel_enable=”YES” in my rc.conf file. ; Installing asterisk
from the FreeBSD ports installed everything I needed included the .ko modules.
Once I enabled zaptel in rc.conf, then I took a little more time going through
the zapatel.conf, and zaptel.conf files to figure out how to configure.
This biggest hang up was the rc.conf file because I was getting errors where
documentation was saying I shouldn217;t.
From: Simpson Chua
[mailto:strain17yahoo.com]
Sent: Wednesday, May 30, 2007
12:21 pm
To: John S. Strock
Subject: RE: Zaptel
Hi,
Please check your zapata.conf file and make sure it has these fields below
[channels]:
usecallerid=yes
hidecallerid=no
usecallingpres=yes
callwaitingcallerid=yes
Try to see if that works. If not, you might have to check how you setup your
outbound dialing in extensions.conf.
Let me know.
Simpson
P.S. If you can, please update the BSD list to let the community know how you
were able to resolve your problem. It might be beneficial to future users.
Thanks again!
"John S.
Strock" <jstrockbatc.edu>
wrote:
Thank you for your help. ; I was able to get everything
working both inbound and outbound, and I’ve got one last question (for
now), how do I enable inbound caller ID? All inbound calls show up as
unknown, yet all phone that I tested allow caller ID to be sent.
From: Simpson Chua
[mailto:strain17yahoo.com]
Sent: Tuesday, May 29, 2007 11:53
pm
To: jstrock
Subject: Zaptel
John,
Forgot
one more thing, once you ztcfg -vvvvvvvv, you need to login to the Asterisk CLI
(asterisk -rvvvvvvvc) and do a "restart gracefully" to reload the zap
channels.
It should be working now.
In the CLI - a "zap show channels"
should show you the status of the channels.
Let me know how it goes.
Simpson
It's here! Your new message!
Get new
email alerts with the free Yahoo!
Toolbar.
|
[1]
|
|
|
about | contact Other archives ( Real Estate discussion Medical topics )
|