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!

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

Search results for query: *

  1. doubletalk

    Hicom 300e (9006) PRI T1 configuration issue

    It appears that the double ring is a system-wide setting for all trunks, unfortunately. We need to leave it as it is so that outside calls can be easily identified. I'm still working on getting the Hicom to pass Caller ID/ANI over the PRI. Is that possibly a COT setting?
  2. doubletalk

    Hicom 300e (9006) PRI T1 configuration issue

    Well, keyset6 wins this round! We changed SRTIDX 1 from MCI8 to NONE, and now, incoming calls can be made. We still have a couple of issues, but least we can make calls. Thanks! The incoming call is a double ring, like it is an outside call. Maybe we need to somehow change the type of line. The...
  3. doubletalk

    Hicom 300e (9006) PRI T1 configuration issue

    Just for comparison. Trunk +------------------------------------------------------------------------------+ | TGRP NUMBER : 60 TGRP NAME : PRI TO SERVER /N MAXIMUM NO: 24 | | SUBGROUP NUMBER: 11 DEVICE TYPE: PRI B DIR TYPE : BOTH | | ACD THRESHOLD : *...
  4. doubletalk

    Hicom 300e (9006) PRI T1 configuration issue

    donb01, I compared your configuration to ours, and it looks pretty much the same, making allowances for variation (e.g., we use NI2 for the protocol). How are your COT/COP 2 defined? We are using the following. | | | | | | | | S E A | | | | | | T...
  5. doubletalk

    Hicom 300e (9006) PRI T1 configuration issue

    keyset6, it sounds like you are thinking of the SRTIDX - the service rule table index for DID translation for PRI B trunks. The SRTIDX in our PRI B entries is 1. This is what the SRT table shows. DISPLAY-DIDCR:SRT,; H500: AMO DIDCR STARTED PRI DID SERVICE RULE TABLE 1 NETWORK-SERVICE...
  6. doubletalk

    Hicom 300e (9006) PRI T1 configuration issue

    Our arrangement here is a little more complex than I first described. In additional to the VoIP server, we have a HiPath 4000 talking CORNet to the Hicom 300e over two T1's, but I don't think it's part of this issue. The VoIP server PRI is configured the same on both ends. We are using NI2...
  7. doubletalk

    Hicom 300e (9006) PRI T1 configuration issue

    The 72xx extensions are working fine. They have been there for ages. Nothing has changed with their routing as far as I know. I know that they don't get routed to the VoIP server, because debugging on the VoIP server doesn't show such calls coming in. Internal calls on the Hicom (e.g., from...
  8. doubletalk

    Hicom 300e (9006) PRI T1 configuration issue

    Thank you, donb01, for the response. The extension should be 4 digits in both directions. We have already tested sending 6 digits and 10 digits from the VoIP server. In all cases, the switchboard display shows both the caller and called extensions, such as "7100->7200 no connection possible"...
  9. doubletalk

    Hicom 300e (9006) PRI T1 configuration issue

    Details 1. Digium Wildcard TE110P PRI T1 card in a VoIP server 2. VoIP server configured as user end (USER or cpe) 3. TMDN64P (Q2484-X) PRI T1 card in a Hicom 300e (9006) 6.5 4. Hicom configured as network end (NETWK) and clock source 5. 1-23B/24D PRI T1 channels work fine (NI2, ESF, 8BZS) 6...

Part and Inventory Search

Back
Top