in your wanpipe.conf file change
TE_SIG_MODE = CCS
to
TE_SIG_MODE = CAS
Saludos/Regards
-
Gerardo Barajas
ClearlyIP
www.clearlyip.com
On Tue, Mar 8, 2022 at 3:43 PM Duncan Turnbull
wrote:
> Hi Carlos
>
> On Wed, Mar 9, 2022 at 10:30 AM Carlos Chavez wrote:
>
>> The provider is
Hi Carlos
On Wed, Mar 9, 2022 at 10:30 AM Carlos Chavez wrote:
> The provider is the timing source. Both wanpipe1.conf and
> system.conf have the timing sources set to the remote side:
>
> TE_CLOCK = NORMAL
>
> Makes sense, I couldn't recall the options but this looks right
>
>
The provider is the timing source. Both wanpipe1.conf and
system.conf have the timing sources set to the remote side:
TE_CLOCK = NORMAL
span=1,1,0,CAS,HDB3
I still have a feeling that the problem is on the providers side as
during testing we never saw the issue.
I have
It’s been a r we hike since we used these cards. This example may help
https://wiki.freepbx.org/plugins/servlet/mobile?contentId=73007457#content/view/73007457
My thinking is it sounds like a timing error. Make sure your provider is the
timing source. Once it loses time you will get dropped
Hello,
I must admit that I have never set up an asterisk system with R2 signalling.
But from the config files
point of view, you stated TE_SIG_MODE in wanpipe1.conf as ccs which should be
cas, right ?
If this does not help, you need to connect an external E1 Monitor.
Regards,
Hans
Am
Last month we switched a Panasonic pbx with a Freepbx 16
appliance. We use a single E1 in MFC/R2 (Mexico) with Telmex as a
provider. This was connected for a couple of days for testing with no
problems before the client moved offices to a new location. In the new
location we are now
