SalesForce and Click to Dial

[shawny78]

Hello All,

Been beating my brains out over this for the last little while. Hoping to get some help or something to point me in the right direction.

I've setup the salesforce desktop integration downloaded from the ONE-X-PORTAL page. Installed it fine. Log into SalesForce and can log into the softphone fine. When I see calls I get the CLID showing up, screen pops all work fine. When I click on a number to dial it will automatically append the 9 for the system prefix (not a problem). But then it adds the 1 (or whatever I change it to) for long distance. This is great and works fine for long distance calls, but messes things up for local (obviously). If I remove the long distance prefix then the reverse is true (local works, no LD). Can someone point me in the right direction on where to fix this?

Thank you all,

 

[Westi]

I think this is a salesforce anomaly because I remember integrating click to dial about 2 years ago with salesforce.com special integration and they couls either dial everything LD or local but not separate.
We had to build shortcodes to change the dialout for all local exchanges to dial without the 1 and leave all LD exchanges the way they were. Took a few hours of programming and a lot of bad language in the process
If you have SIP trunks then you can hope that your provider takes it any way you dial (like mine) and you can just leave it or get some SIP trunks and append an 8 instead of 9 and use the SIP trunks and only if they are all used to go to the regular trunks and hope that LD or local is picked correctly.

Sorry I hate to be the bearer of bad news and maybe there is a setting now but that was the solution 2 years ago.

Joe W.

FHandw, ACSS (SME), ACIS (SME)

http://convergednetworks.ca

Give a tech a solution and he will be back tomorrow to ask you the next question, teach a tech how to read the manual and he will be able to solve the problems for a life time.

 

[shawny78]

Oh crud, we are lucky enough to have a split area code here. Our 905's are both LD and Local. Just to make it fun, they are using a PRI that isn't going to let it go. That is rather unfortunate, but thank you for the information. It certainly seems to be reinforcing what I'm finding.

 

[Westi]

905 huh?
same area code I have so you get really lucky as of March 25th you get a third area code overlapping added to 905 and 289 and Toronto alse gets a third area code added. I feel for you and I really know what you are going through.
I am in Burlington (905) and I think you will need to get the exchanges programmed to solve it.
Sorry neighbour

Joe W.

FHandw, ACSS (SME), ACIS (SME)

http://convergednetworks.ca

Give a tech a solution and he will be back tomorrow to ask you the next question, teach a tech how to read the manual and he will be able to solve the problems for a life time.