[720P]Top.Gear.S24&S25

生肉注意!

孔乙己是站着喝酒而穿长衫的唯一的人。他身材很高大;青白脸色,皱纹间时常夹些伤痕;一部乱蓬蓬的花白的胡子。穿的虽然是长衫,可是又脏又破,似乎十多年没有补,也没有洗。他对人说话,总是满口之乎者也,叫人半懂不懂的。


因为他姓孔,别人便从描红纸上的“pan.baidu.com/s/1vGGSunfS-IMHd6RQGCuePw”这半懂不懂的话里,替他取下一个绰号,叫作wsyv。


孔乙己一到店,所有吃瓜的人便都看着他笑,有的叫道,“生肉,有能看得懂的嘛?”他不回答,对柜里说,“自带BBC英文声轨,自己当做听力练习”便排出五毛大洋。他们又故意的高声嚷道,“你一定又偷了人家的东西了!”孔乙己睁大眼睛说,“你怎么这样凭空污人清白……”“什么清白?萌新都不知道怎么用这代码!”孔乙己便涨红了脸,额上的青筋条条绽出,争辩道,“不会自己百度?……谷歌!……源文件名都没改,能算偷么?”接连便是难懂的话,什么“萌新固傻”,什么“者乎”之类,引得众人都哄笑起来:店内外充满了快活的空气。

默认俄语!

[ICCD]Cisco Phone Cheat Codes

There are many things in this world that are hidden just beneath the surface that make our lives easier.  Whether it be the Secret Menu at In-n-Out Burger or the good old Konami Code, the good stuff that we need is often just out of reach unless you know the code.  This is also the case when dealing with Cisco phones.  There are three key combinations that will help you immensely when configuring these devices, provided you know what they are.

1.  Unlock Settings – *, *, #.  When you check the settings on a Cisco phone, you’ll notice that you can look at the values but you can’t change any of them.  Many of these values are set at the Cisco Unified Communications Manager (CUCM) level.  However, once common issue is the phone not being able to contact the CUCM server or the phone having the wrong address/TFTP server information from DHCP.  While there are a multitude of ways to correct these issues in the network, there is a quick method to unlock the phone to change the settings.

  • Go to the Settings page of the phone
  • While in the settings page, press *, *, # (star, star, pound) about 1/2 second apart
  • The phone will display “Settings Unlocked” and allow you to make changes

It’s that easy.  There won’t be a whole lot to do with the phone Telephony User Interface (TUI), but you can make quick changes to DHCP, IP address, or TFTP server address entries to verify the phone configuration is correct.  By the way, when putting in an IP address via TUI, the “*” key can be used to put a period in an IP address.  That should save you an extra keystroke or two.

2.  Hard Reset – *,*,#,*,*.  Sometimes, you just need to reboot.  There are a variety of things that can cause a phone to need to be reset.  Firmware updates, line changes, or even ring cadence necessitate reboots.  While you can trigger these from the CUCM GUI, there are also times that they may need to be done from the phone itself in the event of a communications issue.  Rebooting is also a handy method for beginning to troubleshoot issues.

But Tom?  Why not just pull the network cable from the back of the phone?  Won’t disconnecting the power reboot?

True, it will.  What if the phone is mounted to the wall?  Or if the phone is running from an external power supply?  Or positioned in such as way that only the keypad is visible?  Better to know a different way to reboot just in case.  Here’s where the reboot cheat code comes in handy.

  • Go to the settings page of the phone
  • Press *,*,#,*,* (star, star, pound, star, star) about 1/2 second apart
  • The phone will display “Resetting” and perform a hard reset

This sequence will cause the phone to reboot as if the power cable had been unplugged and force it to pull a new configuration from CUCM.  Once common issue I find when entering this code is the keypresses not registering with the phone.  Try it a couple of times until you develop a rhythm for entering it about 1/2 second apart.  Much more than that and the phone won’t think you’re entering the code.  Quicker than that and the keys might not all register.

3.  Factory Reset – “1,2,3,4,5,6,7,8,9,*,0,#”.  When all else fails, nuke the phone from orbit.  It’s the only way to be sure.  Some settings are so difficult to change that it’s not worth it.  Or you’ve got a buggy firmware that needs to be erased.  In those cases, there is a way to completely reset a phone back to the shipping configuration.  You’ll need access to unplug the power cable, as well as enough dexterity to press buttons on the front as you plug it back in.

  • Unplug the power from the phone.
  • As you plug it back it, press and hold the “#” key.  If performed correctly, the Headset, Mute, and Speaker buttons in the lower right corner will start to flash in sequence.
  • When those three buttons start flashing in sequence, enter the following code: 1,2,3,4,5,6,7,8,9,*,0,#.  You’ll notice that’s every button on the keypad in sequence from left to right, top to bottom.
  • Phone will display “Upgrading” and erase the configuration.

4. Death trap – “ 3491672850*# ”

  • Unknown

Don’t worry if you press a key twice on accident.  The phone will still accept the code.  However, you do need to be quick about things.  The phone will only accept the factory reset code for 60 seconds after the Headset, Mute, and Speaker buttons start flashing in sequence.

[ICCD]T1 and E1 Glossary

Many of the terms listed below are directly visible in the show controllers t1 or show controllers e1 command output. For more information, refer to the document Understanding the show controllers e1 Command.

Error Events

Bipolar Violation (BPV) Error Event

A BPV error event for an alternate mark inversion (AMI)-coded signal is the occurrence of a pulse of the same polarity as the previous pulse. A BPV error event for a B8ZS- or HDB3- coded signal is the occurrence of a pulse of the same polarity as the previous pulse without being a part of the zero substitution code.

Controlled Slip (CS) Error Event

A Controlled Slip is the replication or deletion of the payload bits of a digital signal level 1 (DS1) frame. A Controlled Slip may be performed when there is a difference between the timing of a synchronous receiving terminal and the received signal. A Controlled Slip does not cause an Out of Frame defect.

Excessive Zeroes (EXZ) Error Event

An EXZ error event for an AMI-coded signal is the occurrence of more than fifteen contiguous zeroes. For a binary 8-zero substitution (B8ZS) coded signal, the defect occurs when more than seven contiguous zeroes are detected.

Line Coding Violation (LCV) Error Event

An LCV is the occurrence of either a Bipolar Violation or Excessive Zeroes error event.

Path Coding Violation (PCV) Error Event

A PCV error event is a frame synchronization bit error in the D4 and E1-no cyclic redundancy check (CRC) formats, or a CRC error in the Extended Super Frame (ESF) and E1-CRC formats.

Performance Defects

Alarm Indication Signal (AIS) Defect

For D4 and ESF links, the ‘all ones’ condition is detected at a DS1 line interface upon observing an unframed signal with a one’s density of at least 99.9 percent present for a time equal to or greater than T, where 3 ms is less than or equal to T, which is less than or equal to 75 ms. The AIS is terminated upon observing a signal not meeting the one’s density or the unframed signal criteria for a period equal to or greater than than T.

For E1 links, the ‘all-ones’ condition is detected at the line interface as a string of 512 bits containing fewer than three zero bits.

Out Of Frame (OOF) Defect

An OOF defect is the occurrence of a particular density of Framing Error events.

For T1 links, an OOF defect is declared when the receiver detects two or more framing errors within a 3 msec period for ESF signals and 0.75 msec for D4 signals, or two or more errors out of five, or fewer consecutive framing-bits.

For E1 links, an OOF defect is declared when three consecutive frame alignment signals have been received with an error.

When an OOF defect is declared, the framer starts searching for a correct framing pattern. The OOF defect ends when the signal is in-frame.

In-frame occurs when there are fewer than two frame bit errors within a 3 msec period for ESF signals and 0.75 msec for D4 signals.

For E1 links, in-frame occurs when:

  • in frame N, the frame alignment signal is correct and
  • in frame N+1, the frame alignment signal is absent (that is, bit 2 in TS0 is set to one) and
  • in frame N+2, the frame alignment signal is present and correct.

Performance Parameters

All performance parameters are accumulated in fifteen minute intervals and up to 96 intervals (covering a 24 hour period ) are kept by an agent. Fewer than 96 intervals of data will be available if the agent has been restarted within the last 24 hours. In addition, there is a rolling 24-hour total of each performance parameter.

There is no requirement for an agent to ensure a fixed relationship between the start of a fifteen minute interval and clock time; however some agents may align the fifteen minute intervals with quarter hours.

Bursty Errored Seconds (BES)

A Bursty Errored Second (also known as Errored Second type B) is a second with fewer than 320 and more than one Path Coding Violation error events, no Severely Errored Frame defects and no detected incoming AIS defects. Controlled slips are not included in this parameter.

This is not incremented during an Unavailable Second.

Controlled Slip Seconds (CSS)

A Controlled Slip Second is a one-second interval containing one or more controlled slips.

Degraded Minutes

A Degraded Minute is one in which the estimated error rate exceeds 1E-6 but does not exceed 1E-3.

Degraded Minutes are determined by collecting all of the Available Seconds, removing any Severely Errored Seconds grouping the result in 60-second long groups and counting a 60-second long group (minute) as degraded if the cumulative errors during the seconds present in the group exceed 1E-6. Available seconds are merely those seconds which are not unavailable as described below.

Errored Seconds (ES)

For ESF and E1-CRC links an Errored Second is a second with one of the following:

  • one or more Path Code Violations
  • one or more Out of Frame defects
  • one or more Controlled Slip events
  • a detected AIS defect

For D4 and E1-noCRC links, the presence of Bipolar Violations also triggers an Errored Second. This is not incremented during an Unavailable Second.

Line Errored Seconds (LES)

A Line Errored Second, according to T1M1.3, is a second in which one or more Line Code Violation error events were detected.

While many implementations are currently unable to detect the zero strings, it is expected that interface manufacturers will add this capability in deference to ANSI; therefore, it will become available in time.

In the T1M1.3 specification, near end Line Code Violations and far end Line Errored Seconds are counted. For consistency, we count Line Errored Seconds at both ends.

Severely Errored Framing Second (SEFS)

An Severely Errored Framing Second is a second with either one or more OOF defects or a detected AIS defect.

Severely Errored Seconds (SES)

A Severely Errored Second for ESF signals is a second with one of the following:

  • 320 or more Path Code Violation Error Events
  • one or more OOF defects
  • a detected AIS defect

For E1-CRC signals, a Severely Errored Second is a second with either 832 or more Path Code Violation error events or one or more OOF defects.

For E1-noCRC signals, a Severely Errored Second is a 2048 LCVs or more.

For D4 signals, a Severely Errored Second is a count of one-second intervals with Framing Error events, or an OOF defect, or 1544 LCVs or more.

Controlled slips are not included in this parameter.

This is not incremented during an Unavailable Second.

Unavailable Seconds (UAS)

Unavailable Seconds are calculated by counting the number of seconds that the interface is unavailable. The DS1 interface is said to be unavailable from the onset of ten contiguous SESs, or the onset of the condition leading to a failure (see Failure States). If the condition leading to the failure was immediately preceded by one or more contiguous SESs, then the DS1 interface unavailability starts from the onset of these SESs. Once unavailable, and if no failure is present, the DS1 interface becomes available at the onset of ten contiguous seconds with no SESs. Once unavailable, and if a failure is present, the DS1 interface becomes available at the onset of 10 contiguous seconds with no SESs, if the failure clearing time is less than or equal to ten seconds. If the failure clearing time is more than ten seconds, the DS1 interface becomes available at the onset of ten contiguous seconds with no SESs, or the onset period leading to the successful clearing condition, whichever occurs later. With respect to the DS1 error counts, all counters are incremented while the DS1 interface is deemed available. While the interface is deemed unavailable, the only count that is incremented is UASs.

A special case exists when the ten or more second period crosses the 900 second statistics window boundary, as the foregoing description implies that the Severely Errored Second and Unavailable Second counters must be adjusted when the Unavailable Signal State is entered. Successive “gets” of the affected dsx1IntervalSESs and dsx1IntervalUASs objects will return differing values if the first get occurs during the first few seconds of the window. This is viewed as an unavoidable side-effect of selecting the presently-defined managed objects.

Failure States

The following failure states are received or detected failures that are reported. The conditions under which a DS1 interface would, if ever, produce the conditions leading to the failure state are described in the appropriate specification.

Alarm Indication Signal (AIS) Failure

The Alarm Indication Signal failure is declared when an AIS defect is detected at the input and the AIS defect still exists after the Loss Of Frame failure (which is caused by the unframed nature of the ‘all-ones’ signal) is declared. The AIS failure is cleared when the Loss Of Frame failure is cleared.

Far End Alarm Failure(Yellow Alarm)

The Far End Alarm failure is also known as a Yellow Alarm in the T1 case and a Distant Alarm in the E1 case.

For D4 links, the Far End Alarm failure is declared when bit 6 of all channels has been zero for at least 335 ms and is cleared when bit 6 of at least one channel is non-zero for a period T, where T is usually less than one second and always less than five seconds. The Far End Alarm failure is not declared for D4 links when a Loss of Signal is detected.

For ESF links, the Far End Alarm failure is declared if the Yellow Alarm signal pattern occurs in at least seven out of ten contiguous 16-bit pattern intervals and is cleared if the Yellow Alarm signal pattern does not occur in ten contiguous 16-bit signal pattern intervals.

For E1 links, the Far End Alarm failure is declared when bit 3 of time-slot zero is received set to one on two consecutive occasions. The Far End Alarm failure is cleared when bit 3 of time-slot zero is received set to zero.

Far End Loss Of Multiframe Failure

The Far End Loss Of Multiframe failure is declared when bit 2 of TS16 of frame 0 is received set to one on two consecutive occasions. The Far End Loss Of Multiframe failure is cleared when bit 2 of TS16 of frame 0 is received set to zero. The Far End Loss Of Multiframe failure can only be declared for E1 links operating in Channel Associated Signalling mode.

Loopback Pseudo-Failure

The Loopback Pseudo-Failure is declared when the near end equipment has placed a loopback (of any kind) on the DS1. This allows a management entity to determine from one object whether the DS1 can be considered to be in service or not (from the point of view of the near end equipment).

Loss Of Frame(LOF) Failure

For T1 links, the Loss Of Frame failure is declared when an OOF or LOS defect has persisted for T seconds, where T is more than or equal to two, but less than or equal to ten. The Loss Of Frame failure is cleared when there have been no OOF or LOS defects during a period T is more than or equal to zero, but less than or equal to twenty. Many systems will perform “hit integration” within the period T before declaring or clearing the failure.

For E1 links, the Loss Of Frame Failure is declared when an OOF defect is detected.

Loss Of MultiFrame Failure

The Loss Of MultiFrame failure is declared when two consecutive multiframe alignment signals (bits 4 through 7 of TS16 of frame 0) have been received with an error. The Loss Of Multiframe failure is cleared when the first correct multiframe alignment signal is received. The Loss Of Multiframe failure can only be declared for E1 links operating with framing (sometimes called Channel Associated Signalling mode).

Loss Of Signal (LOS) Failure

For T1, the Loss Of Signal failure is declared upon observing 175 +/- 75 contiguous pulse positions with no pulses of either positive or negative polarity. The LOS failure is cleared upon observing an average pulse density of at least 12.5 percent over a period of 175 +/- 75 contiguous pulse positions starting with the receipt of a pulse.

For E1 links, the Loss Of Signal failure is declared when greater than ten consecutive zeroes are detected.

TS16 Alarm Indication Signal Failure

For E1 links, the TS16 Alarm Indication Signal failure is declared when time-slot 16 is received as all ones for all frames of two consecutive multiframes. This condition is never declared for T1.

[LEGO]穷三代 42078+42082

[WWB] Oh 365 ~

How to determine the connection of application

Start  “Task Manager”—click  “Processes”—select “PID” box in “view-select Colunms”

Find out the PID of the application

Input the command “ netstat –ano | findstr “PID”

—————— pac file ——–

function FindProxyForURL(url, host)

{

    url = url.toLowerCase();

    host = host.toLowerCase();

                //——————————————————-

                // Traffic should go via proxy

                //——————————————————-

                if (

                                shExpMatch(host, “163.44.159.68”) ||   //Entry for this VPS

                                shExpMatch(host, “*.kkmg.vip”) ||       //Entry for this VPS

                                )

                return “PROXY 127.0.0.1:1080”;

    // Default Traffic Forwarding

     return ” DIRECT “;

}

[ICCD]Extension Mobility Error Codes

Extension Mobility Application Error Codes

Table 1 Extension Mobility Application Error Codes
Error Code Phone Display Quick Description Reason
201 Please try to login again (201) Authentication Error If the user is an EMCC user, this error can occur if “EMCC” is not activated on the Intercluster Service Profile window.
202 Please try to login again (202) Blank userid or pin The user enters a blank user ID or PIN.
204 Login is unavailable (204) Directory server error The EMApp sends this error to the phone when IMS could not authenticate the user with the given PIN.
205 Login is unavailable (205)

Logout is unavailable (205)

User Profile Absent Occurs when the user profile information cannot be retrieved from the cache or the database.
207 Login is unavailable(207)

Logout is unavailable(207)

Device Name Empty Occurs when the device or name tag is missing in the request URI. This cannot happen with real devices and can occur only if the request is sent from third-party applications.
208 Login is unavailable(208)

Logout is unavailable(208)

EMService Connection Error The visiting EMApp cannot connect to any Visiting EMService. (The service is down or not activated.)

The visiting EMService cannot connect to the Home EMService (the WAN is down or certificates are not trusted.)

210 Login is unavailable(210)

Logout is unavailable(210)

Init Fail-Contact Admin An error (such as a database connection failure) occurred while initializing EMApp. The error can occur because of a failure to connect to the database during startup.
211 Login is unavailable(211)

Logout is unavailable(211)

EMCC Not Activated Occurs when the PSTN is not activated in the Intercluster Service Profile window of the visiting cluster.
212 Login is unavailable(212) Cluster ID is invalid Occurs when a remote cluster update fails by sending an incorrect cluster ID to the remote cluster.
213 Login is unavailable(213)

Logout is unavailable(213)

Device does not support EMCC Occurs when a device does not support EMCC.

Extension Mobility Service Error Codes

Table 2 Extension Mobility Service Error Codes
Error Code Phone Display Quick Description Reason
0 Login is unavailable(0)

Logout is unavailable(0)

Unknown Error The EMService failed for an unknown reason.
1 Login is unavailable(1)

Logout is unavailable(1)

Error on parsing When the EMService cannot parse the XML request from the EMApp or EMService. This error occurs when third-party applications send an incorrect query to login XML (EM API). The error can also occur because of a version mismatch between home and visiting clusters.
2 Login is unavailable(2) EMCC Authentication Error The EMCC user credentials cannot be authenticated because the user entered an incorrect PIN.
3 Login is unavailable(3)

Logout is unavailable(3)

Invalid App User Invalid application user. This error commonly occurs because of the EM API.
4 Login is unavailable(4)

Logout is unavailable(4)

Policy Validation error The EM Service sends this error when it cannot validate the login or logout request because of an unknown reason, an error while querying the database or an error while retrieving information from the cache.
5 Login is unavailable(5)

Logout is unavailable(5)

Dev. logon disabled A user logs into a device that has Enable Extension Mobility unchecked in the Phone Configuration window.
6 Login is unavailable(6)

Logout is unavailable(6)

Database Error Whenever the database returns an exception while executing the query or stored procedure that the EM Service requests (login/logout or device/user query), the EM Service sends this error code to EMApp.
8 Login is unavailable(8)

Logout is unavailable(8)

Query type undetermined No valid query was sent to the EMService (DeviceUserQuery and UserDeviceQuery are valid ones). This error occurs because of the EM API or incorrect XML input.
9 Login is unavailable(9)

Logout is unavailable(9)

Dir. User Info Error This error appears in two cases:

  1. IMS returns an exception when it attempts to authenticate a user.
  2. When information about a user cannot be retrieved either from the cache or database.
10 Login is unavailable(10)

Logout is unavailable(10)

User lacks app proxy rights The user tries to log in on behalf of another user. By default, a CCMSysUser has administrative rights.
11 Login is unavailable(11)

Logout is unavailable(11)

Device Does not exist The phone record entry is absent in the device table.
12 Phone record entry is absent in the device table Dev. Profile not found No device profile is associated with the remote user.
18 Login is unavailable(18) Another user logged in Another user is already logged in on the phone.
19 Logout is unavailable(19) No user logged in The system attempted to log out a user who has not logged in. This error occurs when sending logout requests from third-party applications (EM API).
20 Login is unavailable(20)

Logout is unavailable(20)

Hoteling flag error Enable Extension Mobility is unchecked in the Phone Configuration window.
21 Login is unavailable(21)

Logout is unavailable(21)

Hoteling Status error The current user status was not retrieved from either the local cache or database.
22 Login is unavailable(22) Dev. logon disabled Occurs when EM is not enabled on device and the request is sent via EM API or when the services button is pressed on phone.
23 Login is Unavailable (23)

Logout is Unavailable (23)

User does not exist Occurs when the given user ID is not found (in any of the remote clusters).
25 Login is unavailable(25) User logged in elsewhere The user is currently logged in to some other phone.
26 Login is unavailable(26)

Logout is unavailable(26)

Busy, please try again Occurs when the EMService has currently reached the threshold level of Maximum Concurrent Requests service parameter.
28 Login is unavailable(28)

Logout is unavailable(28)

Untrusted IP Error Occurs when the Validate IP Address service parameter is set to True and the user tries to log in or log out from a machine whose IP address is not trusted. For example, a third-party application or EM API from a machine is not listed in the Trusted List of Ips service parameter.
29 Login is unavailable(29)

Logout is unavailable(29)

ris down-contact admin The Real-Time Information Server Data Collector (RISDC) cache is not created or initialized, and the EMService is unable to connect to RISDC.
30 Login is unavailable(30)

Logout is unavailable(30)

Proxy not allowed When login and logout occur through proxy (“Via” is set in HTTP header) and the Allow Proxy service parameter is set to False.
31 Login is unavailable(31)

Logout is unavailable(31)

EMCC Not Activated for the user Occurs when the Enable Extension Mobility Cross Cluster check box is not checked in the End User Configuration window of the home cluster.
32 Login is unavailable(32)

Logout is unavailable(32)

Device does not support EMCC Occurs when a device model does not have EMCC capability.
33 Login is unavailable(33)

Logout is unavailable(33)

No free EMCC dummy device Occurs when all the EMCC dummy devices are in use by other EMCC logins.
35 Login is unavailable(35)

Logout is unavailable(35)

Visiting Cluster Information is not present in Home Cluster Occurs when the home cluster does not have an entry for this visiting cluster.
36 Login is unavailable(36)

Logout is unavailable(36)

No Remote Cluster Occurs when the administrator has not added a remote cluster.
37 Login is Unavailable (37)

Logout is Unavailable (37)

Duplicate Device Name Occurs when the same device name exists in both the home cluster and visiting cluster.
38 Login is unavailable(38)

Logout is unavailable(38)

EMCC Not Allowed Occurs when the home cluster does not want to allow EMCC login (The Enable Extension Mobility Cross Cluster check box is not checked in the home cluster).
43 Login is unavailable(43) Device Security mode error The Device Security Profile that is associated to the EMCC device should be set to Nonsecure for its Device Security Mode.
45 Login is unsuccessful(45) Remote Cluster version not supported Occurs during EMCC login when the visiting cluster version is 9.x and is in mixed mode, the phone is in secure mode, and the home cluster version is 8.x.
46 Login is unsuccessful(46) Remote Cluster security mode not supported Occurs during EMCC login when the visiting cluster security mode is in mixed mode, the phone is in secure mode, and the home cluster is in nonsecure mode.

 

Read More…

[ICCD] Wildcards and Special Characters in Translation Pattern

Character Description Examples
@ (@) 通配符匹配 所有 National Numbering Plan numbers.

每个 route pattern 只允许存在1个@ 通配符.

Route pattern ‘9.@’ 可以 routes 或者 blocks 所有 National Numbering Plan 可以识别的号码.

下列的 route patterns examples 显示了通配符 @ 包含的 National Numbering Plan numbers:

  • 0
  • 1411
  • 19725551234
  • 101028819725551234
  • 01133123456789
X (X)通配符表示匹配范围从0到9的任何单个数字 Route pattern ‘9XXX’ 可以 routes 或 blocks 范围从9000 到 9999的所有号码.
!  (!) 通配符表示匹配 范围从0到9的单个或任意多个数字. Route pattern ‘91!’ 可以routes 或 blocks 范围从 910 到 91999999999999999999999的所有号码.
? (?) 通配符表示匹配值的零个或多个的出现. Route pattern ‘91X?’ 可以 routes或blocks 范围从91 到 91999999999999999999999 的所有号码.
+  (+)通配符表示匹配值的一个或多个的出现. Route pattern ‘91X+’ 可以 routes 或 blocks 范围从 910 到 91999999999999999999999的所有号码.
[ ] ([ ]) 通配符表示匹配这几个数字内的一个. Route pattern ‘813510[012345]’ 可以 routes 或 blocks 范围从8135100 到 8135105的所有号码.
(-) 通配符与 方括号 一起使用,表示一个值的范围. Route pattern ‘813510[0-5]’ 可以 routes 或 blocks 范围从8135100 到 8135105 的所有号码.
^  (^) 通配符与 方括号 一起使用, 表示否定这一系列的值.

务必确保该通配符为方括号后的第一个字符 ([).

另外每个 route pattern 只允许有一个(^)通配符.

Route pattern ‘813510[^0-5]’ 可以 routes 或 blocks 范围从8135106 至8135109的所有号码.
. (.) 通配符,用作分隔符,多 用于在Cisco Unified Communications Manager(CUCM)从号码(directory number)区分出access code.

使用这个特殊通配符, 配合丢弃数字操作(discard digits),可以在 Cisco Unified Communications Manager(CUCM) 将号码发出前将 access code 剥离.

每个 route pattern 只允许有一个 (.) 通配符.

Route pattern ‘9.@’ 可以识别出 9 是一个 Cisco Unified Communications Manager 在National Numbering Plan 的一个 access code.
*  (*) 通配符可以为特殊拨号号码提供额外的数字. 可以配置route pattern ‘*411’ 可以拨打到任何号码的内部拨号.
#  (#) 通常表示拨号操作的结束.

确保# 通配符是位于这个pattern最后一个.

Route pattern ‘901181910555#’ 可以routes 或 blocks 从National Numbering Plan 的一个国际呼叫. 这里的 (#)通配符表示之前的(5)是呼叫队列中的最后一个数字.
\+ 反斜杠后的一个加号,就是(\+)通配符,表示你想要配置国际转义符+.

使用 (\+) 表示这里的 (+) 是国际转移符号用 可以拨打的,不是作为(+)通配符使用.

具体案例, 参考 Use the International Escape Character.

 

Read More…

【风险投资】10年理财产品

  • 产品代码:EVE
  • 产品类别:大型3D在线聊天类
  • 发售起始日期:2008-06-22 12:26
  • 发售截止日期:20XX-XX-XX XX:XX
  • 产品到期日:2018-02-28
  • 预期收益率:?%
  • 投资类型:呵呵
  • 风险评级:RX(??型)
  • 销售渠道:网上
  • 币种:ISK

08年的号到现在,看图说话系列,有意向直接留言

资产(这物价GG)

Hello World !!

新域名测试用. 顺大便.org之后的第一篇文章而已 

另外的话就再安利下Bluesky Frame Rate Converter这个好东西吧,简称BFRC,定义的话 A卡泛用性插帧工具把视频重新补回60fps

  • 所以首先你要有张A卡 并且支持AFM [AMD Fluid Motion],所以有就有了,没有就别往下看了

  • 然后去下载配置BlueskyFRC

                 下载地址:http://bluesky23.yukishigure.com/BlueskyFRC.html

也没啥要配置的,默认这里是现实Enable AFM support 点完会要你重启,再次打开就如图的Initalize AFM support

 

  • 最后设置播放器

我就用potplayer举个栗子了

打开potplayer – F5 设置 – 滤镜 – 全局滤镜优先权 – 添加外部滤镜 – 找到刚刚下载的BFRC的滤镜

优先顺序 – 强制使用

选择视频解码器-内置解码器/DXVA设置 – 勾选 使用硬件加速 

重新打开potplayer即可Done

  • 最后找个视频试下 

可以看到,视频已经被补到了60fps,而观感也得到了一定的提升,类似于看游戏CG一样,一开始可能会不适应这种60fps视频

另外实测有些视频不能成功加速但通过A卡DP口连4K电视能也能自动补帧

 

虽然显示25fps 但能感觉到加速

 

游戏也是 我严重怀疑游戏的FPS也是被补帧补上去的

另外这错觉的确是A卡造成的 如果连我笔记本的N卡没半毛钱特效

 

Great New! No What ?

不知道你有没有留意过第五代极品飞车叫啥,保时捷之旅。

自那时候开始,保时捷和EA的合作协议就是独占授权,所以只有极品飞车家的一直有保时捷的车型,而其他家的要嘛没有,要嘛就是挂着RUF标志的破鞋。然而协议在去年年底到期后,今年新开发的游戏均可以期待保时捷车型的加入。

微软反应最快,不仅把Forza 7的封面定了破鞋,还给Horizon3 上了破鞋的DLC车包,

 

如果不想花钱的话,每月的限时任务[FORZATHON]也能获得大量车包外的车(918 、944 、GT2 、GT3 RS 、Carrera GT、Cayman、MaCan、Cayenne)

 

当然都扯到Horizon3了就叙叙旧了,对于玩RAC从NFS2开始玩到现在NFS19 一路键盘操作过来的PC-er 来说,特别是沉迷 Codemaster家的 GRID和DiRT 系列并有了键盘能应付一切的错觉,这是第一款让我入了个手柄并且很棒的体验,也很推荐入个Xbox的杆子,毕竟都是微软家的,LT/RT线性控制以及独立的震动反馈,大可以把残疾人辅助的ABS和TCR关了,肌肉车或者大马力FR出弯再也不怕甜甜圈了。

Horizon3另外特色的话就是游戏社区的Dalao吧,默认的改车选项及喷漆彩绘并没啥特色,但有了dalao的分享,合理运用社区系统支持的搜索功能 关键字[niconico··呸,啥玩意 ,shimakaze 嗯 之类的],同样分享的调校配置也是同样能够得到的,配合周常任务[FORZATHON]这游戏的生命周期∞

每周都会刷新FORZAthon的任务,比如这周又送辆破鞋

当然959还是有些有趣的历史,有兴趣的同学可以去补补

 

顺便也展示下这游戏的大改

原厂水平六缸可以换混动V8,这数据瞬间就不对了

如果要作大死的话 是可以换成后置后驱 , 想了想电力机恐怖的低速扭矩,额 我还是残疾人得用四驱了

 

和Dalao比,我就简单涂两下了吧 – –

 

游戏画面的话的确不错了,但来和NFS19比一下的话 确差了点,毕竟寒霜不是吹的。虽然都是科迈罗,上面的是17款的ZL1 ,NFS为14款的Z28[NFS没有车内第一人称视角]

NFS19的话给了一种重回Underground的感觉,剧情模式的代入,改大包围,贴纸彩绘也不错,车辆的调校也简直残疾人辅助级别的了。

但我没找到搜索,所以你懂的差评了。可选的车也不多,但想想这些都支持这样的大改,嗯还行,当然也佩服自己能把辆美系肌肉贴成这样

 另外你的好友井茶蜀黍也已上线,游戏中操作反馈也不咋地,也没有砖家模式,漂移的感觉回到了10代,漂移辅助还会导致方向输入消失,我本来以为杆子问题,键盘手操也会有,另外种解释有可能有个高延迟玩家在附近。

 

毕竟头大的话就是全程联网模式,自己的一个私人赛事也会因为全局有玩家路过,延迟了飘啊飘挤出线路,更会碰上怒路的直接怼弯道闸口搞事了。

最要命的话应该算育碧的Crew了,CREW我是UBI30周年领的,然后去年有个CALLING ALL UNIT的DLC感觉不错,就一起入了。

玩了一会儿之后,这游戏的感觉就是《飙车》[挺古董的游戏,但就是这样的感觉],主线剧情其实就是个复仇剧情具体也不剧透了,游戏地图是大,整个美国,而且赛事安排有点乱,路上走好好的触发了一个小游戏,但画面细节和操作反馈再次证明这个就是《飙车》。而且Ubi的游戏还是本地运算,抓个人简直AntiFun啊。

改车是按照比赛类似改,街车、越野、赛道……,涂装的话也是限定死的,育碧设计,自己能任意改的大改就是个自定义底色了吧,而且玩到现在头一个RAC游戏 要自己回车库付费修车的

第一人称雨天的小细节不错,仅此而已。

Crew是14年年底上市的,打了16年的Calling all unit DLC,还是感觉13年年底的NFS18好一大截。而且NFS18还是没剧情的就无脑互怼。

 

当然就是因为有这么些别扭,有些游戏基本没玩超过50个小时,同样我有驾照但没去过赛道跑过,最快也就开过160kph,所以如果你是Dalao,看了之后想Bibi&……¥#,就算了吧,当做来混个浏览量吧。