Hi, I don't know if or how much of a difference this would make but I am using version 4.0.0-015321
Is it possible that something here was changed between versions? I see you have version 3.10.3-014144. I have done some basic checks and the extension from the queue (i.e. in the example 9000) is coming through to the Agent rather than the external Caller ID. Cheers, Grant ________________________________ From: Paweł Pierścionek [[email protected]] Sent: Saturday, 2 May 2009 8:34 p.m. To: Grant Lang Cc: [email protected] Subject: Re: [sipx-users] ACD Caller ID Question On 2009-05-02, at 05:35, Grant Lang wrote: Hi, I don't know if you can do this in the setup but one of the 'normal' requirements when dealing with a Call Centre is to have the calls hit the Queue and then screen pop a record, for example from a database, on the Agents Screen. When I have been looking at this the Caller ID that comes through to the Agent is that of the Queue, so for example if you have a line setup with the extension 9000 and that related to a Gateway or such like coming in then the number that comes through as the Caller ID is the extension, in this example 9000. Is it possible to pass through the original Caller ID so this can be matched and perform a Screen Pop? Having looked at the SIP signaling I must say that the original caller id is where it should be and is passed transparently: ##################### U 10.12.0.5:5060 -> 10.12.255.254:5060 INVITE sip:[email protected] SIP/2.0. [...] From: PSTN CALL<sip:[email protected]:5060>;tag=2c1221214076. To: "pawel_q1"<sip:[email protected];sipx-noroute=VoiceMail>. [...] User-Agent: sipXacd (3.10.3-014144) (Linux). From: contains original calling number and display name. To: contains the queue name as dsplay name and agent username as user part. Pawel,
_______________________________________________ sipx-users mailing list [email protected] List Archive: http://list.sipfoundry.org/archive/sipx-users Unsubscribe: http://list.sipfoundry.org/mailman/listinfo/sipx-users
