|
|
|
|
Joined: Feb 2014
Posts: 660
Moderator-1A2
|
|
Moderator-1A2
Joined: Feb 2014
Posts: 660 |
It's been a long time since I tested T1 circuits. I think CRC errors indicate a coding mismatch (AMI/B8ZS). I definitely have them both configured for B8ZS. I figure it wouldn't work at all if the coding was wrong, correct?
|
|
|
|
|
Joined: Dec 2005
Posts: 9,181 Likes: 9
Spam Hunter
|
|
Spam Hunter
Joined: Dec 2005
Posts: 9,181 Likes: 9 |
It would work to a degree. A framing mismatch would be service affecting.
I Love FEATURE 00
|
|
|
|
|
Joined: Mar 2018
Posts: 345 Likes: 1
Member
|
|
Member
Joined: Mar 2018
Posts: 345 Likes: 1 |
Had an issue where the Telco told us "it's a standard PRI". So we installed everything and tested in and outbound calling. It all worked, but within an hour had severe issues. Turns out the PRI was set for 5ESS, and the phone system was NI2. I don't know if you can change any of those settings in the Partner, or if it is hard set.
The Cloud is just someone else's computer!
|
|
|
|
|
Joined: Dec 2005
Posts: 9,181 Likes: 9
Spam Hunter
|
|
Spam Hunter
Joined: Dec 2005
Posts: 9,181 Likes: 9 |
The Partner ACS doesn't work with ISDN/PRI. It supports inband signaling. (T1E&M Wink for example).
I Love FEATURE 00
|
|
|
|
Forums84
Topics94,527
Posts640,019
Members49,852
| |
Most Online5,661
May 23rd, 2018
|
|
|
0 members (),
114
guests, and
48
robots. |
|
Key:
Admin,
Global Mod,
Mod
|
|
|
|
|
|
