VoIP Mailing List Archives
Mailing list archives for the VoIP community |
|
| View previous topic :: View next topic |
| Author |
Message |
msc at freeswitch.org
Guest
|
 Posted: Wed Apr 08, 2009 2:08 am Post subject: [Freeswitch-users] need help getting ISDN talking to Cisco 3 |
 |
|
John,
Okay, a few things. First off, the wanpipe2.conf file has a booboo. This line is WRONG:
TDMV_DCHAN = 0
For ISDN in North America you want:
TDMV_DCHAN = 24
Also, I recommend changing this line:
wbg1 = wanpipe2, , TDM_VOICE, Comment
To this:
wbg1 = wanpipe2, , TDM_VOICE_API, Comment
A sample config for Sangoma wanpipeX.conf is here:
http://wiki.freeswitch.org/wiki/OpenZAP#Wanpipe_mode
Okay, ISDN 101: there is a "network" side and a "user" side. (Also called "terminal" or "cpe"). From what I see here you are trying to have FS be the network side and the Cisco is the user side. Assuming that this is what you want then you will need to use ozmod_libpri because the default OpenZAP PRI stack does not currently support being the network side. You will need to download and install libpri from downloads.digium.com and then you'll need to reconfigure openzap. Follow these instructions to get libpri and openzap working together:
http://wiki.freeswitch.org/wiki/OpenZAP#Adding_libpri_Support
And then check out this example openzap.conf.xml file for using libpri:
http://wiki.freeswitch.org/wiki/Openzap.conf.xml_Examples#Using_with_PRI_.28libpri_compatibility_stack.29
(Note that you don't want 'cpe' here but rather 'network'.)
Now, on the Cisco side... sorry, can't help you. However, I don't see any glaring gotchas from looking at the configs. I don't see where timing is specified nor do I see where the d channel is specified. Hopefully you can confirm that those are set properly. (The cisco needs to be a "slave" to the FS clock, also called "receiving clock"; d-channel is 23 or 24 depending on how cisco numbers their channels.)
Have fun! 
-MC
On Tue, Apr 7, 2009 at 5:37 PM, John Wehle <john@feith.com (john@feith.com)> wrote:
| Quote: | Our FreeSWITCH setup has an existing T1 using RBS to talk to a digital
modem pack in a Cisco 3845. I'm interested in changing from RBS to
ISDN. I changed both sides, restart things, and see FreeSWITCH report:
|
|
|
| Back to top |
|
 |
msc at freeswitch.org
Guest
|
| Posted: Thu Apr 09, 2009 10:50 am Post subject: [Freeswitch-users] need help getting ISDN talking to Cisco 3 |
|
|
John,
Just curious - why are you using zaptel at all? Does it provide something for you that the wanpipe drivers do not? I use Sangoma only with Sangoma cards and I have a lot of success.
-MC
On Wed, Apr 8, 2009 at 3:19 PM, John Wehle <john@feith.com (john@feith.com)> wrote:
| Quote: | > Okay, a few things. First off, the wanpipe2.conf file has a booboo.
Don't think so.
| Quote: | This line is WRONG:
TDMV_DCHAN = 0
|
Not exactly. My understanding is you can use either:
wanpipeX.conf: TDMV_DCHAN = 0
zaptel.conf: dchan = 24 (or in our case 48 since it's the second span)
which means use zaptel to handle the d-channel hdlc or
wanpipeX.conf: TDMV_DCHAN = 24
zaptel.conf: hardhdlc = 24 (or in our case 48 since it's the second span)
which means use wanpipe to handle the d-channel hdlc assuming the
wanpipe driver has the necessary support (wanpipe on my platform
doesn't).
| Quote: | Also, I recommend changing this line:
wbg1 = wanpipe2, , TDM_VOICE, Comment
To this:
wbg1 = wanpipe2, , TDM_VOICE_API, Comment
|
The sangoma voice API interface isn't available on my platform
and shouldn't be necessary when using zaptel.
| Quote: | assuming that this is what you want then you will need to use
ozmod_libpri because the default OpenZAP PRI stack does not
currently support being the network side.
|
Are you sure? Openzap appears to contain implementations for
both NT and TE. The configuration file supports specifying
either user or network for the mode. Is the NT support
currently nonfunctional?
I had tried configuring the Cisco as the NT with similar
results.
| Quote: | I don't see where timing is specified
|
It's the same T1 which was being used for RBS between
FreeSWITCH and the Cisco so that timing (etc) should
be okay. No errors are showing up at the physical
level and the Cisco reports Layer 1 as active.
The trace on the Cisco seems to show Layer 2 coming up
(timestamps 22:53:44.264 through 22:54:21.760), then
there's a long pause during which no Receive Ready
frames are received from FreeSWITCH. At this point
the Cisco gets unhappy and marks Layer 2 as down.
If nothing obvious comes to anyone's mind, then I'll
simply need to trace through the FreeSWITCH ISDN code
and see what's going on.
-- John
-------------------------------------------------------------------------
| Feith Systems | Voice: 1-215-646-8000 | Email: john@feith.com (john@feith.com) |
| John Wehle | Fax: 1-215-540-5495 | |
-------------------------------------------------------------------------
_______________________________________________
Freeswitch-users mailing list
Freeswitch-users@lists.freeswitch.org (Freeswitch-users@lists.freeswitch.org)
http://lists.freeswitch.org/mailman/listinfo/freeswitch-users
UNSUBSCRIBE:http://lists.freeswitch.org/mailman/options/freeswitch-users
http://www.freeswitch.org
|
|
|
| Back to top |
|
|
|
|
|
You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot vote in polls in this forum
|
Powered by phpBB © 2001, 2005 phpBB Group
|
Search
