On Tue, Nov 8, 2011 at 3:23 AM, Zhiping Wang <[email protected]>wrote:
>
> Mircea,
>
> Unfortunately, In the latest 4.4 update 14, is not availabe.
> Eevn confpin is
> set the value(e.g confpin=1234) in
> /callcontroller/{user1}/{user2}?agent={user3}&timeout=30&isForwardingAllowed=true&confpin={3},
> user1 still need to input confpin before joining the conference. But in
> early update of 4.4 (I'm not sure which update), if confpin is set, user1
> does not need to input the confpin. There should be some wrong.
>
There wasn't changes on this area for quite some time...
Can you please attach sipxrest.log on the exact time when you run the REST
call...
thanks
mircea
>
> Thanks,
>
> Zp
>
>
> On Mon, Nov 7, 2011 at 10:19 PM, Zhiping Wang <[email protected]
> > wrote:
>
>> Great. It works. Thanks a lot, Mircea!
>>
>>
>> On Sun, Nov 6, 2011 at 4:41 PM, Mircea Carasel <[email protected]> wrote:
>>
>>>
>>>
>>> On Fri, Nov 4, 2011 at 4:10 PM, Zhiping Wang <
>>> [email protected]> wrote:
>>>
>>>> Hi,
>>>> It works for some commands e.g. lock, mute.
>>>> curl --digest -k -X PUT
>>>> https://200:123@localhost:8085/conference/mirceaConf/lock
>>>>
>>>> But how to use the dial command?
>>>> The description says: "dial <endpoint_module_name>/<destination>
>>>> <callerid number> <callerid name>"
>>>> Anybody run the dial command successfully? Could you please give an
>>>> example?
>>>>
>>> The following freeswitch commands are not supported via this rest
>>> service:
>>>
>>> dial <endpoint_module_name>/<destination> <callerid number> <callerid name>
>>> bgdial <endpoint_module_name>/<destination> <callerid number> <callerid
>>> name>
>>>
>>> The description of those commands do not respect the overall rule:
>>> {command}/{arg 1}/{arg 2} - which translates for freeswitch into
>>> "command arg1 arg2"
>>> For example mirceaConf/lock translates for freeswitch: "mirceaConf lock"
>>> The difference is that dial and bgdial contain "/" character that has to
>>> be part of the freeswitch command
>>>
>>> However, if you want to invite someone to bridge via REST, there is a
>>> REST api that accomplishes this:
>>> http://wiki.sipfoundry.org/display/sipXecs/Call+Control+Web+Service
>>>
>>> relative url sample to use:
>>> /callcontroller/{user1}/{user2}?agent={user3}&timeout=30&isForwardingAllowed=true&confpin={3}
>>>
>>> confpin stands for the conference pin (can be missing if no conference
>>> pin needed)
>>>
>>> Mircea
>>>
>>>
>>>> Please help!
>>>>
>>>> Zp
>>>>
>>>> _______________________________________________
>>>> sipx-users mailing list
>>>> [email protected]
>>>> List Archive: http://list.sipfoundry.org/archive/sipx-users/
>>>>
>>>
>>>
>>> _______________________________________________
>>> sipx-users mailing list
>>> [email protected]
>>> List Archive: http://list.sipfoundry.org/archive/sipx-users/
>>>
>>
>>
>
> _______________________________________________
> sipx-users mailing list
> [email protected]
> List Archive: http://list.sipfoundry.org/archive/sipx-users/
>
_______________________________________________
sipx-users mailing list
[email protected]
List Archive: http://list.sipfoundry.org/archive/sipx-users/
