woojar

本周最大的事情莫过于台湾南部海域发生的7.2级大地震了，本次地震虽未对台湾同胞造成太大的伤害，但对中国的互联网却造成了极大的伤害。因为发生地震的海域刚好是中国互联网连通国际互联网的光缆所在地，那么我们国内访问国外的网站就中断了，MSN也上不了(真是垃圾软件呀)，查询资料也受到很大的影响。国内的COM域名网站也受到了不同程度的影响，因为COM域名的根服务器在美国放着，即使你的网站，IP是中国的，但要解析还是要到美国走一圈，哎，没办法谁让人家美国先有计算机呢。看来国内的网站如果只对国内的用户的话还是用CN域名安全些。

听说要一到两周光缆才能修好，希望快点修好，要不我们通往世界的大门就要紧闭了。。。

元旦放假了，今年的元旦刚好在星期一，那么就可以和星期六星期天一块休了，但变态的是国家却规定要123放假，所以我老婆还要上班，我也只能一个在家休息了。

去医院检查了身体，啥事没有，就是有点脂肪肝，看来是生活水平有点高嘛，看来还是少吃点油，多锻炼身体为好。

回来的路上路过移动厅，办个移动钱包吧，听说可以通过银行卡充值，不错!可以省去找店充值的麻烦。办的时候还需要实名制，只好改了原来手机的名字来了个实名。办完以后，为老婆试充了100块钱，是很方便。
但看看手机钱包的其它功能，缴水电费啦，买股票啦，为别人手机充值啦等，看来功能还真不少。我突然想到，如果我手机丢了，别人就好象捡到了一个银行卡，如果一不小心的话又被人家弄到了手机钱包密码，那就麻烦了。看来密码还是小心保存好。
任何方便的事总有一定风险的，看来。

Technorati : 手机钱包 安全

You can download the configuration guide of CISCO 7905 from this link

Today we converted sccp firmware to sip on CISCO 7905 phone. Before do that we should understand the cisco ip phone boot process.

Initialization Process Overview

The initialization process of the Cisco SIP IP phone is responsible for establishing network connectivity and for making the phone operational in your IP network.

Once you connect your phone to the network and to an electrical supply, the phone begins its initialization process.

During the initialization process, the following events take place:

1. The stored image is loaded.

The Cisco SIP IP phone has non-volatile Flash memory in which it stores the firmware images, user-defined preferences, and permanent factory information about the phone.

During initialization, the phone runs a bootstrap loader that loads and executes the phone image stored in Flash memory.

2. The VLAN is configured.

If the Cisco SIP IP phone is connected to a Catalyst switch, the switch notifies the phone of the voice VLAN defined on the switch. The phone needs to know its VLAN membership before it can proceed with the DHCP request for its IP settings (if using DHCP).

3. An IP address is acquired.

If the Cisco SIP IP phone is using DHCP to obtain the IP settings, the phone queries the DHCP server. If the phone is not using DHCP, then the phone will use IP settings that are stored in Flash memory.

4. The TFTP server is contacted.

On the TFTP server is the latest Cisco SIP IP phone firmware image and the dual boot file (OS79XX.TXT) that enables the phone to automatically determine and initialize for the VoIP environment in which it is being installed.

If the phone is using the TFTP server to obtain its SIP parameters, there should also be a configuration file or files on the TFTP server that the phone will request and download. In the configuration file or files, SIP parameters that are required by the phone to operate in a SIP VoIP environment are defined. If the phone is not obtaining its SIP parameters via the TFTP server, the phone will use SIP settings that are stored in Flash memory.

5. The firmware version is verified.

If the phone is obtaining its SIP parameters via a TFTP server, the configuration files are requested. If the phone determines that the image defined in a configuration file differs from the image it has stored in Flash memory, it performs a firmware upgrade.

When performing a firmware upgrade, the phone downloads the firmware image from the TFTP server, programs the image into Flash memory, and reboots. <from CISCO>

Remember to change the item “image_version” to fit your imag name in file SIPmacaddress.cnf.
The detail steps we can refer to CISCO Site

Technorati : 7960 sip firmware

Matching Outbound Dial Peers

If DID is configured in the inbound POTS dial peer, the router uses the full incoming dial string to match the destination pattern in the outbound dial peer. With DID, the setup message contains all the digits necessary to route the call; no additional digit collection is required. If more than one dial peer matches the dial string, all of the matching dial peers are used to form a rotary group. The router attempts to place the outbound call leg using all of the dial peers in the rotary group until one is successful. From http://www.cisco.com/univercd/cc/td/doc/product/software/ios123/
123 cgcr/vvfax_c/int_c/dpeer_c/dp_confg.htm#wp1067791