cbennett912

I have a IP403 2.1.24 with T1 blade.

I took POTS lines ad installed them into an Adtran TA850 with an FXO blade, then to the PRI port on the IP Office. I have everything working, incoming calls are fine, outgoing calls are fine as far as setup-teardown. I have outgoing caller ID working fine, incoming calls gives me ?? in PhoneManager everytime.

I tried playing with a bunch of the channel settings, and I am really lost here. I have tried routing digits at 0, 4, and 9.

The reason for this is I am using a Vonage appliance that hands off 2 loop-start lines. A regular 2500 set picks up the CLID with no problem.

I worked wih adtran and they say the bits are being received, but the PBX isn't getting them or it's a timing issue.

Anyone have any idea of some specific settings I can try???

Thanks

koelemon

That is a toughie, there is not much you can do to the IPO to make it NOT handle the caller ID....can you run the line right into the IPO bypassing the Adtran?

__________________
"There are only 10 types of people in the world,
those who can read binary and those that cannot."

PBXtech.info

 

cbennett912

Yes, If I use analog trunk blade, I do get the call ID. There is some setting that will effect it on the T1, it worked a couples time yesterday, then I cleaned up the wiring and it was gone again.

When a call hits that POTS line, then flips from the adtran to T1, it hits the IP403 PRI port immediately. I mean instant, as soon as you call it, it rings the hunt group right away and rings the phones. As we know CLID is passed between rings 1 and 2.

koelemon

Hmm, the only thing I can think of is the Loop Start ICLID setting on the Analog lines...I am curious to see what the resolution is

__________________
"There are only 10 types of people in the world,
those who can read binary and those that cannot."

cbennett912

I confirmed with Adtran that CLID is being received, and passed out it's DSX-1 port. The PRI blade don't see it though. I keep playing with setting, but like I say, I dunno what most of the channel timing setting mean. "Winking" shouldn't have anything to do with this application should it??

koelemon

I may be way off here, but is the Adtran doing some conversion of the ICLID to soomething the PRI can interperet? I only ask because on a PRI you don't really see caller ID it is pretty much ANI, on an analog circuit you should see caller ID like at home, etc.

__________________
"There are only 10 types of people in the world,
those who can read binary and those that cannot."

PBXtech.info

 

Cephas

Check the Adtrans PRI settings - is it set to emulate DMS-100, 5ESS, NI-1, NI-2? Then make sure the IPO is configured the same way. If you have a choice, go for NI-2.

Also, fire up monitor and watch for incoming (Rx) ISDN layer 3 packets, see if you are seeing the inbound callerID information come in.

Finally, I suspect the adtran needs to be told to wait for the callerID to come in between the first and second ring as you suggested - although it's strange that adtran asserts it is getting the CLID.

Peter

cbennett912

Ok, it just doesn't work with incoming caller ID period. The AB bits go out backwards. Incoming call flow, outgowing call flow, and outgoing CLID work perfectly.

Adtran is working on resolving this issue for TA750 and TA850.

I flipped 20 Vonage IP lines, from loopstart to T1 via FXO in the Adtran, passed that to the T1 blade on the IP403.

Ensure to use a T1 crossovercable.

But it works!

Customer went from $6000/month in LD to $1000/month Flat, so loosing CLID wasn't that bad. :)

cbennett912

Also, there is no delay on the T1 blade to port the call to the stations, so it doesn;t wait long enough to collect digits (Like POTS between rings 1 and 2). No timing issues in the IP Office, nor the Adtran unit could resolve it.

From the remote caller dialing number to first ring it is literally instant to the IP Office huntgroup or ext ringing. I mean INSTANT.

Cephas

Hey.... not bad! If I was the customer I think I would be pretty pleased with that deal too!

Peter