Display says 'incompatible' when calling 2nd switch on SCN 1

[phonesaz]

I have 2 IP Offices installed as first part of 4 system scn deployment. Location one uses 2xx extensions; location 2 uses 3xx. H323 lines are 18 and 19 respectively. Both sites have SCN license. When I call a 2xx number from the 3xx site it takes the number string and then rings fast busy and the display says incompatible.

Unfortunately about the time this happened I knocked the IP Office over (it was on the floor because that was the only way it would connect to the switch) and killed it. So.. I need to put everything in a new chassis, so I am hoping someone has input on the incompatible message so when I go back out tomorrow I will have a head start.

Incidentally... I took the chassis apart at the office to see if perhaps I knocked something loose and I am amazed to report that ALL the internal screws were so loose I could twist them in my fingers and almost all the ones on the casing were as well. Gotta think if they were tighter it still might be working... sigh...

 

[intrigrant]

incompatible" means the number is not recognized so SCN is not working.
Do you have IP routing on order?

A simple mind delivers great solutions

 

[phonesaz]

I have:

H323 trunk on switch 200 with IP address on VoIP tab set to address of switch 300
H323 trunk on switch 300 with IP address on VoIP tab set to address of switch 200
a four-port networking license on each one
3XX, dial, . , line group 18 on switch 200 as a short code
2XX, dial, . , line group 19 on switch 300 as a short code
0.0.0.0 IP routes with the gateway for each switch
IP address in LAN1 tab on each switch
The H323 trunks are line groups 18 and 19 (one on each)

When I was watching the dial string in System Status I was seeing the call reach the H323 trunk and then go nowhere. Then I broke the phone system.

 

[RafaelGrande]

I agree with intrigant, it smells like routing.

Because even if you forgot to select "IP Office SCN" on the Suplementary Services field (VoIP Settings tab), the default for an H323 trunk is to ring an extension if the received digits matches that extension number. (sorry for my bad English)

How does the trunk/channels show on the System Status? Try to use the ping tool on SSA Aplication.

 

[amriddle01]

It's nearly always the network/routing.... if you link 2 systems with a cable and it works for a period then stops, you look at the cable to see what's wrong. In this case the network/routers form the link and now the link has stopped working...where do you look?


Avaya Implementation Qualified Professional Specialist Technical Engineer (AIQPSTE)

 

[tlpeter]

Remove shortcodes for dailing the SCN.
These are not needed in a SCN.
If you need them then you have a problem in your network.


BAZINGA!

I'm not insane, my mother had me tested!

 

[phonesaz]

Thank you everyone. As soon as I get a box to replace the one I dropped I will do some tracing. As an aside it never worked; it is a new install and I broke the processor while testing the second site.

 

[CarGoSki]

It's nearly always the network/routing.... if you link 2 systems with a cable and it works for a period then stops, you look at the cable to see what's wrong. In this case the network/routers form the link and now the link has stopped working...where do you look?

Look at the technician and complain that IPO has been a real bad solution since day one.

 

[amriddle01]

Reading back, I thought he said it was working before....now I see it wasn't, probably isn't the network in this case lol


Avaya Implementation Qualified Professional Specialist Technical Engineer (AIQPSTE)

 

[phonesaz]

Ready to try this again... I thought I needed the short codes if I am using embedded messaging instead of VM Pro?

 

[tlpeter]

Embedded in a SCN is not supported.
And no, you never need shortcodes for a SCN.


BAZINGA!

I'm not insane, my mother had me tested!

 

[phonesaz]

I have implemented (unfortunately I didn't engineer them) sites with embedded voice mail and multiple locations for our LEC, who carries the IP Office and contracts out the installations. In another thread this was discussed and the point was made that its not a huge deal to lose Avaya support since it is a little thin anyway. AND if I choose to go this route I may need short codes. Rather than revisit it here I will find the other thread; I didn't realize that discussion wasn't part of this thread.

 

[tlpeter]

Shortcodes for dailing across a SCN is never needed, not even with embedded voicemail.


BAZINGA!

I'm not insane, my mother had me tested!