Displaying 4 results from an estimated 4 matches for "2030s".
Did you mean:
2030
2016 Jan 06
2
Asterisk 11 and old Thomson 2030S Hardphone => SIP Register/Auth Problem against V11
...y New Year first!
Allthough, I'm relative new to Asterisk, I got our server up and
Running, Softphones, ISDN, and a brand new Snom 821 are working
flawlessly. :)
Platform is Debian 8/Asterisk Packages (11) from Debian Repo.
But I am running into problems setting up 2 older Hardphones, Thomson
2030S. :(
with in my sip.conf, I have got for this hardphone:
[...]
[hard1]
username=hard1
secret=correct-and-three-times-checked-4-digit-pin
allow=ulaw
allow=alaw
context=internal
type=friend
nat=force_rport,comedia
qualify=yes
ho...
2016 Jan 07
2
Asterisk 11 and old Thomson 2030S Hardphone => SIP Register/Auth Problem against V11
Am 07.01.2016 um 10:55 schrieb Frank:
> On Wed, 2016-01-06 at 17:03 +0100, Juergen Sauer wrote:
Thx, 4answer. :)
>> with in my sip.conf, I have got for this hardphone:
>> [...]
>> [hard1]
>> username=hard1
>> secret=correct-and-three-times-checked-4-digit-pin
>
> In most cases, there is no need to set the "username=" option. The
2016 Apr 04
2
Understanding POSIXct creation on different OSes.
...t from GMT in
use either for 1902 (when there was no DST) or that predicted for
one of 2030 to 2037 (chosen so that the likely DST transition days
are Sundays), and uses the alternate (daylight-saving) time zone
only if ?isdst? is positive or (if ?-1?) if DST was predicted to
be in operation in the 2030s on that day."
It's not clear what this exactly means, and if it is related to the
behaviour shown above. It'd be nice to know if a) this behaviour of
non-identical result is as expected, and if so, b) can we rely on
setting 'isdst' to -1 returning the expected result always?...
2016 Apr 11
0
Understanding POSIXct creation on different OSes.
...in
| use either for 1902 (when there was no DST) or that predicted for
| one of 2030 to 2037 (chosen so that the likely DST transition days
| are Sundays), and uses the alternate (daylight-saving) time zone
| only if ?isdst? is positive or (if ?-1?) if DST was predicted to
| be in operation in the 2030s on that day."
|
| It's not clear what this exactly means, and if it is related to the
| behaviour shown above. It'd be nice to know if a) this behaviour of
| non-identical result is as expected, and if so, b) can we rely on
| setting 'isdst' to -1 returning the expected result...