Monitoring Calls Across an SCN in 7.0

[Justplainjo]

Here's the scoop.

2 IP Office IP500 V2's. Both are running 7.0(23) with the patch as well. The systems are connected using SCN.

I have a group setup on one of the systems for the managers to monitor calls. When the manager is in the 2nd location, even if he logs into his extension on the first system, he is not able to monitor calls.

Avaya says this is the way it is supposed to be, and that you are not able to listen to calls over an SCN.

Anyone know of any ways to get this to work?

 

[tlpeter]

True but upgrade to 8.0 when it is there:

Supported SCN Features
 

The following features are supported between systems in a Small Community Network. 

Feature
 Description
 Minimum Software Level
 
Extension Dialing
 Each system automatically learns the user extension numbers available on other systems and allows routes calls to those numbers.
 
 
Absence Text
 Calling an SCN user with absence text set will display the absence text. 
 
 
Call Tagging
 Call tag text added to a call is retained by calls routed across the Small Community Network. 
 
 
Anti-tromboning
 Calls routed across the SCN and back to the originating system are turned back into internal calls on the originating system only. 
 
 
Hold
 Hold and held calls are signalled across the SCN. 
 
 
Transfer
 Calls can be transferred to SCN extension numbers.
 
 
Forwarding
 Calls can be forwarded to SCN extension numbers. 
 
 
Paging
 Page calls can be made to SCN extension numbers. 
 
 
Call Pick-Up Extension
 The directed call pickup feature can use SCN extension numbers as its target for the call pickup.
 
 
Callback When Free
 When calling a busy or unanswered extension across the SCN, the callback when free function can be used to set a callback. 
 
 
Conference
 For IP Office Release 8.0+, Meet Me conference IDs are now shared across a Small Community Network. For example, if a conference with the ID 500 is started on one system, anyone else joining conference 500 on any system will join the same conference. Each conference still uses the conference resources of the system on which it was started and is limited by the available conference capacity of that system. 

Previously separate conferences, each with the same conference ID, could be started on each system in a Small Community Network.
 
 
User DSS/BLF
 Monitoring of user status only. The ability to use additional features such as call pickup via a USER button will differ depending on whether the monitored user is local or remote. Indication of new voicemail messages provided by Phone Manager/SoftConsole user speed dial icon is not supported across an SCN. 
 
 
Advertised Hunt Groups
 A hunt group can be set to be 'advertised'. Hunt groups that are advertised can be dialed by users on other systems within the Small Community Network (SCN) without the need for short codes.
 4.0
 
Distributed Hunt Groups
 Hunt groups on a system can include users located on remote systems within the SCN network. A distributed hunt group can only be edited on the system on which they were created. 
 4.0
 
Remote Hot Desking
 Users can hot desk between systems within the network. The system on which the user configured is termed their 'home' system, all other systems are 'remote' systems. 

When a user logs in to a remote system;

· The user's incoming calls are rerouted across the SCN. 

· The user's outgoing calls use the settings of the remote system at which they are logged in. 

· The user's own settings are transferred. However some settings may become unusable or may operate differently. 

· Users settings are transferred but user rights are not. However if user rights with the same name exist on the remote system then they will be used. The same applies for user rights applied by time profiles, if a time profile with the same name also exists on the remote system . 

· Appearance buttons configured for users on the home system will no longer operate. 

· Various other settings may either no longer work or may work differently depending on the configuration of the remote system at which the user has logged in. For example T3 phones, the personal directory is not transferred with the user.  

· If a remote user's home system is no longer visible within the SCN, they are automatically logged out after 24 hours.  
 4.0
 
Break Out Dialing
 This feature allows the user to select a system in the network from a displayed list and then dial a subsequent number as if dialing locally on the select system. This feature is triggered either by a programmable button or short code.
 4.0
 
Music on Hold Source Selection
 The 4 possible music on hold sources are numbered 1 to 4, with 1 being the System Source. Where the source number to associate with a call is changed, that number is retained when the call is rerouted across the SCN. If the receiving switch has a matching numbered alternate source, that source is used. 
 4.2
 
Mobile Call Control
 Licensed mobile call control users who remote hot desk to another system within the SCN take their licensed status with them rather than consuming (if available) a license on the system to which they hot desk. 
 4.2
 
Fallback
 Systems can provide fallback support for Avaya H323 phones, advertised hunt groups and centralized voicemail. 
 5.0
 
Centralized Personal Directory
 If the user hot desks to another system in the Small Community Network, their personal directory is still available. 
 5.0
 
Centralized Call Log
 The centralized call log features include support for users hot desking within a Small Community Network. 

· The user's call log records are stored by the system that is their home system, ie. the one on which they are configured. When the user is logged in on another system, new call log records are sent to the user's home system, but using the time and date on the system where the user is logged in.  

· Hunt group call log records are stored on the system on which the hunt group is configured.  
 5.0
 
Fax Relay
 For an IP500 or IP500 V2 system with an IP500 VCM card, Fax relay can be configured on SIP lines and extensions. Within a Small Community Network, fax calls can transition from a trunk or extension with T38 support to a system SCN line with Fax Transport Support enabled. 
 5.0
 
User Profile Resilience
 When a user hot desks to another switch in the SCN, they retain their Profile settings and rights as validated by the licenses in their home switch's configuration. They do not use a license on the remote switch. This applies even if their home switch is temporarily removed from the SCN. 
 6.0
 
Distributed Voicemail Server Support
 When using Voicemail Pro 6.0 or higher, each system can support its own Voicemail Pro server in addition to the central Voicemail Pro server. The distributed severs can provide call recording and auto attendant functions to their local system. The central Voicemail Pro server is still used as the message store for all messages. For full details refer to the Voicemail Pro Installation Manual.
 6.0
 
[b]Intrusion Features
 Call intrusion features are supported across a Small Community Network. This applies to new intrusion features added in Release 8.0 and to existing intrusion features which were not previously supported across the Small Community Network. 
 8.0[/b]

BAZINGA!

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

 

[nmessick]

hummm... I am trying this right now. Two systems, V8, I can't do the Coaching feature.

 

[nmessick]

I should not need a line group from this right. Just dial coaching and the extension. Since its in the SCN it should know the number.It works fine locally, just not over the SCN.