Thanks Mike. Yep, it seems broken, but they don't seem to think it's their issue. 1) This would mean that I have to handle this carriers and others carrier separately. I do a bunch of things to process the inbound caller ID so that's not really ideal.. 2) I think gateway caller-id-in-from is for outbound, not inbound. Perhaps cid_type=none but right now it's just an ACL for inbound so I'd have to create a user for each incoming IP address and set the var there. Not ideal... -Avi On Mon, Nov 5, 2012 at 3:29 PM, Michael Jerris <mike@jerris.com> wrote:
I am not sure why they would tell you to ignore PID, that seem broken to me. However, in this case, you could resolve it in a couple ways.
1) you could just look at the sip_from_user variable 2) you could set a param on the gateway for caller id in from (this may be less sucessful based on if we can match this inbound call to the gateway)
Mike
On Nov 3, 2012, at 5:45 PM, Avi Marcus <avi@avimarcus.net> wrote:
Hi - I'm getting calls from a carrier with the proper e.164 FROM but their PID is coming in inconsistently. I was told to ignore the PID.
Apparently, FS is using the PID for the profile Caller-Caller-ID-Number variable.
Are there any toggles for how to manage *inbound *caller ID? This is currently coming in via ACL to public context... can I even set the sip_cid for that?
Suggestions?
Thanks,
-Avi Marcus
_________________________________________________________________________ Professional FreeSWITCH Consulting Services: consulting@freeswitch.org http://www.freeswitchsolutions.com
FreeSWITCH-powered IP PBX: The CudaTel Communication Server http://www.cudatel.com
Official FreeSWITCH Sites http://www.freeswitch.org http://wiki.freeswitch.org http://www.cluecon.com
FreeSWITCH-users mailing list FreeSWITCH-users@lists.freeswitch.org http://lists.freeswitch.org/mailman/listinfo/freeswitch-users UNSUBSCRIBE:http://lists.freeswitch.org/mailman/options/freeswitch-users http://www.freeswitch.org