origination_caller_id_number used instead of effective_caller_id_number
I don't know what I'm doing wrong. origination_caller_id_number is used on the B-leg of the bridge, although I also specify the effective_caller_id_number. The thing is that it originally worked in my tests, and I can't figure out what changed in the meantime. The code is something like this ... session = new Session("{originate_retry_sleep_ms=30000,ignore_early_media=true,is_callcenter=0,origination_caller_id_number=+40722333444,effective_caller_id_number=+40711222333}sofia/gateway/provider/<phone>"); if (session.ready()) { new_session = new Session("sofia/gateway/provider/<another phone>", session); if (new_session.ready()) bridge(session, new_session); } Thanks,
Just a follow up, I execute the following command: originate {effective_caller_id_number=40722333444}sofia/gateway/provider/<phone1> &bridge('sofia/gateway/provider/<phone2>') And it worked, but when I add origination_caller_id_number ... it overrides effective_caller_id_number. My provider's setup is nothing fancy, something like: <param name="username" value="anything" /> <param name="password" value="anything"/> <param name="realm" value="<ip>" /> <param name="register" value="false"/> <!-- tried setting this on and off --> <!--<param name="caller-id-in-from" value="true"/>--> On Thu, 2009-02-19 at 12:36 +0200, Alexandru Nedelcu wrote:
I don't know what I'm doing wrong. origination_caller_id_number is used on the B-leg of the bridge, although I also specify the effective_caller_id_number.
The thing is that it originally worked in my tests, and I can't figure out what changed in the meantime.
The code is something like this ...
session = new Session("{originate_retry_sleep_ms=30000,ignore_early_media=true,is_callcenter=0,origination_caller_id_number=+40722333444,effective_caller_id_number=+40711222333}sofia/gateway/provider/<phone>");
if (session.ready()) {
new_session = new Session("sofia/gateway/provider/<another phone>", session); if (new_session.ready()) bridge(session, new_session); }
Thanks,
Clarification on the 2 vars....you set origination_caller_id_number on the call leg directly. you set effective_caller_id_number on any leg that will get bridged to something else. Internally, the core will look if effective_caller_id_number is set on the A-leg to see if it can use it. This said: originate {origination_caller_id_number=12223334444,effective_caller_id_number=13334445555}sofia/gateway/blah/12345 &bridge(sofia/gateway/blah/54321) 12345 is called and sees 12223334444 as callerid, then the call is bridged to 54321 which sees 13334445555 because bridge looks up the variable in the a-leg. It would be the same as doing originate {origination_caller_id_number=12223334444}sofia/gateway/blah/12345 &bridge({origination_caller_id_number=13334445555}sofia/gateway/blah/54321) Having it as effective_caller_id_number only saves you the extra work of setting it on all B-legs Mathieu On Thu, Feb 19, 2009 at 6:03 AM, Alexandru Nedelcu <alex@sinapticode.ro>wrote:
Just a follow up, I execute the following command:
originate {effective_caller_id_number=40722333444}sofia/gateway/provider/<phone1> &bridge('sofia/gateway/provider/<phone2>')
And it worked, but when I add origination_caller_id_number ... it overrides effective_caller_id_number.
My provider's setup is nothing fancy, something like:
<param name="username" value="anything" /> <param name="password" value="anything"/>
<param name="realm" value="<ip>" />
<param name="register" value="false"/> <!-- tried setting this on and off --> <!--<param name="caller-id-in-from" value="true"/>-->
On Thu, 2009-02-19 at 12:36 +0200, Alexandru Nedelcu wrote:
I don't know what I'm doing wrong. origination_caller_id_number is used on the B-leg of the bridge, although I also specify the effective_caller_id_number.
The thing is that it originally worked in my tests, and I can't figure out what changed in the meantime.
The code is something like this ...
session = new
Session("{originate_retry_sleep_ms=30000,ignore_early_media=true,is_callcenter=0,origination_caller_id_number=+40722333444,effective_caller_id_number=+40711222333}sofia/gateway/provider/<phone>");
if (session.ready()) {
new_session = new Session("sofia/gateway/provider/<another phone>", session); if (new_session.ready()) bridge(session, new_session); }
Thanks,
_______________________________________________ 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
OK, so effective_caller_id_number is the same as origination_caller_id_number set on the B-leg (cool). Unfortunately origination_caller_id_number on the A-leg overides the origination_caller_id_number on the B-leg (I tried setting it with both effective_caller_id on the A-leg and origination_caller_id on the B-leg). It doesn't work. If I'm setting caller-id on the B-leg only, then it works. Has this something to do with my SIP provider maybe? On Thu, 2009-02-19 at 08:42 -0500, Mathieu Rene wrote:
Clarification on the 2 vars.... you set origination_caller_id_number on the call leg directly. you set effective_caller_id_number on any leg that will get bridged to something else.
Internally, the core will look if effective_caller_id_number is set on the A-leg to see if it can use it.
This said: originate {origination_caller_id_number=12223334444,effective_caller_id_number=13334445555}sofia/gateway/blah/12345 &bridge(sofia/gateway/blah/54321)
12345 is called and sees 12223334444 as callerid, then the call is bridged to 54321 which sees 13334445555 because bridge looks up the variable in the a-leg.
It would be the same as doing originate {origination_caller_id_number=12223334444}sofia/gateway/blah/12345 &bridge({origination_caller_id_number=13334445555}sofia/gateway/blah/54321)
Having it as effective_caller_id_number only saves you the extra work of setting it on all B-legs
Mathieu
Can you re-test this with current svn trunk. I believe this was fixed yesterday. Mike On Feb 19, 2009, at 9:19 AM, Alexandru Nedelcu wrote:
OK, so effective_caller_id_number is the same as origination_caller_id_number set on the B-leg (cool).
Unfortunately origination_caller_id_number on the A-leg overides the origination_caller_id_number on the B-leg (I tried setting it with both effective_caller_id on the A-leg and origination_caller_id on the B-leg). It doesn't work.
If I'm setting caller-id on the B-leg only, then it works.
Has this something to do with my SIP provider maybe?
On Thu, 2009-02-19 at 08:42 -0500, Mathieu Rene wrote:
Clarification on the 2 vars.... you set origination_caller_id_number on the call leg directly. you set effective_caller_id_number on any leg that will get bridged to something else.
Internally, the core will look if effective_caller_id_number is set on the A-leg to see if it can use it.
This said: originate {origination_caller_id_number =12223334444,effective_caller_id_number=13334445555}sofia/gateway/ blah/12345 &bridge(sofia/gateway/blah/54321)
12345 is called and sees 12223334444 as callerid, then the call is bridged to 54321 which sees 13334445555 because bridge looks up the variable in the a-leg.
It would be the same as doing originate {origination_caller_id_number=12223334444}sofia/gateway/blah/12345 &bridge({origination_caller_id_number=13334445555}sofia/gateway/ blah/54321)
Having it as effective_caller_id_number only saves you the extra work of setting it on all B-legs
Mathieu
Yeap, it's fixed. On Thu, Feb 19, 2009 at 5:03 PM, Michael Jerris <mike@jerris.com> wrote:
Can you re-test this with current svn trunk. I believe this was fixed yesterday.
Mike
-- Alexandru Nedelcu Software Developer, Sinapticode
participants (3)
-
Alexandru Nedelcu
-
Mathieu Rene
-
Michael Jerris