 09-11-2006, 10:13 AM | #1 (permalink) | ||||||||
| Junior Member 
Location: Mass Rep Power: 7  Country:  |  2nd PRI T1 tie problem Hey All, We have a Norstar MICS 6.1 with 2 PRI T1's. The first one is dialtone to the carrier and the second is a tie trunk to an Astrisk IP PBX. The setup works great with one little snag. We have a phone on the Norstar that had a DID assigned to it. This phone is forwarded to go out over the tie T1 to the Astrisk system. For some reason the Norstar seems to be using the D channel when it forwards. Whenever we call the first call gets a busy signal and any others get right threw. We can't seem to find a work around for this issue. Anybody got any suggestions? TIA, Rob | ||||||||
 |   |
| 09-12-2006, 09:59 AM | #2 (permalink) | ||||||||
| Junior Member  Shooter has no status.
Location: Lake Elmo, Mn Rep Power: 7 Country: | Have you tried routing the call using services? There can be no target line, extension or mailbox on the nortel that matches the DID. Program a route to use the proper PRI. Use the destination code as your DID to point to the proper route. | ||||||||
| | |
| 09-19-2006, 05:24 PM | #7 (permalink) | ||||||||
| Junior Member  gogoGophers is wishing he either didn\'t like pro football or was not a Lions fan
Location: Meechigan Rep Power: 5 Gender:  Country: | This is fairly interesting - Questions Why do you say you think it's using the D channel What exactly were you doing when you were forwarding it, What exactly were you doing when you used routing service. If you don't have time or the will to pursue this, I understand. | ||||||||
| | |
| 09-20-2006, 10:14 AM | #8 (permalink) | ||||||||
| Junior Member
Location: Mass Rep Power: 7 Country: | When we made calls to the DID the first call went to a busy signal but any more that we could get in before the first one hung up would go threw. We were using 3 phones and were able to repeat this and acurately know which phone was going to get the busy. We have a phone with a DID target line assigned to it. That line is forwarded from that phone to 49999999. The 4 is a route built to access the second PRI. I think all the 9's were stripped off so it was just getting trunk access over to the other system. When it worked the caller got the AA of the Astrixs system. We are testing if changing the T1 to non-PRI will let all the calls go threw and not just the 2nd and on. The down side is we will lose CID if this does work. | ||||||||
| | |
| 09-20-2006, 03:43 PM | #10 (permalink) | ||||||||
| Junior Member
Location: Mass Rep Power: 7 Country: | Now it works. We went to a T1 and them back to PRI. The customer went threw all his settings and reconfirmed them all. We had the route built with PRI B, so we just pointed back to that. The one change I made was Asending to decending. One of them made it work. like it should have. WOOHOO!! | ||||||||
| | |
 |
| Currently Active Users Viewing This Thread: 1 (0 members and 1 guests) | |
| Thread Tools | |
| Display Modes | |
| |
 Similar Threads | ||||
| Thread | Thread Starter | Forum | Replies | Last Post |
| NNC Alarm in TIE PRI | justzikle | Meridian Systems | 2 | 08-05-2006 04:31 AM |
| Strange Problem with a T1 isdn with SBC | yuvami | Meridian Systems | 2 | 04-29-2006 02:51 PM |
| How can I change Interface type? | nlhtech | Meridian Systems | 3 | 04-09-2006 11:06 AM |
| Really Strange MICS/AA/Voice Mail problem | lgherb | BCM and Norstar | 5 | 04-06-2006 09:30 AM |
. Anyone else have any suggestions to try?
Linear Mode
