VoIP Mailing List Archives :: View topic - [Freeswitch-users] originate command sofia behaviour

Sponsor: VoiceMeUp - Corporate & Wholesale VoIP Services

VoIP Mailing List Archives
Mailing list archives for the VoIP community

[Freeswitch-users] originate command sofia behaviour

VoIP Mailing List Archives Forum Index -> freeSWITCH Users

View previous topic :: View next topic

Author

Message

aep.lists at it46.se
Guest

Posted: Wed Sep 16, 2009 9:42 am Post subject: [Freeswitch-users] originate command sofia behaviour

I will like to update the wiki to spell out clearly the differences between this three commands I have a IVR running in 4600 and the FS box has IP address 192.168.46.15 originate sofia/192.168.46.15/1001 4600 originate sofia/internal/1001@192.168.46.15 4600 originate sofia/internal/1001%192.168.46.15 4600 The first originate places a call as a external gateway, not until registered phone 1001 answers the call is transfer to 4600 The second and third originate command triggers extension 4600 Javascript IVR although 1001 has not answer Can anyone clarify me if this is the intended behavior also including the difference between % and @ /aep _______________________________________________ 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

msc at freeswitch.org
Guest

Posted: Wed Sep 16, 2009 1:32 pm Post subject: [Freeswitch-users] originate command sofia behaviour

On Wed, Sep 16, 2009 at 7:26 AM, Alberto Escudero <aep.lists@it46.se (aep.lists@it46.se)> wrote:

Quote:

I will like to update the wiki to spell out clearly the differences
between this three commands
I have a IVR running in 4600 and the FS box has IP address 192.168.46.15

originate sofia/192.168.46.15/1001 4600
originate sofia/internal/1001@192.168.46.15 (1001@192.168.46.15) 4600
originate sofia/internal/1001%192.168.46.15 4600

The first originate places a call as a external gateway, not until
registered phone 1001 answers the call is transfer to 4600

The second and third originate command triggers extension 4600 Javascript
IVR although 1001 has not answer

Can anyone clarify me if this is the intended behavior also including the
difference between % and @

The difference between % and @ is discussed here:
http://wiki.freeswitch.org/wiki/Dialplan_XML#SIP-Specific_Dialstrings
-MC

aep.lists at it46.se
Guest

Posted: Wed Sep 16, 2009 1:47 pm Post subject: [Freeswitch-users] originate command sofia behaviour

The problem i am facing is the following:

Extension 4600 is a Javascript IVR that starts by session.aswer()

I want to originate a call to leg 1 and then connected to the IVR when the
leg 1 has answered.

If I run

originate sofia/192.168.46.15/1001 4600
call is transfer to extension 4600 *IVR* after 1001 answers the call

If I run
originate sofia/internal/1001@192.168.46.15 4600
the IVR starts BEFORE user 1001 has answered?

What is the best way to:

Initiate a call to leg 1 and connect it to leg 2 (the Javascript IVR)
after leg 1 has answered the call?

/aep

--
Stopping junk mailers is good for the environment

Quote:

On Wed, Sep 16, 2009 at 7:26 AM, Alberto Escudero <aep.lists@it46.se>
wrote:

Quote:

I will like to update the wiki to spell out clearly the differences
between this three commands
I have a IVR running in 4600 and the FS box has IP address 192.168.46.15

originate sofia/192.168.46.15/1001 4600
originate sofia/internal/1001@192.168.46.15 4600
originate sofia/internal/1001%192.168.46.15 4600

The first originate places a call as a external gateway, not until
registered phone 1001 answers the call is transfer to 4600

The second and third originate command triggers extension 4600
Javascript
IVR although 1001 has not answer

Can anyone clarify me if this is the intended behavior also including
the
difference between % and @

The difference between % and @ is discussed here:
http://wiki.freeswitch.org/wiki/Dialplan_XML#SIP-Specific_Dialstrings
-MC
_______________________________________________
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

_______________________________________________
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

msc at freeswitch.org
Guest

Posted: Wed Sep 16, 2009 2:10 pm Post subject: [Freeswitch-users] originate command sofia behaviour

On Wed, Sep 16, 2009 at 11:43 AM, Alberto Escudero <aep.lists@it46.se (aep.lists@it46.se)> wrote:

Quote:

The problem i am facing is the following:

Extension 4600 is a Javascript IVR that starts by session.aswer()

I want to originate a call to leg 1 and then connected to the IVR when the
leg 1 has answered.

If I run

originate sofia/192.168.46.15/1001 4600

call is transfer to extension 4600 *IVR* after 1001 answers the call

If I run
originate sofia/internal/1001@192.168.46.15 (1001@192.168.46.15) 4600

the IVR starts BEFORE user 1001 has answered?

What is the best way to:

Initiate a call to leg 1 and connect it to leg 2 (the Javascript IVR)
after leg 1 has answered the call?

You can try ignoring early media to force the A-leg to answer before anything else happens. Try this and let us know if it does what you want:
originate {ignore_early_media=true} sofia/internal/1001@192.168.46.15 (1001@192.168.46.15) 4600

You can probably look at the SIP traces of the two options you've tried (without ignoring early media) to confirm that you're getting media prior to answer when doing "originate sofia/internal/1001@192.168.46.15 (1001@192.168.46.15) 4600" - probably in one case you get a 180 and in the other a 183. Check it out and let us know. Smile

-MC

aep.lists at it46.se
Guest

Posted: Wed Sep 16, 2009 3:45 pm Post subject: [Freeswitch-users] originate command sofia behaviour

Yes, it did work! No we do not need to pay for several GSM calls to test
a IVR script!

/aep and gmaruzz
--
Stopping junk mailers is good for the environment

Quote:

On Wed, Sep 16, 2009 at 11:43 AM, Alberto Escudero
<aep.lists@it46.se>wrote:

Quote:

The problem i am facing is the following:

Extension 4600 is a Javascript IVR that starts by session.aswer()

I want to originate a call to leg 1 and then connected to the IVR when
the
leg 1 has answered.

If I run

originate sofia/192.168.46.15/1001 4600
call is transfer to extension 4600 *IVR* after 1001 answers the call

If I run
originate sofia/internal/1001@192.168.46.15 4600
the IVR starts BEFORE user 1001 has answered?

What is the best way to:

Initiate a call to leg 1 and connect it to leg 2 (the Javascript IVR)
after leg 1 has answered the call?

You can try ignoring early media to force the A-leg to answer before
anything else happens. Try this and let us know if it does what you want:
originate {ignore_early_media=true} sofia/internal/1001@192.168.46.15 4600

You can probably look at the SIP traces of the two options you've tried
(without ignoring early media) to confirm that you're getting media prior
to
answer when doing "originate sofia/internal/1001@192.168.46.15 4600" -
probably in one case you get a 180 and in the other a 183. Check it out
and
let us know. Smile

-MC
_______________________________________________
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

Display posts from previous:

	VoIP Mailing List Archives Forum Index -> freeSWITCH Users	All times are GMT - 5 Hours
Page 1 of 1

You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot vote in polls in this forum