You might want to try the ozmod_pri instead of ozmod_isdn until the new revision of ozmod_isdn is published into the source tree.<br><br><br><div class="gmail_quote">On Thu, Oct 1, 2009 at 9:37 AM, <span dir="ltr"><<a href="mailto:Russell.Mosemann@cune.org">Russell.Mosemann@cune.org</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">We have connected FS to a Siemens Hicomm 300. As you might guess, it's<br>
not working right. Here is what we are working with.<br>
<br>
Dell 1750 (dual socket, dual core Xeon 2.8GHz)<br>
Debian 5<br>
FS (15029), OpenZAP (without libpri)<br>
TE110P T1 card (Zaptel driver)<br>
Handles 71xx extensions<br>
<br>
Siemens Hicom 300<br>
TMDN64P T1 card<br>
Handles 74xx extensions<br>
<br>
We are pretty much using the stock FS configuration, yet, because we're<br>
trying to get this to work. I have configured OpenZAP and the associated<br>
files like the examples on the wiki (see below) to work with a PRI T1.<br>
There are 23 B channels and 1 D channel. The Zaptel side looks fine.<br>
OpenZAP is able to open the channels when FS boots. So far, so good.<br>
<br>
When a call is made from 74xx (Rolmphone 624) to 71xx (X-Lite 4.0 beta<br>
from CounterPath on an office PC), X-Lite rings. The call can be<br>
answered, and the conversation sounds fine. That means the routing,<br>
registration and authorization are working on the network between X-Lite<br>
and FS. It also means that FS is able to communicate with the Hicom over<br>
the T1. Great.<br>
<br>
When the caller presses the transfer button on the 74xx phone, the Hicom<br>
sends a message over the D channel, and the call is disconnected<br>
(watching with fs_cli). As best I can interpret the bytes in the message,<br>
the Hicom sends a disconnect message when 74xx presses the transfer key.<br>
<br>
In order to call 74xx, I created dialplan/default/02_hicom.xml. The<br>
contents are<br>
<br>
<include><br>
<extension name="hicom"><br>
<condition field="destination_number" expression="^(74\d{2})$"><br>
<action application="bridge" data="openzap/1/a/$1"/><br>
</condition><br>
</extension><br>
</include><br>
<br>
If a call is made from 71xx to 74xx, the Hicom forwards the call to the<br>
switchboard with "7100->7445 connection not possible" (or whatever<br>
extensions) in the switchboard display.<br>
<br>
1. Are these issues related to the way I have configured FS?<br>
<br>
The Hicom is maintained by the local phone company. I do not have access<br>
to view or configure the T1 card on the Hicom. According to the phone<br>
guy, there isn't anything else that needs to be configured on the Hicom.<br>
He believes that if 74xx can call 71xx, then 71xx should be able to call<br>
74xx.<br>
<br>
I suspect that something more needs to be done on the Hicom in order to<br>
accept calls from FS and bridge/transfer them to a local extension on the<br>
Hicom. It's as if the Hicom doesn't know how or is not permitted to route<br>
incoming calls on the T1 to local extensions. I have no way to know,<br>
though. I'm hoping someone else has connected FS to a Hicom 300 and can<br>
provide configuration details. If I could tell the phone guy something<br>
like, "You need to look at <this>," that would help him out.<br>
<br>
2. Should I receive CID/ANI from the Hicom?<br>
<br>
X-Lite displays "OpenZAP" as the call and "1" as Other when the call<br>
comes in, which is the information for the endpoint. Is there something I<br>
need to do in the FS configuration to capture CID/ANI information from<br>
the Hicom and make it available (or is it not being provided by the Hicom)?<br>
<br>
3. When dialing from the Rolmphone is there a way for FS to send the<br>
called name back to the Hicom for it to appear in the display?<br>
<br>
When dialing 74xx to 74xx, of course, it shows the called number and name<br>
in the display. We also have a HiPath 4000 connected to the Hicom 300.<br>
When dialing an extension on the HiPath from the Hicom, the HiPath ships<br>
the called name back to the Hicom for display on the phone. It would be<br>
nice to do that from FS.<br>
<br>
Let me know if you need additional information. Thanks for any pointers<br>
or insight as to how things work.<br>
<br>
--<br>
Russell Mosemann<br>
<br>
<br>
openzap.conf<br>
[span zt PRI_1]<br>
name => OpenZAP<br>
number => 1<br>
trunk_type => t1<br>
b-channel => 1-23<br>
d-channel => 24<br>
<br>
zt.conf<br>
[defaults]<br>
codec_ms => 20<br>
wink_ms => 150<br>
flash_ms => 750<br>
echo_cancel_level => 64<br>
rxgain => 0.0<br>
txgain => 0.0<br>
<br>
openzap.conf<br>
<configuration name="openzap.conf" description="OpenZAP Configuration"><br>
<settings><br>
<param name="debug" value="0"/><br>
<!--<param name="hold-music" value="$${moh_uri}"/>--><br>
<!--<param name="enable-analog-option" value="call-swap"/>--><br>
<!--<param name="enable-analog-option" value="3-way"/>--><br>
</settings><br>
<pri_spans><br>
<span name="PRI_1"><br>
<param name="q921loglevel" value="alert"/><br>
<param name="q931loglevel" value="alert"/><br>
<param name="mode" value="user"/><br>
<param name="dialect" value="national"/><br>
<param name="dialplan" value="XML"/><br>
<param name="context" value="public"/><br>
</span><br>
</pri_spans><br>
</configuration><br>
<br>
zaptel.conf<br>
# Span 1: WCT1/0 "Digium Wildcard TE110P T1/E1 Card 0" (MASTER)<br>
span=1,1,0,esf,b8zs<br>
# termtype: te<br>
bchan=1-23<br>
dchan=24<br>
<br>
# Global data<br>
loadzone = us<br>
defaultzone = us<br>
<br>
<br>
________________________________________________________<br>
Concordia University, Nebraska<br>
See <a href="http://www.cune.edu/" target="_blank">http://www.cune.edu/</a> for the latest news and events!<br>
<br>
<br>
_______________________________________________<br>
FreeSWITCH-users mailing list<br>
<a href="mailto:FreeSWITCH-users@lists.freeswitch.org">FreeSWITCH-users@lists.freeswitch.org</a><br>
<a href="http://lists.freeswitch.org/mailman/listinfo/freeswitch-users" target="_blank">http://lists.freeswitch.org/mailman/listinfo/freeswitch-users</a><br>
UNSUBSCRIBE:<a href="http://lists.freeswitch.org/mailman/options/freeswitch-users" target="_blank">http://lists.freeswitch.org/mailman/options/freeswitch-users</a><br>
<a href="http://www.freeswitch.org" target="_blank">http://www.freeswitch.org</a><br>
</blockquote></div><br><br clear="all"><br>-- <br>Anthony Minessale II<br><br>FreeSWITCH <a href="http://www.freeswitch.org/">http://www.freeswitch.org/</a><br>ClueCon <a href="http://www.cluecon.com/">http://www.cluecon.com/</a><br>
Twitter: <a href="http://twitter.com/FreeSWITCH_wire">http://twitter.com/FreeSWITCH_wire</a><br><br>AIM: anthm<br><a href="mailto:MSN%3Aanthony_minessale@hotmail.com">MSN:anthony_minessale@hotmail.com</a><br>GTALK/JABBER/<a href="mailto:PAYPAL%3Aanthony.minessale@gmail.com">PAYPAL:anthony.minessale@gmail.com</a><br>
IRC: <a href="http://irc.freenode.net">irc.freenode.net</a> #freeswitch<br><br>FreeSWITCH Developer Conference<br><a href="mailto:sip%3A888@conference.freeswitch.org">sip:888@conference.freeswitch.org</a><br><a href="http://iax:guest@conference.freeswitch.org/888">iax:guest@conference.freeswitch.org/888</a><br>
<a href="mailto:googletalk%3Aconf%2B888@conference.freeswitch.org">googletalk:conf+888@conference.freeswitch.org</a><br>pstn:213-799-1400<br>