Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations Shaun E on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

Wierd PRI/Target line issue 2

Status
Not open for further replies.

Norstarguy

Vendor
Mar 29, 2002
150
US
Hello guys-

I've got a system I'm trying to program remotely that I'm having an issue with and can't seem to figure out.

I've done numerous PRI installs without a hitch, but haven't seen this problem before. Got the target lines built, got outbound working fine with the routing, etc- however the calls aren't being routed properly across the target lines...in fact, they won't ever ring on the targets. Only rolls in to the prime set on the PRI Trunks, ie x6800 in this case.

I have verified from the provider end that they are sending me 4 digits (as is programmed in the MICS), so that isn't the issue, had their NOC on the phone verifying that they can see the 4 digits going out to my MICS on test calls...but I've been beating my head against a wall on this for the last two days.

Any ideas? I'm really of the opinion that it's something screwy on the circuit itself, but trying to tell VZ that has its own "complications" LOL.

TIA-

NG
 
A bit of clarification, this is a MICS 4.1 (customer provided equipment).

Thx-

NG
 
there must be no prime sets for the physical trunks and trunks must not appear on any set
 
Senk1s-

Thx for the reply. The trunks are not set to appear on any telephone, but there is a prime set associated for the trunks.

I've never had to remove the prime set before for PRI trunks, so I don't know why this would be causing the problem. Can you give me any insight on this?
 
thats the way it is supposed to be set -
so to speak, 'the physical trunk as such doesnt deal with the DN specifc call processing' - the target line does
 
Ok, Just dialed in and made the change. No change. The line still rings on the dialing phone (my cell) but it still doesn't come in on the target line on the set. Not sure where it's ringing now though...outer space maybe?

I've done probably 30 or so installs and never removed the prime set on the PRI trunks. I knew you're supposed to do that on E&M trunking on T1's though to get DID's to work, but not PRI- but I've not run into this problem before.

Any other ideas as to what it might be?

TIA!

NG
 
There is no auto answer setting-

Line 001:

Trk type: PRI

Line Type: PRI A

Prime Set: None

End of list
 
sorry got confused with t1 settings ...
are the protocols matching with the CO?
how about sequencing of B channels - asc or desc?

if OG is working without problems ...then start checking with the CO
 
No problem!

The protocols are all matching, CO is coming in ascending.

I think I've eliminated everything on my side, so I'm in agreement with you that there's something screwball going on with the CO- however trying to get them to understand that when they're seeing the digits outpulsing to me is going to be next to impossible.

Just wanted to check if there were any ideas as to what it might be- if anyone has any ideas, feel free to chime in!

NG

 
You said you verified they are sending 4 digits? You might want to re-verify that with them. your symptoms match exactly what a lenght problem would cause.

MarvO said it
 
Update:

Ok, had the Verizon tech onsite this morning. He was able to capture the receive digits on his test set from the D-Channel...so all of that is good.

Still having the same problem. If it wasn't for the fact that I'm getting a solid green sync with no errors on my system, and that I'm able to make outbound calls, I'd suspect my combo card was wacked out....but I can't see how any of this would be possible if my system wasn't able to sync using the D-Channel.

Any ideas???
 
Try assigning the TL's as
Private to:6810
Recvd digits:6810
Prime:6810
CLID Set:6810
and see what happens on an inbound call
What version of 4.1 are you using? WI6.13 & 6.15 were the best of the bunch
 
are we using any service modes that have physical trunks assigned to that set

6 months until ski season starts...sadly i must resign myself to the warmer weather"this will include a normal 8-5 work day, 5 days a week"
 
Sprucegrover- I'll give that a shot, the only change I'll have to make to the existing line programming is making the lines private- everything else is already setup as you described.

luv2ski- No service modes. All of the programming is still default with the exception of the 4 or 5 test target lines, the programming needed that should make the PRI work, and the outbound route.

NG
 
if you have trunk prime set to none and and target lines set to private
to said ext and primed to that ext and they still go to the operator console then the only way for that to happen is for the trunks to be assigned in services"defaults to this assignment" same with target lines..if the target line recvd digit length was wrong would ring trunk not target line and again if trunks were set to no prime then call should iether ring no answer or ring busy

6 months until ski season starts...sadly i must resign myself to the warmer weather"this will include a normal 8-5 work day, 5 days a week"
 
luv2ski-

I'm a little confused. If there are no service modes active, why would services have anything to do with this issue? Can you clarify?

Also, Although this isn't the case here (because they match), I've had 4 digits transmitted and had the Norstar at 3 digit receive and had this go without a hitch- because the Norstar just sees the last 3 digits of the pulsed numbers and route the calls.

I'll try privating the lines this morning- however the biggest problem I'm going to have is there are 5 lines they want in a hunt group (to ring on several extensions) so I'm not sure how that will work out in the end.

NG
 
all i am saying
is give peace a chance oops\

the config default is as i stated ..just make sure the service modes are all off and not manual or auto..thats all

and did you see the screen on the co techs test set and see the 4 digits?

and who else is involved...who is provider of circuit...verizon is span are they the provider also

6 months until ski season starts...sadly i must resign myself to the warmer weather"this will include a normal 8-5 work day, 5 days a week"
 
Ok, thx for the clarification!

VZ is the span and provider. No, I did not see the four digits as I am in Dallas doing the programming remotely and this customer is in Houston- however I was doing the test calls, not telling the VZ tech was I was dialing, and he was reading off the correct 4 digits, so he wasn't "cheating" :)

I'm going to have an onsite tech replace the combo card either this afternoon or Monday morning as well. We've already swapped the DTI card with no affect. The VZ CO insists there is something going on with my system and the D channel, and since the VZ tech has confirmed he's seeing the digits, I'm starting to run out of ammo with them.

NG
 
Are you set for internal CSU, or are you using external CSU?

MarvO said it
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top