Timing Loss on IPO

[quazimotto]

I have a Merlin Magix connected to an IPO via PRI. The Magix's PRI is set to b8zs,esf and Merlin PBX. The IPO is set to b8zs, esf and 5ESS as per an Avaya Tech Tip. Here is my problem: The IPO keeps lossing its timing source and the trunks between the systems do not work after a period of time. Any suggestions?

Thanx/Quaz

 

[ThePhoneMn]

Do you have any other PRI's in either system? If yes, then in the IPO, only one PRI can be set to Network, the others will be Fallback. If no, then only one of the two systems can provide timing for the circuit, so if the Magix is the Primary, then the PRI on the IPO should be set to Network. The IPO set to Network will receive timing from the Magix.

 

[sheldoom]

Did you set Provider field to AT&T? With 5ESS as switch type Merlin/Legend only supports AT&T Custom as protocol.

 

[quazimotto]

Guys,

I have the Magix set to local timing and the IPO to network. The provider field on the IPO is AT+T, 5ESS switch type. The Magix switch type is Merlin PBX. It is still not right. When I dial 9 on the IPO to get a trunk on the Magix I usually get waiting-for-line message on the IPO telephone. Any suggestions?

Quaz

 

[quazimotto]

Fellas,

I am still having problems, so I went over my settings and the Avaya Tech Tip 134.pdf which is about this subject. On page 3 of 3, it states:


IP Office Requirements
• Voice networking should NOT be checked
• PRI should be set for AT&T, 5ESS, ESF, B8ZS, CPE or 5ESS local
• Must program short code to dial Magix extensions:

I don't know what the first item is referring to. Does anyone know where the Voice Networking box is that should not be checked?? I see it in my H.323 trunks. I appreciate any help you can give me.

Thanx/Quaz

 

[CarGoSki]

I don't suppose that the T1 card in the Magix is the first trunk card in the system?

Are you set to CO or CPE in the IPO?

Voice Networking is for IP Trunks.

 

[quazimotto]

I have it set to CPE and the T-1 card is not the first trunk card.

Quaz

 

[CarGoSki]

I would set the IPO to CO and set the Magix to loop. One has to be the central office.

 

[CarGoSki]

I would also turn the Magix T1 csu on, if it is a DCD.

 

[quazimotto]

CarGoSki,

I am not using a CSU; just wiring reversal. When I set the IPO to CO I cannot do anything. I believe that CPE is the correct setting. What happens is that after a reboot the link will work for 3 maybe 4 calls; then it gets hosed-up. I can direct acces the trunks from the Magix and they will always come up and give me a dial tone. If I direct trunk access the T-1 from the IPO side, I get dial tone everytime until I make a few calls from the IPO, then it shuts down and no calls will pass. I have the system set according to Tech Tip 134.pdf. Any ideas?

Quaz

 

[WANLord1]

Quazi... What do the Transient and or Permanant errors read in the Magix? Give me the codes in the logs. I'm not thinking timing is the issue here...I need more info.

Lord

 

[WANLord1]

Explain your buid-out on both sides. Circuits connected, how many, you get the jest! Be back soon, gotta go look up some recipes.

Lord

 

[Notsetinstone]

Do you have an external csu or csu's? Are they set to look for clock in the correct place?

http://www.nu-tel.com

 

[quazimotto]

My build out is stated at the top. I have traced 2 calls after the IPO was rebooted. The first call was completed to extension 3615 across the PRI link and disconnects normally when I hang-up. The second call attempts sieze trunk 2 of the PRI on the IPO, but it is never completed. DO you know what code 16 and code 31 are? Here is the trace.

12/22/08 9:13:35 PM-333ms Line = 5, Seized, Channel ID = 1, Call Ref = 3
12/22/08 9:13:35 PM-343ms Line = 5, Channel = 1, Q.931 Message = Setup, Call Ref = 3, Direction = From Switch, Calling Party Number = 4415, Called Party Number = 3615
12/22/08 9:13:35 PM-371ms Line = 5, Channel = 1, Q.931 Message = CallProceeding, Call Ref = 3, Direction = To Switch
12/22/08 9:13:35 PM-376ms Call Ref = 3, Originator State = Dialling, Type = User, Destination State = Dialling, Type = Trunk
12/22/08 9:13:35 PM-391ms Line = 5, Channel = 1, Q.931 Message = Alerting, Call Ref = 3, Direction = To Switch
12/22/08 9:13:35 PM-394ms Call Ref = 3, Alerting, Line = 5, Channel = 1
12/22/08 9:13:35 PM-396ms Call Ref = 3, Originator State = Ringback, Type = User, Destination State = Outgoing Alerting, Type = Trunk
12/22/08 9:13:50 PM-945ms Line = 5, Channel = 1, Q.931 Message = Connect, Call Ref = 3, Direction = To Switch
12/22/08 9:13:50 PM-956ms Call Ref = 3, Originator State = Connected, Type = User, Destination State = Connected, Type = Trunk
12/22/08 9:13:50 PM-956ms Call Ref = 3, Answered, Line = 5, Channel = 1
12/22/08 9:13:58 PM-850ms Extension = 4415, Switchhook, Status = On
12/22/08 9:13:58 PM-852ms Call Ref = 3, Originator State = Clearing, Type = User, Destination State = Connected, Type = Trunk
12/22/08 9:13:58 PM-852ms Call Ref = 3, Disconnect from Originator End
12/22/08 9:13:58 PM-881ms Line = 5, Channel = 1, Q.931 Message = Disconnect, Direction = From Switch, Cause Code = 16
12/22/08 9:13:58 PM-928ms Line = 5, Channel = 1, Q.931 Message = Release, Direction = To Switch
12/22/08 9:13:58 PM-929ms Line = 5, Channel = 1, Q.931 Message = ReleaseComplete, Direction = From Switch
12/22/08 9:13:58 PM-932ms Line = 5, Idle, Channel ID = 1
12/22/08 9:14:08 PM-873ms Call Ref = 4, Originator State = Dialling, Type = User, Destination State = Seized, Type = Target List
12/22/08 9:14:08 PM-873ms Call Ref = 4, Short Code Matched = System, 3xxx
12/22/08 9:14:08 PM-885ms Line = 5, Seized, Channel ID = 1, Call Ref = 4
12/22/08 9:14:08 PM-895ms Line = 5, Channel = 1, Q.931 Message = Setup, Call Ref = 4, Direction = From Switch, Calling Party Number = 4415, Called Party Number = 3615
12/22/08 9:14:16 PM-895ms Line = 5, Channel = 1, Q.931 Message = ReleaseComplete, Call Ref = 4, Direction = From Switch, Cause Code = 31
12/22/08 9:14:16 PM-901ms Call Ref = 4, Originator State = Dialling, Type = User, Destination State = Clearing, Type = Trunk
12/22/08 9:14:16 PM-901ms Call Ref = 4, Disconnect from Destination End
12/22/08 9:14:16 PM-922ms Line = 5, Idle, Channel ID = 1


I cleared the Magix error logs earlier today. I am thinking I might have a bad PRI card in the IPO. What do you guys think?

Quaz