Thanks, Per. (01)
Possibly, the next time you plan to join us, we could run a little
private test prior to the official session, to make sure you can
connect properly. (02)
In future, I will heed their advice and avoid placing two of the same
number alongside each other. You might consider just sending the
access code without the "#" key (and just wait till it gets
recognized) if you come across any difficulty getting connected to the
conference on first try. (03)
Let's set that up by email when the opportunity arises. (04)
Regards,
PPY
-- (05)
Per Myrseth wrote Mon, 26 Apr 2004 10:49:25 +0200: (06)
> Hi
>
> Thank you for responding to my problems entering the conferance. Related
> to what Mark mentions regarding
> use of mobile phone. I did use my mobil phone calling a telephone service
> number in Norway. This service
> forewarded me to the conferance call.
>
> Sincerely
> Per Myrseth
> -------------------------------------
> Senior Security Consultant
> PKI Consulting & Services
> ITS Norway
> Address: IBM, Rosenholmvn. 25, N-1411 Kolbotn, NORWAY
> Cell.: +47 99524768, Fax: +47 66999333
> E-mail: per.myrseth@xxxxxxxxxx
> http://www-5.ibm.com/services/no/its/validsign/ (07)
> Peter Yim
> <peter.yim@xxxxxx
> om> To
> conference-support@xxxxxxxxxxxxx
> 23.04.2004 21:25 cc
> Per Myrseth/Norway/IBM@IBMNO,
> "'[cwe-imp]'"
> <cwe-imp@xxxxxxxxxxxx>
> Subject
> Re: FreeConference.com Support
> Request
>
>
>
>
>
>
>
>
>
>
> Hello Mark,
>
> Thank you for the very comprehensive answer. I will certainly make a
> note of that in the future.
>
> Let's see if Per has anything else to add. If not, we can consider
> this ticket closed.
>
> Thanks & regards,
> PPY
> -- (08)
> Conference Call Support wrote Fri, 23 Apr 2004 11:47:36 -0700:
>
>
>>Hello Peter,
>>
>>The problem does not appear to be related to the # sign. It is not
>
> strictly
>
>>required anyway. Our computer interprets the # sign as an indication
>
> that
>
>>the caller is done entering digits. If the # sign is omitted the caller
>>will still get into the conference (as long as the access code itself is
>>valid), although it will take several seconds longer for our computer to
>>realize the caller is done entering digits.
>>
>>I can see from our log files that one or more callers were attempting to
>>enter the access code "2004422". However, what we received was "204422".
>>The two zeroes had run together and our computer could not discern that
>
> two
>
>>separate digits were entered. That could have been because of a poor
>>quality international circuit between Norway and the USA, the caller may
>>have been using a mobile phone that does not emit touchtones of
>
> sufficient
>
>>length to be interpreted correctly, or a combination of these two
>
> factors.
>
>>Of course, I have no way of knowing if Mr. Myrseth was using a mobile
>
> phone.
>
>>My recommendation is to avoid using mobile phones to call into conference
>>calls, especially internationally, as the lower sound quality can degrade
>>the sound in the entire conference call. I also recommend avoiding using
>
> an
>
>>access code that has consecutive digits (e.g. 00 and 44). A better
>
> access
>
>>code would be, for example, 20402020 (not to mention that it doesn't
>
> include
>
>>the current date). Thank you.
>>
>>Best Regards,
>>
>>Mark (09)
>>>-----Original Message-----
>>>From: Peter Yim [mailto:peter.yim@xxxxxxxx]
>>>Sent: Friday, April 23, 2004 11:24 AM
>>>To: conference-support@xxxxxxxxxxxxx
>>>Cc: Per Myrseth; [cwe-imp]
>>>Subject: Re: FreeConference.com Support Request
>>>
>>>Hello Mark,
>>>
>>>Thank you for the prompt response.
>>>
>>>Our colleague from Norway, Per, has evidently tried using "#"
>>>(the "pound" sign) at the end of the access code, without success.
>>>
>>>I'm copying him here to see if the two of you can communicate
>>>directly (keep me in the loop, though) to resolve this.
>>>
>>>Thanks,
>>>PPY
>>>-- (010)
>>>Conference Call Support wrote Fri, 23 Apr 2004 09:07:24 -0700:
>>>
>>>
>>>
>>>>Hi Peter,
>>>>
>>>>The # is the key that is referred to in the prompt to enter
>>>
>>>the "pound
>>>
>>>
>>>>sign".
>>>>
>>>>By the way, it is not advisable to use today's date as your access
>>>>code. Many other groups do this same thing and it is only
>>>
>>>a matter of
>>>
>>>
>>>>time before a stranger stumbles into one of your conferences. We
>>>>recommend choosing a more secure access code that does not include
>>>>guessable digits such as the current date or repeating sequences of
>>>>numbers. Thank you.
>>>>
>>>>Regards,
>>>>
>>>>Mark Phillips
>>>>FreeConference Support (011)
> ===
> Peter Yim wrote:
>
>>>> I am asking this on behalf of one of our call attendees who was
>>>> trying to join us from Norway. This is the feedback I
>>>
>>>got from him:
>>>
>>>
>>>> // I tried to call up several times yesterday, punhced
>>>
>>>the access
>>>
>>>
>>>> code but the code and the following postfix sign did not get
>>>> accepted. I tried to use both "*" and "#" as ending signs after
>>>> puncing the access code, but I did'nt have any success.
>>>
>>>To be better
>>>
>>>
>>>> prepared to next conferance call could you give me a
>>>
>>>hint on which
>>>
>>>
>>>> sign to use? --pm // Please advise how I should answer
>>>
>>>him. Thanks.
>>>
>>>
>>>> -ppy
_________________________________________________________________
To Post: mailto:ontolog-admin@xxxxxxxxxxxxxxxx
Message Archives: http://ontolog.cim3.net/forum/ontolog-admin/
Community Wiki: http://ontolog.cim3.net/wiki/
Shared Files: http://ontolog.cim3.net/file/
Community Portal: http://ontolog.cim3.net/ (012)
|