Re: CTI Integration

Hey,
[email protected] wrote: 
> On Mar 28, 2007, at 13:55, Adam Tauno Williams wrote:
> > But I'll buy into your part about home users,  although I still  
> > suspect
> > they constitute sub-1% of the work force using a PBX or PBX-like.  But
> > even in that case [connected over a true broadband VPN] you will have
> > the ability to resolve the device name (DNS/WINS).  Very little of the
> > technology of a modern WAN/LAN works well at all without DNS/WINS,
> > including Kerberos and CIFS.
> 
> I think Sebastian is quite focused on the setup in his company, which  
> obviously is quite forward thinking ;-)
> 
> So maybe we should stop discussing the general PBX world ;-) The  
> suggestion made by Sebastian is still valid, using the logged in  
> account instead of the client machine IP to lookup the required  
> endpoint for callouts is a very useful addition.
> I think in practice both methods are required depending on the setup.
> 
Ok, got it, I'll add a Default, so that the Admin can decide, how it should 
work, take a look at the IP of the clients, or take a look at something 
related to the users accout information, most likely a telephone number ;)


> So if the IP=>phone default is set, the dialer should use it. If it  
> isn't or if the IP could not be found, a dialer should scan the  
> telephones of the login account for numbers which are managed by the  
> PBX associated with it.
Yes, If that IP=>phone default is set, it should be used as a fallback, I 
can do it this way.

> 
> As mentioned I do *not* understand why a different phone number type  
> is required. The dialer should know which numbers it can dial. So it  
> just needs to iterate over the available numbers and pick the first  
> which is associated with the dialer. Eg by checking for some prefix.
or suffix, e.g. sip phone numbers usually look like this:

[email protected]
nevertheless, so I should make it configurable whether to match a prefix or 
suffix... 

kind regards
Sebastian

-- 
OpenGroupware.org Discussion [email protected]
http://mail.opengroupware.org/mailman/listinfo/discuss