Scott Lawrence wrote: > > It is not totally clear to me why CallerAlias does not manipulate > > CallerID for external callers, > > The reasoning is pretty simple - we are trying to make the > caller id as much as possible reflect who will be on the > other end of the phone if the callee answers it. If I have > my office phone forwarded to my cell, or if someone in the > office blind transfers an outside call to me, then the caller > id presented on my cell phone will be that of the party I'll > be speaking to if I accept the call (at least to the extent > that the caller id they provided when they called my office > was honest, but there's nothing much we can do about that > problem). If the system replaced that From header with that > of some number for the office, then I get misleading > caller-id: it's not my office calling, and I won't be talking > to my office if I answer.
I think I see an inconsistency in the CallerID behavior for external calls. Assuming I am using gateway A with "specify CallerID" option, which translated into wildcard entry for the gateway domain. A call from whate...@sipxdomain routed to the gateway gets the CallerId overwritten. If I have an analog/digital gateway (such as Audiocodes), I receive a call from PSTN and send it to gateway A. Audiocodes formats the "from" header as <PSTNCaller>@<sipXdomain>. Since the caller domain is local the caller ID rewrite takes place. Compared to that if I receive a call from SIP trunk gateway B (B may be the same as A) sipXbridge formats the "from" header as <ITSPCaller>@<gatewayBdomain>. Since the caller domain is NOT local the caller ID rewrite does NOT take place. Can this inconsistency be resolved simply by setting the sipXdomain in the "from" header rather then using the gateway domain? Are there any other reasons why the gateway domain is used? Another problem with wildcard CallerId rewrite as it is related to multiple ITSP accounts with the same domain: If more then one SIP trunk gateway with the same domain use "specify CallerID" option then the two settings clash. The key of the CallerId wildcard entry is domain and two SIP trunk gateways with the same domain result in two colliding entries in caller-alias.xml database. Mark. _______________________________________________ sipx-dev mailing list [email protected] List Archive: http://list.sipfoundry.org/archive/sipx-dev Unsubscribe: http://list.sipfoundry.org/mailman/listinfo/sipx-dev sipXecs IP PBX -- http://www.sipfoundry.org/
