Last active 6 months ago
I don't have access to Group Policy for that machine but if FOP is able to run wouldn't that preclude blocking 4445?
I have a similar situation with one brand new Windows 7 Pro 64-Bit Machine. the other slightly older machines on that network are fine, no issues logging in.
After putting in credentials on this machine it attempts to connect over and over again
This is what I did:
[from-internal-custom] ;Chanspy Direct SIP Extension exten => _84377,1,Chanspy(SIP/4377|b)
I don't get any audio...
When I dial that extension(prefixed with "8") I get a "Beep" followed by silence
Is there a way of restricting extenspy to only one extension?
I may be straying off-topic....
I have FOP2 for the Receptionist (55+ extensions) on a Touchscreen Monitor, and she loves it btw.
Now they want to setup a single extension that can be listened to by several other extensions in that unit.
I wanted to try extenspy for that but I dont want to interfere with FOP2, and I dont want to use FOP2 for this task as the unit employees want to just setup a speed dial on their handsets.
Any advice is welcome!