Non SCN H323 trunking between IPO's

[jeepguy267]

Adding to an existing network of IP office systems, Hub and spoke config.
New switch is 500v2 r9.o.2.o
existing networked IPO's are all 406's 5.0(18)

I don't want to mess with upgrading the entire network so I was looking to do a simple NON-SCN H323/H450 IP trunk and add short codes to dial across between the 500v2R9 and the Hub 406. 500v2 has the voice networking license and trunks all look good in system status. When trying to dial across I get "unobtainable." Im pretty confident in my config and have a message into the router guy to verify off fix ups are off.

My primary question has to do with the disparate releases. Please don't copy paste the docs about 1 major release difference not supported because that says specifically for SCN. If I can build h323 trunks between different vendors, can't I also build h323 trunks between different release IPO's?

Below is a trace and trunk details:

Trunk Information, mainlocation (192.168.10.201)
4/24/2014 2:21:31 PM
-------------------------------------------------------------------------

IP Address: 192.168.0.201
Line Number: 105
Number of Administered Channels: 4
Number of Channels in Use: 0
Administered Compression: G729 A
Small Community Networking: Not Enabled
Direct Media Path: Off
Enable Faststart: Off
Silence Suppression: Off

Channel Call Current Time in Remote Media Codec Connection Caller ID or Other Party Direction Round Trip Receive Receive Packet Transmit Transmit Packet
Number Ref State State Address Type Dialed Digits on Call of Call Delay Jitter Loss Fraction Jitter Loss Fraction
------------------------------------------------------------------------------------------------------------------------------------------------------------------------
1 Idle 03:15:33

2 Idle 03:15:33

3 Idle 03:15:33

4 Idle 03:15:33
===============================================and the trace======================

4/24/14 2:20:54 PM-682ms Extension = 2416, Digit dialed, Digit = 2
4/24/14 2:20:54 PM-689ms Call Ref = 2, Originator State = Dialling, Type = User, Destination Type = none
4/24/14 2:20:54 PM-895ms Extension = 2416, Digit dialed, Digit = 1
4/24/14 2:20:55 PM-358ms Extension = 2416, Digit dialed, Digit = 9
4/24/14 2:20:55 PM-695ms Extension = 2416, Digit dialed, Digit = 2
4/24/14 2:20:55 PM-696ms Call Ref = 2, Short Code Matched = System, 21xx
4/24/14 2:20:55 PM-698ms My buttons = 1, Call Ref = 2, Originator State = Dialling, Type = User, Destination State = Seized, Type = Target List
4/24/14 2:20:55 PM-705ms Line = 105, Channel = 1, Line Ref = 1008, Q.931 Message = Setup, Call Ref = 2, Direction = From Switch, Calling Party Number = 2416, Called Party Number = 2192
4/24/14 2:20:55 PM-708ms My buttons = 1, Call Ref = 2, Originator State = Dialling, Type = User, Destination State = Clearing, Type = Trunk
4/24/14 2:20:55 PM-708ms Call Ref = 2, Disconnect from Destination End
4/24/14 2:20:55 PM-712ms Extension = 2416, State = Busy
4/24/14 2:20:55 PM-712ms Extension = 2416, Button = 1, Idle
4/24/14 2:20:59 PM-269ms Extension = 2416, Switchhook, Status = On
4/24/14 2:20:59 PM-270ms Extension = 2416, State = Busy Wrap Up
4/24/14 2:21:01 PM-270ms Extension = 2416, State = Idle

 

[AACon]

make sure shortcodes are good? wanna upload the configs? but yes, make sure the h323 garbage is off between routers. That always messes it up.

-Austin
ACE: Implement IP Office

 

[Bas1234]

Checked the ip routes in both units?

___________________________________________
It works! Now if only I could remember what I did...

Dain Bramaged (Avaya Search tool

http://tinyurl.com/bas1234

)
______________________________________

 

[jeepguy267]

SC
21xx
Dial
21N
Line 105 (my ip trunk)

extension are 21xx at the far end 24xx at the near end, relative to local short code

====
IP routes are good.
====

Do you expect an r5 and an r9 to talk and so I should keep plugging away at troubleshooting, or this will never work and I am chasing my tail?

 

[AACon]

It says Line 105, but is that your outgoing group id of the line as well? Line ID and Group ID are different beasts.

-Austin
ACE: Implement IP Office

 

[Bas1234]

Try a code like 2192/dial/2192/105 and try to call an analog extension.

___________________________________________
It works! Now if only I could remember what I did...

Dain Bramaged (Avaya Search tool

http://tinyurl.com/bas1234

)
______________________________________

 

[jeepguy267]

both are 105 at both ends, nice to make them match

I have other networks I am referencing and I have an entry in the TIE field for one location. Have no idea why I would have changed that. It's been a long time since building that one

 

[AACon]

run a monitor trace

-Austin
ACE: Implement IP Office

 

[IPGuru]

There is no reason why you cannot use a plain h323 trunk in this way

Rule one of VoIP issues: it IS the data network.

prove your system is transmitting the data & dump it in the lap of the data guy.




A Maintenance contract is essential, not a Luxury.
Do things on the cheap & it will cost you dear

 

[jeepguy267]

Thank you IPGuru for answering my question. I will post resolution after arm wrestling with IT

 

[jeepguy267]

follow up as promised. IT "did their thing" on the switches and everything came up. No changes to my config

 

[hairlessupportmonkey]

got voice networking licences on the rel 9 switch? Even though you arent using SCN features, you will still need these licences on later switches.

ACSS - SME
General Geek

 

[amriddle01]

It's working Sean

 

[hairlessupportmonkey]

That will teach me for posting at 5.30 am

ACSS - SME
General Geek

 

[IPGuru]

Voip faultfinding guide

1) does it Work?
Yes - Leavi things alone & go home ;-)
No - pass to data guys to check network config

2) go back to step 1



A Maintenance contract is essential, not a Luxury.
Do things on the cheap & it will cost you dear