ignore_display_updates blocks display name for IVR
Hi, I am using FreeSWITCH-mod_sofia/1.5.8b+git~20140204T065630Z~5228e02b19~64bit. To block to get display update after connected to IVR , I have added <X-PRE-PROCESS cmd="set" data="ignore_display_updates=false"/> to vars.xml and FS does not send update anymore. But this time on the phone screen, "Outgoing Call" is written instead of IVR. I have checked the code find the place what causes this, but I wonder this is related with this variable somehow. I would like to ask you that is there any way to send IVR string as displayname? Remote-Party-ID: "Outgoing Call" <sip:IVR@192.168.169.169
;party=calling;privacy=off;screen=no
regards Mehmet
Your phone is looking at the RPID. -- Brian West brian@freeswitch.org FreeSWITCH Solutions, LLC PO BOX 2531 Brookfield, WI 53008-2531 Twitter: @FreeSWITCH , @briankwest http://www.freeswitchbook.com http://www.freeswitchcookbook.com T: +1.918.420.9001 | F: +1.918.420.9002 | M: +1.918.424.WEST iNUM: +883 5100 1420 9001 ISN: 410*543 Skype:briankwest PGP Key: http://www.bkw.org/key.txt (AB93356707C76CED) On Feb 11, 2014, at 7:46 AM, mehmet ozisik <mehmetzsk@gmail.com> wrote:
Hi,
I am using FreeSWITCH-mod_sofia/1.5.8b+git~20140204T065630Z~5228e02b19~64bit. To block to get display update after connected to IVR , I have added <X-PRE-PROCESS cmd="set" data="ignore_display_updates=false"/> to vars.xml and FS does not send update anymore. But this time on the phone screen, "Outgoing Call" is written instead of IVR. I have checked the code find the place what causes this, but I wonder this is related with this variable somehow. I would like to ask you that is there any way to send IVR string as displayname?
Remote-Party-ID: "Outgoing Call" <sip:IVR@192.168.169.169>;party=calling;privacy=off;screen=no
regards Mehmet
Hi, Thx Brian Yes it is but I am looking for a way to change it within FS, I can not configure the phone. these settings also did not work : <action application="set" data="effective_caller_id_name=Mehmet1"/> <action application="set" data="origination_callee_id_name=Mehmet2"/> <action application="set" data="origination_callee_id_number=Mehmet3"/> <action application="set" data="caller_id_name=Mehmet4"/> <action application="set" data="caller_id_number=Mehmet5"/> <action application="set" data="effective_caller_id_number=Mehmet6"/> <X-PRE-PROCESS cmd="set" data="effective_caller_id_name=MMehmet1"/> <X-PRE-PROCESS cmd="set" data="origination_callee_id_name=MMehmet2"/> <X-PRE-PROCESS cmd="set" data="origination_callee_id_number=MMehmet3"/> <X-PRE-PROCESS cmd="set" data="caller_id_name=MMehmet4"/> <X-PRE-PROCESS cmd="set" data="caller_id_number==MMehmet5"/> <X-PRE-PROCESS cmd="set" data="effective_caller_id_number=MMehmet6"/> Regards Mehmet 2014-02-11 15:52 GMT+02:00 Brian West <brian@freeswitch.org>:
Your phone is looking at the RPID. -- Brian West brian@freeswitch.org FreeSWITCH Solutions, LLC PO BOX 2531 Brookfield, WI 53008-2531 Twitter: @FreeSWITCH , @briankwest http://www.freeswitchbook.com http://www.freeswitchcookbook.com
T: +1.918.420.9001 | F: +1.918.420.9002 | M: +1.918.424.WEST iNUM: +883 5100 1420 9001 ISN: 410*543 Skype:briankwest PGP Key: http://www.bkw.org/key.txt (AB93356707C76CED)
On Feb 11, 2014, at 7:46 AM, mehmet ozisik <mehmetzsk@gmail.com> wrote:
Hi,
I am using FreeSWITCH-mod_sofia/1.5.8b+git~20140204T065630Z~5228e02b19~64bit. To block to get display update after connected to IVR , I have added <X-PRE-PROCESS cmd="set" data="ignore_display_updates=false"/> to vars.xml and FS does not send update anymore. But this time on the phone screen, "Outgoing Call" is written instead of IVR. I have checked the code find the place what causes this, but I wonder this is related with this variable somehow. I would like to ask you that is there any way to send IVR string as displayname?
Remote-Party-ID: "Outgoing Call" <sip:IVR@192.168.169.169 ;party=calling;privacy=off;screen=no
regards Mehmet
_________________________________________________________________________ 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
Details, caller_id_name and caller_id_number aren’t real (you can however use set_profile_var to use those but I wouldn’t) origination_callee/caller bits go inside {} on the bridge line, they have no effect on the a-leg of the call. Effective bits are explained here: https://wiki.freeswitch.org/wiki/Variable_effective_caller_id_number (also follow the see also links) Remember, you'll need to understand that FreeSWITCH has two threads for each bridged session, The so called A-Leg, and the so called B-Leg. The idea of how this works gets more complex when A calls B and A transfers. You’ll quickly get confused on who or what is the caller vs callee. There is a JIRA open for me to extend this documentation. I’ll need copious amounts of coffee and time to complete the task. It gets more fun when you originate an outbound call to A and then A is linked to another outbound B leg via the dial plan. You technically have two outbound legs… ;) -- Brian West brian@freeswitch.org FreeSWITCH Solutions, LLC PO BOX 2531 Brookfield, WI 53008-2531 Twitter: @FreeSWITCH , @briankwest http://www.freeswitchbook.com http://www.freeswitchcookbook.com T: +1.918.420.9001 | F: +1.918.420.9002 | M: +1.918.424.WEST iNUM: +883 5100 1420 9001 ISN: 410*543 Skype:briankwest PGP Key: http://www.bkw.org/key.txt (AB93356707C76CED) On Feb 11, 2014, at 8:14 AM, mehmet ozisik <mehmetzsk@gmail.com> wrote:
Hi,
Thx Brian Yes it is but I am looking for a way to change it within FS, I can not configure the phone. these settings also did not work :
<action application="set" data="effective_caller_id_name=Mehmet1"/> <action application="set" data="origination_callee_id_name=Mehmet2"/> <action application="set" data="origination_callee_id_number=Mehmet3"/> <action application="set" data="caller_id_name=Mehmet4"/> <action application="set" data="caller_id_number=Mehmet5"/> <action application="set" data="effective_caller_id_number=Mehmet6"/>
<X-PRE-PROCESS cmd="set" data="effective_caller_id_name=MMehmet1"/> <X-PRE-PROCESS cmd="set" data="origination_callee_id_name=MMehmet2"/> <X-PRE-PROCESS cmd="set" data="origination_callee_id_number=MMehmet3"/> <X-PRE-PROCESS cmd="set" data="caller_id_name=MMehmet4"/> <X-PRE-PROCESS cmd="set" data="caller_id_number==MMehmet5"/> <X-PRE-PROCESS cmd="set" data="effective_caller_id_number=MMehmet6"/>
https://wiki.freeswitch.org/wiki/Sofia.conf.xml <!-- *optional* --> <param name="cid-type" value="rpid"/> On Feb 11, 2014, at 11:00 AM, Brian West <brian@freeswitch.org> wrote:
Details,
caller_id_name and caller_id_number aren’t real (you can however use set_profile_var to use those but I wouldn’t)
origination_callee/caller bits go inside {} on the bridge line, they have no effect on the a-leg of the call.
Effective bits are explained here:
https://wiki.freeswitch.org/wiki/Variable_effective_caller_id_number (also follow the see also links)
Remember, you'll need to understand that FreeSWITCH has two threads for each bridged session, The so called A-Leg, and the so called B-Leg. The idea of how this works gets more complex when A calls B and A transfers. You’ll quickly get confused on who or what is the caller vs callee. There is a JIRA open for me to extend this documentation. I’ll need copious amounts of coffee and time to complete the task.
It gets more fun when you originate an outbound call to A and then A is linked to another outbound B leg via the dial plan. You technically have two outbound legs… ;)
On Feb 11, 2014, at 8:14 AM, mehmet ozisik <mehmetzsk@gmail.com> wrote:
Hi,
Thx Brian Yes it is but I am looking for a way to change it within FS, I can not configure the phone. these settings also did not work :
<action application="set" data="effective_caller_id_name=Mehmet1"/> <action application="set" data="origination_callee_id_name=Mehmet2"/> <action application="set" data="origination_callee_id_number=Mehmet3"/> <action application="set" data="caller_id_name=Mehmet4"/> <action application="set" data="caller_id_number=Mehmet5"/> <action application="set" data="effective_caller_id_number=Mehmet6"/>
<X-PRE-PROCESS cmd="set" data="effective_caller_id_name=MMehmet1"/> <X-PRE-PROCESS cmd="set" data="origination_callee_id_name=MMehmet2"/> <X-PRE-PROCESS cmd="set" data="origination_callee_id_number=MMehmet3"/> <X-PRE-PROCESS cmd="set" data="caller_id_name=MMehmet4"/> <X-PRE-PROCESS cmd="set" data="caller_id_number==MMehmet5"/> <X-PRE-PROCESS cmd="set" data="effective_caller_id_number=MMehmet6"/>
Hi, ı had tried cid-type and sip_cid_type for sofia.conf.xml with value "none" but had not see the effect. Could you please inform me how should I set it in which conf file? @Brian : in which file should I set origination_callee_id_name and how if my channel name sofia/<domainname>/sip:IVR@<ip:port> Could you please help on these? Regards Mehmet 2014-02-11 18:43 GMT+02:00 Michael Jerris <mike@jerris.com>:
https://wiki.freeswitch.org/wiki/Sofia.conf.xml
<!-- *optional* --> <param name="cid-type" value="rpid"/>
On Feb 11, 2014, at 11:00 AM, Brian West <brian@freeswitch.org> wrote:
Details,
caller_id_name and caller_id_number aren't real (you can however use set_profile_var to use those but I wouldn't)
origination_callee/caller bits go inside {} on the bridge line, they have no effect on the a-leg of the call.
Effective bits are explained here:
https://wiki.freeswitch.org/wiki/Variable_effective_caller_id_number (also follow the see also links)
Remember, you'll need to understand that FreeSWITCH has two threads for each bridged session, The so called A-Leg, and the so called B-Leg. The idea of how this works gets more complex when A calls B and A transfers. You'll quickly get confused on who or what is the caller vs callee. There is a JIRA open for me to extend this documentation. I'll need copious amounts of coffee and time to complete the task.
It gets more fun when you originate an outbound call to A and then A is linked to another outbound B leg via the dial plan. You technically have two outbound legs... ;)
On Feb 11, 2014, at 8:14 AM, mehmet ozisik <mehmetzsk@gmail.com> wrote:
Hi,
Thx Brian Yes it is but I am looking for a way to change it within FS, I can not configure the phone. these settings also did not work :
<action application="set" data="effective_caller_id_name=Mehmet1"/> <action application="set" data="origination_callee_id_name=Mehmet2"/> <action application="set" data="origination_callee_id_number=Mehmet3"/> <action application="set" data="caller_id_name=Mehmet4"/> <action application="set" data="caller_id_number=Mehmet5"/> <action application="set" data="effective_caller_id_number=Mehmet6"/>
<X-PRE-PROCESS cmd="set" data="effective_caller_id_name=MMehmet1"/> <X-PRE-PROCESS cmd="set" data="origination_callee_id_name=MMehmet2"/> <X-PRE-PROCESS cmd="set" data="origination_callee_id_number=MMehmet3"/> <X-PRE-PROCESS cmd="set" data="caller_id_name=MMehmet4"/> <X-PRE-PROCESS cmd="set" data="caller_id_number==MMehmet5"/> <X-PRE-PROCESS cmd="set" data="effective_caller_id_number=MMehmet6"/>
_________________________________________________________________________ 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
participants (3)
-
Brian West
-
mehmet ozisik
-
Michael Jerris