- Joined
- Jun 29, 2009
- Messages
- 25
- Reaction score
- 0
So I was hoping that this issue would be fixed with version 9 and the new Call Assistant, but the issue is still there.
If I use the calling feature from a contact in Outlook 2007 and dial a number my default local area code (305), the system calls my extension, I pick up, and the call completes to the destination.
If I dial a contact number with any area code outside my default local area code (such as 786, 954, etc), the system calls my extension, but when I pick up, I hear "Call Transfer Failed".
When I look at the logs, I see that the TAPI driver is passing a "%20" in front of the number, so 3CX is not recognizing this and not able to complete the call. I looked up "%20" and this is actually the code for a space. See logs below:
23:35:54.948 [CM503008]: Call(1): Call is terminated
23:35:51.948 [CM503016]: Call(1): Attempt to reach <sip:%[email protected]:5060> failed. Reason: Not Found
23:35:51.948 [CM503014]: Call(1): No known route to target: <sip:%[email protected]:5060>
23:35:51.948 [CM503010]: Making route(s) to <sip:%[email protected]:5060>
23:35:50.495 [CM503007]: Call(1): Device joined: sip:[email protected]:48089;rinstance=7260d41e20e038d5
23:35:50.495 [CM503007]: Call(1): Device joined: sip:[email protected]:40600;rinstance=1a39928792d53e4b
Why is the TAPI driver passing this to 3CX and how can I fix it?
:roll:
I tried multiple contacts in Outlook with various contact numbers and they all react the same. I have also tried this on different computers: XP, Vista, and Windows 7 and I have the same issue. There is NOT a space in the contact for Outlook and I've gone through my settings over and over to make sure everything is configured correctly.
The only I was able to work around the issue on version 8 was to use the Terminal Services version of the 3CX Call Assistant. Unfortunately, one does not exist yet for version 9.
Support had acknowledged it was a "known issue" and that they were working on a fix, but now they seem to have forgotten all about it and are asking me to send them logs and info all over again... PLEASE HELP!
If I use the calling feature from a contact in Outlook 2007 and dial a number my default local area code (305), the system calls my extension, I pick up, and the call completes to the destination.
If I dial a contact number with any area code outside my default local area code (such as 786, 954, etc), the system calls my extension, but when I pick up, I hear "Call Transfer Failed".
When I look at the logs, I see that the TAPI driver is passing a "%20" in front of the number, so 3CX is not recognizing this and not able to complete the call. I looked up "%20" and this is actually the code for a space. See logs below:
23:35:54.948 [CM503008]: Call(1): Call is terminated
23:35:51.948 [CM503016]: Call(1): Attempt to reach <sip:%[email protected]:5060> failed. Reason: Not Found
23:35:51.948 [CM503014]: Call(1): No known route to target: <sip:%[email protected]:5060>
23:35:51.948 [CM503010]: Making route(s) to <sip:%[email protected]:5060>
23:35:50.495 [CM503007]: Call(1): Device joined: sip:[email protected]:48089;rinstance=7260d41e20e038d5
23:35:50.495 [CM503007]: Call(1): Device joined: sip:[email protected]:40600;rinstance=1a39928792d53e4b
Why is the TAPI driver passing this to 3CX and how can I fix it?
:roll:
I tried multiple contacts in Outlook with various contact numbers and they all react the same. I have also tried this on different computers: XP, Vista, and Windows 7 and I have the same issue. There is NOT a space in the contact for Outlook and I've gone through my settings over and over to make sure everything is configured correctly.
The only I was able to work around the issue on version 8 was to use the Terminal Services version of the 3CX Call Assistant. Unfortunately, one does not exist yet for version 9.
Support had acknowledged it was a "known issue" and that they were working on a fix, but now they seem to have forgotten all about it and are asking me to send them logs and info all over again... PLEASE HELP!