Have spent a couple days trying to set up a tie line between a Meridian and my G3R. I have set up paraneters as:
ESF
B8ZS
Robbed-Bit(apparently no equivalent for this field exists in Nortel side.)
svery time I release my trunks I see all sorts of traffic like it is sending or searching for signal, they then busy, and finally disconnect.
Tech on far side stated that he was seeing all 1's and I explained that the idle code for Definity was to send 1's...
He stated it should be zero because that was the idle code for his switch; at which point I changed setting on idle code to 0's..
Trunks reacted same way however; some busy, then disconnect, while some stayed in idle. When he used a dac from his side he was able to reach my switch and dial extensions on my end....
Funny thing is he came across a trunk that was listed as disconnected when I went to the status trunk group screen.
when I dial my TAC to get across the span, I get a second dial tone which makes me think I'm on his switch, though he states that he sees no activity, but if I dial any digits subsequent to this secondary dial tone I get nothing, followed by busy tone after what would seem to be some swort of time out.
I've tried playing with different settings but i end up with the same progression of trunks going to MA/Busy, followed by disconnection.
I get the impression that it is a signaling mismatch of some kind but I'm running out of time to play with it as the site is coming on board next week.
Any ideas? I looked through previous trails and found little or no references.
ESF
B8ZS
Robbed-Bit(apparently no equivalent for this field exists in Nortel side.)
svery time I release my trunks I see all sorts of traffic like it is sending or searching for signal, they then busy, and finally disconnect.
Tech on far side stated that he was seeing all 1's and I explained that the idle code for Definity was to send 1's...
He stated it should be zero because that was the idle code for his switch; at which point I changed setting on idle code to 0's..
Trunks reacted same way however; some busy, then disconnect, while some stayed in idle. When he used a dac from his side he was able to reach my switch and dial extensions on my end....
Funny thing is he came across a trunk that was listed as disconnected when I went to the status trunk group screen.
when I dial my TAC to get across the span, I get a second dial tone which makes me think I'm on his switch, though he states that he sees no activity, but if I dial any digits subsequent to this secondary dial tone I get nothing, followed by busy tone after what would seem to be some swort of time out.
I've tried playing with different settings but i end up with the same progression of trunks going to MA/Busy, followed by disconnection.
I get the impression that it is a signaling mismatch of some kind but I'm running out of time to play with it as the site is coming on board next week.
Any ideas? I looked through previous trails and found little or no references.