{"id":642,"date":"2013-09-17T00:07:12","date_gmt":"2013-09-16T15:07:12","guid":{"rendered":"http:\/\/www.tciskfactory.com\/blog\/?p=642"},"modified":"2026-10-29T16:30:39","modified_gmt":"2026-10-29T07:30:39","slug":"google-voice-obi","status":"publish","type":"post","link":"https:\/\/blog.coppe.jp\/en\/2013\/09\/17\/google-voice-obi\/","title":{"rendered":"Upgrade your Google Voice-compatible OBI to support Caller ID."},"content":{"rendered":"<p>OBiHai Technology&#039;s ATA has excellent cloud configuration capabilities, but there is a problem where CallerID (number display) is not displayed when used in the environment of existing telephones in Japan. We are working with OBi to resolve this issue.<a title=\"We have made a strong request to OBiHai Technology to improve the device for the Japanese market! (2)\" href=\"https:\/\/blog.coppe.jp\/en\/web\/ip-pbx\/%e3%83%87%e3%83%90%e3%82%a4%e3%82%b9%e3%81%ae%e6%97%a5%e6%9c%ac%e4%bb%95%e6%a7%98%e6%94%b9%e8%89%af%e3%82%92obihai-technplogy%e3%81%ab%e9%8b%ad%e6%84%8f%e4%be%9d%e9%a0%bc%ef%bc%812.html\/\">We have made a strong request to OBiHai Technology to improve the device for the Japanese market! (2)<\/a>However, we received good news regarding this matter from the technical staff in Silicon Valley.<\/p>\n<p>&quot;I think I&#039;ve managed to get it displaying correctly, so could you please check it?&quot; they said. I quickly skimmed through the email and saw that there were a lot of things to check.<\/p>\n<p>First, I had them access several OBi devices installed in my office and rewrite the firmware to the dedicated one. After receiving the message &quot;Done!!&quot;, I immediately accessed the configuration screen and found that &quot;NTT (Japan)&quot; was now available as a selection option in Phone Port Settings! I selected this, and also changed the Polarity Settings to &quot;Opposite&quot;, and saved. Just to be safe, I restarted the device, then connected an older Sanyo phone from Japan and tried making a call.<\/p>\n<p><img loading=\"lazy\" decoding=\"async\" class=\"aligncenter size-medium wp-image-644\" alt=\"COLLECT_CID2\" src=\"https:\/\/blog.coppe.jp\/app\/uploads\/COLLECT_CID2-300x225.jpg\" width=\"300\" height=\"225\" \/>Wow, I did it! The numbers are displayed correctly! Amazing!<\/p>\n<p>Actually, this phone is quite old, and the Japanese caller ID technology standards are from a very early stage. Even Grandstream&#039;s ATA couldn&#039;t display Japanese caller ID, but the OBi technical staff made it possible. That&#039;s amazing!<\/p>\n<p>Next, I connected it to a SHARP fax machine that meets current technical standards and tried making a call again.<\/p>\n<p><img loading=\"lazy\" decoding=\"async\" class=\"aligncenter size-medium wp-image-645\" alt=\"misconversion\" src=\"https:\/\/blog.coppe.jp\/app\/uploads\/misconversion-300x225.jpg\" width=\"300\" height=\"225\" \/>Pressure pressure experience memory resistance * ... It&#039;s garbled text!?<\/p>\n<p>Current Japanese telephones are, of course, capable of displaying fonts that conform to the JIS standard. The problem lies in the encoding, which is causing all the displayed phone numbers to appear as misconversions. This is not a simple matter...<\/p>\n<p>I completed all other requested checks and provided feedback to the technical staff, along with a request to resolve the character encoding issue.<\/p>\n<p>He also said, &quot;Japan is thoroughly &#039;isolationist&#039;.&quot; I agree. It&#039;s truly a Galapagos. In recent years, mobile phones have finally become smartphones, and standards are gradually becoming globalized, but in reality, we&#039;re only reluctantly following global standards because we&#039;re forced to, so our progress is uneven and slow. I vented my frustrations about such things to him.<\/p>\n<p>However, the replies from the Silicon Valley tech staff aren&#039;t exactly fast either. Of course, I didn&#039;t say this out loud. It&#039;s a tricky situation...<\/p>","protected":false},"excerpt":{"rendered":"<p>OBiHai has excellent cloud configuration capabilities\u2026<\/p>","protected":false},"author":5,"featured_media":2212,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[1],"tags":[],"class_list":["post-642","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-uncategorized"],"_links":{"self":[{"href":"https:\/\/blog.coppe.jp\/en\/wp-json\/wp\/v2\/posts\/642","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/blog.coppe.jp\/en\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/blog.coppe.jp\/en\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/blog.coppe.jp\/en\/wp-json\/wp\/v2\/users\/5"}],"replies":[{"embeddable":true,"href":"https:\/\/blog.coppe.jp\/en\/wp-json\/wp\/v2\/comments?post=642"}],"version-history":[{"count":1,"href":"https:\/\/blog.coppe.jp\/en\/wp-json\/wp\/v2\/posts\/642\/revisions"}],"predecessor-version":[{"id":2318,"href":"https:\/\/blog.coppe.jp\/en\/wp-json\/wp\/v2\/posts\/642\/revisions\/2318"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/blog.coppe.jp\/en\/wp-json\/wp\/v2\/media\/2212"}],"wp:attachment":[{"href":"https:\/\/blog.coppe.jp\/en\/wp-json\/wp\/v2\/media?parent=642"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/blog.coppe.jp\/en\/wp-json\/wp\/v2\/categories?post=642"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/blog.coppe.jp\/en\/wp-json\/wp\/v2\/tags?post=642"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}