We have an Atlas 830 with a PRI coverting to BRI S/Ts for our Polycom VTCs. Everything was working great until we replaced the older Polycoms with the 8000hdx models. Now, no matter what settings we have for the Polycoms or the Adtran, they won't complete an outgoing ISDN call. Calls come in fine up to 512 kbps, but on outgoing calls the polycom will request a setup with the distant end, but won't handshake and connect. It seems like there's some protocol compatibility issue between the Adtran and the Polycom. Any Suggestions?
Of course you want to make sure the ISDN protocol is the same on the ATLAS as on the Polycom (either National ISDN, AT&T 4ESS, DMS-100, etc.).
What is the SPID format in both the ATLAS and the Polycom?
Do you have 2 SPIDs per BRI, or does the ATLAS only have 1 SPID per BRI with 2 call appearances (Calls=2)? If you have 1 SPID per BRI, then I suggest using 2 SPIDs per BRI and changing the Trailing Identifier (TID); because the ATLAS cannot have both SPIDs being the identical. (So if the number is 256-555-1234, you can have SPIDs of 25655512340101 and 25655512340102.) The Polycom will have to be configured with the same SPIDs as are programmed in the ATLAS.
If you have 2 SPIDs per BRI then you'll need to do some logging in the ATLAS in order to see how many channels dial through the ATLAS and how many connect.
Thank you,
Patrick
Of course you want to make sure the ISDN protocol is the same on the ATLAS as on the Polycom (either National ISDN, AT&T 4ESS, DMS-100, etc.).
What is the SPID format in both the ATLAS and the Polycom?
Do you have 2 SPIDs per BRI, or does the ATLAS only have 1 SPID per BRI with 2 call appearances (Calls=2)? If you have 1 SPID per BRI, then I suggest using 2 SPIDs per BRI and changing the Trailing Identifier (TID); because the ATLAS cannot have both SPIDs being the identical. (So if the number is 256-555-1234, you can have SPIDs of 25655512340101 and 25655512340102.) The Polycom will have to be configured with the same SPIDs as are programmed in the ATLAS.
If you have 2 SPIDs per BRI then you'll need to do some logging in the ATLAS in order to see how many channels dial through the ATLAS and how many connect.
Thank you,
Patrick
Thanks for your reply.
Yes, everything is as you have said, 2 SPIDs per BRI, 2 call appearances, different TIDs. Both systems are programmed the same. We also tried each protocol (rebooting after each change) working with the local telco to make sure our protocol matched the way they had the PRIs programmed. Our old Polycom equipment works great, it seems to be the 8000hdx units that have a compatibility issue somewhere. In the Atlas, the call goes out and requests 3 channels, looks like it connects, then drops the call. The other end sees a call request, but won't handshake and drops the call. The telco said it looked like the call completed and they couldn't see any errors.
Verify all the SPIDs register. In the ATLAS you can go under SYSTEM CONFIG and an EVENT LOGGING and set the ISDN EVENTS to INFO. You can then view the events under SYSTEM STATUS in the EVENT LOG.
The end equipment does the Bonding negotiation, so if the Polycom only dials 3 channels, then the ATLAS will only send 3 channels out the PRI. It is up to the Polycom to originate the calls. If all the SPIDs are not registering, then the Polycom may not be dialing because it does not see the channels as available (but this doesn't explain why it will answer all the channels on an inbound call). If all the SPIDs do register and the end devices negotiate 6 channels in the BONDING negotiation, then there is no reason for the Polycom to only dial 3 channels, but the ATLAS cannot force the Polcycom to dial additional channels.
-Patrick
Thank you, Patrick. Your replys helped me to see that my SPIDS were programmed wrong in the Atlas. I reprogrammed them and it works fine now.