Shoretel Softphone Issue
I am 90% sure it was working and belive this is a director issue.. However:
Tested over a VPN and also locally on the LAN and get a line not in service error on the communicator.
Check HQ/Director and foudn that the SG90 @ HQ site is showing the softphone as out of service and is assigned to a MAC address of a device i cant trak (assyume a laptop):
D4-BE-D9-23-A1-EC Headquarters D4-BE-D9-23-A1-EC 172.19.105.163 Unknown Out of Service (Operational) Soft Phone
Ideas?
Tested over a VPN and also locally on the LAN and get a line not in service error on the communicator.
Check HQ/Director and foudn that the SG90 @ HQ site is showing the softphone as out of service and is assigned to a MAC address of a device i cant trak (assyume a laptop):
D4-BE-D9-23-A1-EC Headquarters D4-BE-D9-23-A1-EC 172.19.105.163 Unknown Out of Service (Operational) Soft Phone
Ideas?
SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
the other issue (linked to this) is that some phones are assigning themselves to a remote switch in another site...
SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
No, we only have 2x scopes/servers at outr main site. the remote site has statics..
ASKER
update: would appear that the machine switching between the networks are not updating the ip address quickly enough for DNS and shoretel system to see the machine with the single IP/Name.
Also the device is automatically assigning to the shoregear switch in our remote site not the main site where director is. The comms co says this is correct due to the way in which resilience/failover is configured...
Also the device is automatically assigning to the shoregear switch in our remote site not the main site where director is. The comms co says this is correct due to the way in which resilience/failover is configured...
ASKER
in the end a couple of issues:
1. resources on the live switch we're maxed out, so we have brought the failover switch live and now new devices are registering to the new switch.
2. the ingate sbc was not allowing traffic and ringtone through it. required additional ip ranges to be added to it.
1. resources on the live switch we're maxed out, so we have brought the failover switch live and now new devices are registering to the new switch.
2. the ingate sbc was not allowing traffic and ringtone through it. required additional ip ranges to be added to it.
ASKER