HELP! T1 PRI is not working after move

Status
Not open for further replies.

rmayer

Joined
Jan 7, 2010
Messages
58
Reaction score
0
Verizon says that there is nothing wrong on their end and that there is a problem with the D-channel communications with the Pattan 4960. The system was working fine before the move, it also worked for about 30 minutes after the move but has not worked since. I need a solution ASAP and I am willing to pay if needed(does 3cx have an emergency contact/support?). Please respond if you need my contact info.

Thanks!
 
Hi

What move exactly? Can you be more specific?

If you changed nothing in the Patton and nothing was changed in the provider side, then it has to work.

What is not working exactly?
What version of 3CX are you using?

I can tell you from now that we changed absolutely nothing in this area and things with Patton and ISDN remained working as they were before.

Also you can send the Patton running configuration on this email addr for checking [email protected] giving proper details of what is not working exactly.

Also if it worked for 30 minutes and then it stopped working, then it could be that there might be a problem with the device as well. It is possible.

Let me know
 
We moved to a new location. I've been talking to verizon and I found out they switch us from ni2 to dms-100. However, after switching the patton 4960 over to dms-100 the issue is still not resolved. I'm currently having verizon switch us back to ni2 to see if that solves the problem. I've attached my current config.

Thanks!
 

Attachments

Not working after the switch, verizon says it's still in D-Channel lockout...
 
Yes your config still thinks that the patton is expecting ni2 - no wonder it is not syncing.

if they moved you to dms100, then you have to change this to dms100

protocol ni2

uni-side user
bchan-number-order ascending
encapsulation cc-isdn
bind interface IF_ISDN_0 switch

port e1t1 0 0
no shutdown
 
Turns out our riser managment company extended the pairs wrong which caused the issue.

It's fixed now,
Thanks!
 
Status
Not open for further replies.

Latest Posts

Forum statistics

Threads
111,880
Messages
589,533
Members
164,733
Latest member
HLISolutions