If the Cisco phone is being used a remote station, connected to and provisioned by Call Manager, then when a call is placed from the phone it will not use PureConnect or its dial plan. It will instead dial directly through Call Manager. I suspect this is the case.
Is the above scenario, you do need to test the dial string used when dialing from iDesktop using dial plan's
simulate call. this should reveal the issue. The SIPEngine log will also record the actual dial string used to place the call.
------------------------------
Chris Mayo
Director, Technical Services
Altivon
------------------------------
Original Message:
Sent: 05-09-2019 17:41
From: Elyse Gritsonis
Subject: Busy Signal through Interaction Connect
Hi Paul,
The Cisco phone is being used as a station.
------------------------------
Elyse Gritsonis
Johnson Financial Group
Original Message:
Sent: 05-08-2019 12:01
From: Paul Simpson
Subject: Busy Signal through Interaction Connect
Is the Cisco phone connected to IC and being used as a Station, or is it independant?
If it's independant, then it may well be worth putting the number into "Simulate Call" in the Dial Plan to see if it's being manipulated in some way by IC / being sent to a Line that has issues / whatever. There isn't much point in doing this if the phone is used as an IC Station, since it would be using the same DIal Plan...
------------------------------
Paul Simpson
Senior Technical Instructor
Original Message:
Sent: 05-07-2019 13:33
From: Elyse Gritsonis
Subject: Busy Signal through Interaction Connect
Looking for help. I am currently having an issue where if I dial a number directly from my Cisco phone the number works. If I dial through using Interaction Connect, I get a busy signal. I looked to see if there was a dial plan issue and there seems to not be one unless it's user error. :(
#Telephony
------------------------------
Elyse Gritsonis
Johnson Financial Group
------------------------------