On Sun, Dec 13, 2009 at 9:56 AM, Tzury Bar Yochay
wrote:
> Hi all,
>
> I am getting a frustrating errors while trying to build the latest wanpipe
> on my newly and freshly installed Ubuntu 9.10
>
> I pastebin the output at http://gist.github.com/255442 and would
> appreciate any help.
>
>
Hi Tzury
Hi all,
I am getting a frustrating errors while trying to build the latest wanpipe
on my newly and freshly installed Ubuntu 9.10
I pastebin the output at http://gist.github.com/255442 and would appreciate
any help.
Thanks,
--
Tzury Bar Yochay
___
Fre
Q.931 and Q.921 are protocols for Euro ISDN. So this is the right protocol.
See here: http://www.voip-info.org/wiki/view/EuroISDN
Best regards Peter
Niall Crosby schrieb:
> Sorry, my mistake.
>
> I was asked by telco to specifically use Euro dialect, will using Q931
> cause any issues?
>
> tnks
>
euro and q931 are the same thing on most devices.
Europe uses pure q931 where most other places use "enhanced" versions of it.
On Fri, Jul 31, 2009 at 9:45 AM, Niall Crosby wrote:
> Sorry, my mistake.
>
> I was asked by telco to specifically use Euro dialect, will using Q931
> cause any issues?
Sorry, my mistake.
I was asked by telco to specifically use Euro dialect, will using Q931
cause any issues?
tnks
2009/7/31 Peter P GMX :
>>I was asked by telco to specifically use telco, will using Q931 cause
>>any issues for me?
>
> Sorry, I do not not understand that question.
>
> Best regards
>I was asked by telco to specifically use telco, will using Q931 cause
>any issues for me?
Sorry, I do not not understand that question.
Best regards
Peter
Niall Crosby schrieb:
> Thanks for help.
>
> Got my alarms sorted - telco had problem there.
>
> As for my Freeswitch problem, chaning to Q9
Thanks for help.
Got my alarms sorted - telco had problem there.
As for my Freeswitch problem, chaning to Q931 clears the error message.
I was asked by telco to specifically use telco, will using Q931 cause
any issues for me?
Thanks again,
Niall.
2009/7/31 Peter P GMX :
> Firstly I would try g
Firstly I would try get get rid of the sangoma errors. There are 2 errors:
Short Circuit: ON
Loss of Signal: ON
So either the card is not configured correctly or there is a cabling
problem. What is your wanpipe1.conf?
Second, if euro doesn't work, try Q931.
I had success with that some time ago
Not libpri (hadn't heard of this), am using Openzap.
Sangoma support got back and say that the alarms should be cleared
even when Freeswitch is not running (which is not the case for me) so
looks like it's nothing to do with Freeswitch.
Also Sangoma pointed out to me that my Rx Level is < -44db w
Pastebin your configs. Also, are you using libpri?
-MC
Sent from my iPhone
On Jul 30, 2009, at 7:26 AM, Niall Crosby
wrote:
> Hi,
>
> This might be Sangoma config issue, so apologies in advance for
> posting it here if it is. I am waiting for Sangoma helpdesk to get
> back to me!
>
> But I h
Hi,
This might be Sangoma config issue, so apologies in advance for
posting it here if it is. I am waiting for Sangoma helpdesk to get
back to me!
But I have a Sangoma a101 and trying to get it working with
Freeswitch. Have E1 line coming from telco and everything set up
correctly (to my best eff
It's not critical it just means there are no zaptel devices configured.
The D channel does not use the state mechanism at the moment so the state
probably will always say down. I might change that to show up in the future
but it's more of an aesthetic change.
On Wed, May 21, 2008 at 4:15 AM, Hel
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi Anthony,
I reinstalled wanpipe driver. I configured it with freeswitch option
(TDM_VOICE_API) and no zaptel. openzap.conf is same as before (span
wanpipe). Wanpipe channel devices are created in /dev by wanrouter as it
should be. when freeswitch st
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi Lukasz,
yeah, I learned that yesterday ;) Anthony explained it already, you
confirmed it and I got it up and running. Thx!
regards
Helmut
Lukasz Kutkowski schrieb:
| Hi,
|
| I don't know if this solve your problems but if you use zaptel and
| wa
Hi,
I don't know if this solve your problems but if you use zaptel and
wanpipe then /etc/openzap/openzap.conf should have:
[span zt]
If you use wanpipie with tdm api then /etc/openzap/openzap.conf should have:
[span wanpipe]
Regards,
Lukasz
Helmut Kuper wrote:
> -BEGIN PGP SIGNED MESSAGE
you can also try to add freeswitch user to the group owning the devices
take a look to usermod and -G switch
2008/5/20 Brian West <[EMAIL PROTECTED]>:
> You can chown the devices or change the permissions so the non-root
> user can access those. I think the udev rules would need to be
> change
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hello Anthony,
thanks for your explanations. I undid my changes to zip_wanpipe.c and
reconfigured wanpipe1.conf as explained manually. That works :)
But there is still the problem that freeswitch has to be root user to
get access to the TDM devices c
You can chown the devices or change the permissions so the non-root
user can access those. I think the udev rules would need to be
changed also so that they are created with the right permissions next
time you start.
/b
On May 20, 2008, at 12:13 PM, Helmut Kuper wrote:
> -BEGIN PGP S
That is horribly wrong.
If you are using wanpipe under zaptel you forget it is a wanpipe device and
configure it under zaptel.
with [span zt]
There are specific instructions for setting up the wanpipe in standalone
mode that does not require zaptel at all.
in the /etc/wanpipe/wanpipe1.conf you ha
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hello,
sorry for my last post here. It was wrong. So here the correct message ;)
I fixed it. Problem is, that my zaptel API, which was automaticly
compiled and configured by sangoma's wanpipe driver setup, creates all
channel devices in /dev/zap wit
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hello,
I fixed it. problem is, that my zaptel API, which was automaticly
compiled and configured by sangoma's wanpipe driver setup, expects all
channel devices in /dev with the name format wptdm_sXcY, where X=span
number and Y=channel number. My Zapt
On Tue, 2008-05-20 at 17:16 +0200, Helmut Kuper wrote:
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA1
>
> Hello,
>
> since mod_wanpipe is depricated, I try to get freeswitch with openzap,
> zaptel, wanpipe and Sangoma A101 E1-Pri-card running.
>
> I use zaptel-1.4.2, wanpipe-3.1.4 and ubuntu
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi again,
further debugging shows that zap_wanpipe assumes that channel devices
are directly located in /dev called e.g. "wptdm_s1c22" for span 1
channel 22.
Is there a way to configure the device path and name?
regards
helmut
Helmut Kuper schrieb
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi,
I found that the console lines
2008-05-20 16:30:59 [ERR] zap_zt.c:721 zt_init() Cannot open control device
2008-05-20 16:30:59 [ERR] zap_io.c:2050 zap_global_init() Error
initilizing zt.
Were caused by having wrong permissions on /dev/zap/ctl.
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hello,
since mod_wanpipe is depricated, I try to get freeswitch with openzap,
zaptel, wanpipe and Sangoma A101 E1-Pri-card running.
I use zaptel-1.4.2, wanpipe-3.1.4 and ubuntu 2.6.20-16-server. ztcfg -vv
~ detects all channels and "wanrouter list" s
25 matches
Mail list logo
