2 months ago when I struggled with E1 trunks and OpenZAP in freeswitch there was a timer problem which was not solved yet. This caused channels to be busy in my case.
I am not sure whether this is solved yet. Can anybody confirm? Best regards Peter Mark Tabron schrieb: > We're a couple more steps forward from yesterday. Turned out some of my > regex was incorrect, plus example #9 in the Freeswitch Dialplan Wiki has > an extra space before one of the closing brackets in the default.xml > example. After staring at the screen all day it's funny how you miss > these things! > > Situation now is I can get the call into FS but, it rings the extension > for a fraction of a second then the call drops. Here's the contents of > the public and default dialplans I'm using (as per example in the wiki) > and the debug - http://pastebin.freeswitch.org/7819 > > I'm also seeing another issue when placing subsequent inbound calls, > they bounce if hitting the same channel the first call came in to > (typically /1:1). Again, grabbed a debug of this - > http://pastebin.freeswitch.org/7818 > > Getting there (slowly) > > Mark. > > <quote author="mercutioviz"> > On Tue, Mar 17, 2009 at 4:24 AM, Mark Tabron > <[email protected]> wrote: > >> Another update - this time (part) good news! Decided to run >> > wancfg_tdmapi again, using the same settings as we always did, and we > can now make external calls. I suspect that whatever BT did yesterday > kicked the circuit back into life. > > Good. I can't tell you how many times I've spoken to a telco when > there's a problem and the circuit magically comes back to life. They > frequently claim, "We didn't do anything." I think that's a euphemism > for "we did a reset and prayed." > > >> However placing an external call into FS isn't as successful, looks >> > like it can't assign a channel and terminates the call. > > > Be sure that you have some routing mechanism in your public.xml file. > Do you have a whole block of DID numbers? Anyway, pastebin your > public.xml and a debug trace of an incoming call, including what phone > number the caller dialed, and we'll take a look. > > -MC > > _______________________________________________ > Freeswitch-users mailing list > [email protected] > http://lists.freeswitch.org/mailman/listinfo/freeswitch-users > UNSUBSCRIBE:http://lists.freeswitch.org/mailman/options/freeswitch-users > http://www.freeswitch.org > > </quote> > > -----Original Message----- > From: [email protected] > [mailto:[email protected]] On Behalf Of > Michael Collins > Sent: 17 March 2009 15:48 > To: [email protected] > Subject: Re: [Freeswitch-users] Problem dialing out via E1 > > On Tue, Mar 17, 2009 at 4:24 AM, Mark Tabron > <[email protected]> wrote: > >> Another update - this time (part) good news! Decided to run >> > wancfg_tdmapi again, using the same settings as we always did, and we > can now make external calls. I suspect that whatever BT did yesterday > kicked the circuit back into life. > > Good. I can't tell you how many times I've spoken to a telco when > there's a problem and the circuit magically comes back to life. They > frequently claim, "We didn't do anything." I think that's a euphemism > for "we did a reset and prayed." > > >> However placing an external call into FS isn't as successful, looks >> > like it can't assign a channel and terminates the call. > > > Be sure that you have some routing mechanism in your public.xml file. > Do you have a whole block of DID numbers? Anyway, pastebin your > public.xml and a debug trace of an incoming call, including what phone > number the caller dialed, and we'll take a look. > > -MC > > _______________________________________________ > Freeswitch-users mailing list > [email protected] > http://lists.freeswitch.org/mailman/listinfo/freeswitch-users > UNSUBSCRIBE:http://lists.freeswitch.org/mailman/options/freeswitch-users > http://www.freeswitch.org > > Save paper - don't print this email unless you need to. > > -------------------------------------------------------------------------------- > NOTICE from RNID Typetalk > > This communication contains information which is confidential and may also be > privileged. It is for the exclusive use of the addressee. > If you are not the addressee, please note that any distribution, > dissemination, copying or use of this communication or the information in it > is prohibited. If you have received this message in error, please notify the > sender immediately at the above e-mail address and delete the information > from your computer system. > Please note that neither RNID nor the sender accepts any responsibility for > viruses and it is your responsibility to scan the email and attachments (if > any). > > > > -------------------------------------------------------------------------------- > > > > > > _______________________________________________ > Freeswitch-users mailing list > [email protected] > http://lists.freeswitch.org/mailman/listinfo/freeswitch-users > UNSUBSCRIBE:http://lists.freeswitch.org/mailman/options/freeswitch-users > http://www.freeswitch.org > > _______________________________________________ Freeswitch-users mailing list [email protected] http://lists.freeswitch.org/mailman/listinfo/freeswitch-users UNSUBSCRIBE:http://lists.freeswitch.org/mailman/options/freeswitch-users http://www.freeswitch.org
