[Spce-user] CONFERENCE

[Daniel Grotti]

Hi,
Please check that your device is supporting DTMF based on 
telephone-event (RFC 2833).
Looks like a DTMF problem. Have you tried from some other phone/softphones?

Another check to do: what do you see in /var/log/ngcp/sems.log? You 
should see something like:

Jan  8 17:02:30 sp1 sems[10451]: [#7fcdc75f5700] [execute, 
DSMCoreModule.cpp:542] INFO: FSM: '>> start_pin_entry'
Jan  8 17:02:30 sp1 sems[10451]: [#7fcdc75f5700] [execute, 
DSMCoreModule.cpp:542] INFO: FSM: 'start_pin_entry <<'
Jan  8 17:02:36 sp1 sems[10451]: [#7fcdc75f5700] [execute, 
DSMCoreModule.cpp:542] INFO: FSM: 'USER ENTERED key '2''
Jan  8 17:02:36 sp1 sems[10451]: [#7fcdc75f5700] [execute, 
DSMCoreModule.cpp:542] INFO: FSM: 'USER ENTERED key '6''
Jan  8 17:02:36 sp1 sems[10451]: [#7fcdc75f5700] [execute, 
DSMCoreModule.cpp:542] INFO: FSM: 'USER ENTERED key '5''
Jan  8 17:02:37 sp1 sems[10451]: [#7fcdc75f5700] [execute, 
DSMCoreModule.cpp:542] INFO: FSM: 'USER ENTERED key '8''
Jan  8 17:02:37 sp1 sems[10451]: [#7fcdc75f5700] [execute, 
DSMCoreModule.cpp:542] INFO: FSM: 'Key 11 pressed, tryAgain is 0'
Jan  8 17:02:37 sp1 sems[10451]: [#7fcdc75f5700] [execute, 
DSMCoreModule.cpp:542] INFO: FSM: '>> incorrect_retry, pin '2658', 
tryAgain '0''




Daniel




On 01/08/2018 04:49 PM, Syaiful Bahri Kamaruddin wrote:
>
> Hi Daniel,
>
> Sorry not to cc to user list.
>
> I had set up the pin number on the subscriber for the conference, but 
> when other subscriber call to it asking for pin, they enter it 
> accordingly but the system said the pin is invalid. But when I remove 
> the pin from the subscriber, they can go into conference.
>
> Mr 5.5.2
>
>          With PIN
>
>  1. Conference number > set with pin
>  2. Other subscriber call to conference number > enter PIN > pin invalid
>
>          Without PIN
>
>  1. Conference number > NO PIN
>  2. Other subscriber call in > get into conference with prompt from
>     system telling the que number are…
>
> Best Regards
>
> Syaiful
>
> Sent from Mail <https://go.microsoft.com/fwlink/?LinkId=550986> for 
> Windows 10
>
> ------------------------------------------------------------------------
> *From:* Daniel Grotti <dgrotti at sipwise.com>
> *Sent:* Monday, January 8, 2018 10:50:22 PM
> *To:* Syaiful Bahri Kamaruddin
> *Subject:* Re: [Spce-user] CONFERENCE
> Hi,
> please make sure to write to the mailing list.
> What is the problem? that you can still enter without pin, if pin is set?
>
>
> Daniel
>
>
> On 01/08/2018 03:48 PM, Syaiful Bahri Kamaruddin wrote:
>>
>> Hi Daniel,
>>
>> Have activated the soun set, call to conference can enter the 
>> conference line without pin . but when set the pin , when prompt to 
>> enter the pin that i set, it prompt , "you have entere invalid pin , 
>> please try again" , but without pin, i can enter .
>> Need your advise what to do next.
>>
>> Best Regards
>> Syaiful
>>
>> On January 8, 2018 2:41:25 PM Daniel Grotti <dgrotti at sipwise.com> wrote:
>>
>>> Hi,
>>> Conference is enabled out of the box.
>>> First you have to configure sound set and assign them to you domain. 
>>> You can load the  default sound sets in English.
>>> Then you can set Call forward to the conference in the subscriber’s 
>>> preferences.
>>>
>>> Daniel
>>>
>>>
>>> Sent from my iPhone
>>>
>>> On 06.01.2018, at 16:58, Syaiful Bahri Kamaruddin 
>>> <chefsyaiful at outlook.com <mailto:chefsyaiful at outlook.com>> wrote:
>>>
>>>> Hi All,
>>>>
>>>> How to setup conference system in SPCE MR5.5.2 step by step as I 
>>>> used this for my internal calling system but halt on conference 
>>>> setting. Further more id there any pre-make sound set to be download.
>>>>
>>>> Best Regards
>>>>
>>>> Syaiful Bahri Kamaruddin
>>>>
>>>> _______________________________________________
>>>> Spce-user mailing list
>>>> Spce-user at lists.sipwise.com <mailto:Spce-user at lists.sipwise.com>
>>>> https://lists.sipwise.com/listinfo/spce-user
>

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.sipwise.com/pipermail/spce-user_lists.sipwise.com/attachments/20180108/ae5e41c4/attachment-0001.html>