How do I see both systems in manager in an SCN environment? 4

[datadump]

In manager, how do I setup the ability to see my remote site extensions and my main site extensions at the same time? When looking at the H323 line in system status on both ends it shows SCN is up and I can make and receive and transfer calls in both directions so I assume I am configured correctly. However, I cannot point a DID from the main site to my remote site because the remote site extensions do not list up? Anyone know what I'm missing here? Thanks in advance. Also, I can log into the remote site using the manager from the main site because both sites list up when initially opening manager using the 255.255.255.255 broadcast. But I can only view one at a time and I need both sites to learn each other's extensions.

 

[amriddle01]

They don't list, you need to type them in


Avaya Implementation Qualified Professional Specialist Technical Engineer (AIQPSTE)

 

[tlpeter]

Go to File -> preferences ->discovery -> IP search criteria and enter both system IP address in it.
Put a ; in between to seperate them.
Now they will both show up when you leave the Unit/broadcast address to 255.255.255.255


BAZINGA!

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

 

[hairlessupportmonkey]

Follow the details in this link:

http://marketingtools.avaya.com/kno...jects/manager/scn_service_user_management.htm

ACSS - SME
General Geek

 

[hairlessupportmonkey]

start here:

http://marketingtools.avaya.com/kno...ice/mergedProjects/manager/scn_management.htm

ACSS - SME
General Geek

 

[teletechman]

8.1 you can check in preferences/discovery the SCN discovery tab. This will show all unit that are able to be reached via a broadcast address 255.255.255.255. Then it shows new info in the manager program. But amriddle is correct you have to type them in manually, just did this 10 minutes ago.
Mike
Mike

 

[amriddle01]

He/she has said they can already can see both systems in the broadcast window. He/she wants to actually see both systems users, extns, groups etc in the programming once opened in Manager as he/she assumes that's how the systems learn about each others extensions in an SCN. Obviously this is not the case.

datadump, as mentioned the system never shows users in the destinations drop down in ICR (nice if it did) they need to be typed in manually


Avaya Implementation Qualified Professional Specialist Technical Engineer (AIQPSTE)

 

[Wallysworld]

@ hairlessupportmonkey;

What is that link and why doesn't it look the same as when you go into the "normal" IPO knowledgebase?

 

[datadump]

Thank you all for your responses. I think what I have is some kind of directory issue. When looking at system status I noticed an error under Resources: Directory: HTTP
It shows "invalid response" . However, if I look at the same thing on the remote side it shows "success". The configurations look the same however so I'm not surre what piece of the puzzle I am missing. However, I do know that the "users" for the remote site used to show up in the pane when looking in manager on the Main site. Now I just realized that if I just type the exension number in, I can still route the DIDs over to the remote site. So calls are routing correctly. Just not appearing in manager correctly.

 

[hairlessupportmonkey]

thats the direct link to the KB article covering SCN management.



ACSS - SME
General Geek

 

[amriddle01]

I am having invisible post syndrome again, hate that IPS


Avaya Implementation Qualified Professional Specialist Technical Engineer (AIQPSTE)

 

[teletechman]

With SCN discovery checked in 8.1 you will have all systems in one manager, no need to open more than one manager, listed as different systems with the users, HGs, time profiles and user rights in an SCN tab so you can see all users or HGs or time profiles or user rights across the SCN at once.
Mike

 

[amriddle01]

But not Incoming call routes etc


Avaya Implementation Qualified Professional Specialist Technical Engineer (AIQPSTE)

 

[teletechman]

No but you can open both systems at the same time.