Woody Home Page
 
   
AR168G IP phone
  
Jan 27, 2007
Digitmat has become the 3rd company to offer AR1688 based IP phones after Yuxin and High-link. We are expecting more than 10 manufacturers in the future months.
GP1260 IP phone from Digitmat is based on our AR168G reference design. Unlike free AR168F, AR168G is provided with extra supporting fee. It uses 132x64 dot matrix display, the software can be more fancy than 2x16 character LCD display, and can support Chinese and other special chars not included in standard ASCII table. AR168G also support more keys, for example, max 10 speed dial.

Comments for this page:

dungvt@postef.com.vnposted on 2012-03-05 03:52:18 113.160.16.218
Dear Woody

Just ask you that we have IP phone with phone model is AR168P, version 0.45.006 and which API they using?

Now we need those API to change something to our customer

dungvt@postef.com.vnposted on 2012-03-05 05:41:41 113.160.16.218
i just build the ar168p from ar1688 api 056 is ok.

But when i flash to IP phone completed then i can't use any functions?

Have any wrong here? And how to recover it?

I can't ping, enter web page,... enter the phone for recover or reset to default?

Woodyposted on 2012-03-05 07:29:14 125.33.177.132
Try safe mode recovery, it should be always working.
We can not figure out what was wrong in your compile process, please provide more information like detail command line output.

dungvt@postef.com.vnposted on 2012-03-05 09:02:11 113.160.16.218
Dear Woody

Just try to safe mode then set "#5*5" but can't get the IP address or ping to IP phone. Can't use any function in IP phone.

Please help me more

"
C:\sdcc\src>mk ar168p sip vn

C:\sdcc\src>attrib -r ..\include\version.h

C:\sdcc\src>..\bin\reversion ..\include\version.h ar168p sip vn
Palmmicro reversion utility 0.55.011

C:\sdcc\src>attrib -r linkmain.lnk

C:\sdcc\src>..\bin\relink linkmain.lnk ar168p sip vn
Palmmicro AR1688 relink utility 0.55.015

C:\sdcc\src>..\bin\make
C:\SDCC\BIN\sdcc main.c -mz80 -c --std-c99 --codeseg CODE0
C:\SDCC\BIN\sdcc ce3.c -mz80 -c --std-c99 --codeseg CODE0
C:\SDCC\BIN\sdasz80 -plosgff datatype.rel datatype.s
C:\SDCC\BIN\sdcc dm9000.c -mz80 -c --std-c99 --codeseg CODE0
C:\SDCC\BIN\sdcc isr_gpio.c -mz80 -c --std-c99 --codeseg CODE0
C:\SDCC\BIN\sdcc ksz8842.c -mz80 -c --std-c99 --codeseg CODE0
C:\SDCC\BIN\sdcc lcd.c -mz80 -c --std-c99 --codeseg CODE0
C:\SDCC\BIN\sdasz80 -plosgff math.rel math.s
C:\SDCC\BIN\sdcc ne2000.c -mz80 -c --std-c99 --codeseg CODE0
C:\SDCC\BIN\sdcc font.c -mz80 -c --std-c99 --codeseg CODEF
C:\SDCC\BIN\sdcc buf.c -mz80 -c --std-c99 --codeseg CODE
C:\SDCC\BIN\sdcc data.c -mz80 -c --std-c99 --codeseg CODE
C:\SDCC\BIN\sdcc heap.c -mz80 -c --std-c99 --codeseg CODE
C:\SDCC\BIN\sdcc line.c -mz80 -c --std-c99 --codeseg CODE
C:\SDCC\BIN\sdcc misc.c -mz80 -c --std-c99 --codeseg CODE
C:\SDCC\BIN\sdcc options.c -mz80 -c --std-c99 --codeseg CODE
C:\SDCC\BIN\sdcc rand.c -mz80 -c --std-c99 --codeseg CODE
C:\SDCC\BIN\sdcc sipc.c -mz80 -c --std-c99 --codeseg CODE
C:\SDCC\BIN\sdcc syslog.c -mz80 -c --std-c99 --codeseg CODE
C:\SDCC\BIN\sdcc udpdebug.c -mz80 -c --std-c99 --codeseg CODE
C:\SDCC\BIN\sdcc adc_key.c -mz80 -c --std-c99 --codeseg CODE1
C:\SDCC\BIN\sdcc dtmf.c -mz80 -c --std-c99 --codeseg CODE1
C:\SDCC\BIN\sdcc function.c -mz80 -c --std-c99 --codeseg CODE1
C:\SDCC\BIN\sdcc gpio_key.c -mz80 -c --std-c99 --codeseg CODE1
C:\SDCC\BIN\sdcc hook.c -mz80 -c --std-c99 --codeseg CODE1
C:\SDCC\BIN\sdcc ivr.c -mz80 -c --std-c99 --codeseg CODE1
C:\SDCC\BIN\sdcc led.c -mz80 -c --std-c99 --codeseg CODE1
C:\SDCC\BIN\sdcc serial.c -mz80 -c --std-c99 --codeseg CODE1
C:\SDCC\BIN\sdcc slic.c -mz80 -c --std-c99 --codeseg CODE1
C:\SDCC\BIN\sdcc time.c -mz80 -c --std-c99 --codeseg CODE1
C:\SDCC\BIN\sdcc dhcp.c -mz80 -c --std-c99 --codeseg CODE2
C:\SDCC\BIN\sdcc dns.c -mz80 -c --std-c99 --codeseg CODE2
C:\SDCC\BIN\sdcc net.c -mz80 -c --std-c99 --codeseg CODE2
C:\SDCC\BIN\sdcc ppp.c -mz80 -c --std-c99 --codeseg CODE2
C:\SDCC\BIN\sdcc pppoe.c -mz80 -c --std-c99 --codeseg CODE2
C:\SDCC\BIN\sdcc sntp.c -mz80 -c --std-c99 --codeseg CODE2
C:\SDCC\BIN\sdcc stun.c -mz80 -c --std-c99 --codeseg CODE2
C:\SDCC\BIN\sdcc tftp.c -mz80 -c --std-c99 --codeseg CODE2
C:\SDCC\BIN\sdcc http.c -mz80 -c --std-c99 --codeseg CODE3
C:\SDCC\BIN\sdcc httpc.c -mz80 -c --std-c99 --codeseg CODE3
C:\SDCC\BIN\sdcc ap_innom.c -mz80 -c --std-c99 --codeseg CODE3
C:\SDCC\BIN\sdcc call_log.c -mz80 -c --std-c99 --codeseg CODE4
C:\SDCC\BIN\sdcc menu.c -mz80 -c --std-c99 --codeseg CODE4
C:\SDCC\BIN\sdcc settings.c -mz80 -c --std-c99 --codeseg CODE4
C:\SDCC\BIN\sdcc ui_str.c -mz80 -c --std-c99 --codeseg CODE4
res\\vn\\menu.h:8: warning 147: excess elements in array of chars initializer af
ter '_cMainMenu'
res\\vn\\menu.h:8: warning 147: excess elements in array of chars initializer af
ter '_cMainMenu'
res\\vn\\menu.h:8: warning 147: excess elements in array of chars initializer af
ter '_cMainMenu'
res\\vn\\menu.h:16: warning 147: excess elements in array of chars initializer a
fter '_cTestMenu'
res\\vn\\menu.h:23: warning 147: excess elements in array of chars initializer a
fter '_cCallMenu'
res\\vn\\menu.h:33: warning 147: excess elements in array of chars initializer a
fter '_cSettingsMenu'
res\\vn\\menu.h:33: warning 147: excess elements in array of chars initializer a
fter '_cSettingsMenu'
res\\vn\\menu.h:45: warning 147: excess elements in array of chars initializer a
fter '_cInfoMenu'
res\\vn\\menu.h:45: warning 147: excess elements in array of chars initializer a
fter '_cInfoMenu'
res\\vn\\menu.h:75: warning 147: excess elements in array of chars initializer a
fter '_cNetworkMenu'
res\\vn\\menu.h:96: warning 147: excess elements in array of chars initializer a
fter '_cVoiceMenu'
res\\vn\\menu.h:141: warning 147: excess elements in array of chars initializer
after '_cProtocolMenu'
res\\vn\\menu.h:141: warning 147: excess elements in array of chars initializer
after '_cProtocolMenu'
res\\vn\\menu.h:157: warning 147: excess elements in array of chars initializer
after '_cDialplanMenu'
res\\vn\\menu.h:157: warning 147: excess elements in array of chars initializer
after '_cDialplanMenu'
res\\vn\\menu.h:157: warning 147: excess elements in array of chars initializer
after '_cDialplanMenu'
res\\vn\\menu.h:157: warning 147: excess elements in array of chars initializer
after '_cDialplanMenu'
res\\vn\\menu.h:157: warning 147: excess elements in array of chars initializer
after '_cDialplanMenu'
res\\vn\\menu.h:157: warning 147: excess elements in array of chars initializer
after '_cDialplanMenu'
res\\vn\\menu.h:172: warning 147: excess elements in array of chars initializer
after '_cSystemMenu'
res\\vn\\menu.h:172: warning 147: excess elements in array of chars initializer
after '_cSystemMenu'
res\\vn\\menu.h:172: warning 147: excess elements in array of chars initializer
after '_cSystemMenu'
res\\vn\\menu.h:172: warning 147: excess elements in array of chars initializer
after '_cSystemMenu'
res\\vn\\menu.h:172: warning 147: excess elements in array of chars initializer
after '_cSystemMenu'
res\\vn\\menu.h:193: warning 147: excess elements in array of chars initializer
after '_cYesNoMark'
res\\vn\\str.h:54: warning 147: excess elements in array of chars initializer af
ter '_cIDS'
res\\vn\\str.h:54: warning 147: excess elements in array of chars initializer af
ter '_cIDS'
res\\vn\\str.h:54: warning 147: excess elements in array of chars initializer af
ter '_cIDS'
res\\vn\\str.h:54: warning 147: excess elements in array of chars initializer af
ter '_cIDS'
res\\vn\\str.h:54: warning 147: excess elements in array of chars initializer af
ter '_cIDS'
res\\vn\\str.h:54: warning 147: excess elements in array of chars initializer af
ter '_cIDS'
res\\vn\\str.h:54: warning 147: excess elements in array of chars initializer af
ter '_cIDS'
res\\vn\\str.h:54: warning 147: excess elements in array of chars initializer af
ter '_cIDS'
res\\vn\\str.h:54: warning 147: excess elements in array of chars initializer af
ter '_cIDS'
res\\vn\\str.h:54: warning 147: excess elements in array of chars initializer af
ter '_cIDS'
res\\vn\\str.h:54: warning 147: excess elements in array of chars initializer af
ter '_cIDS'
res\\vn\\str.h:54: warning 147: excess elements in array of chars initializer af
ter '_cIDS'
res\\vn\\str.h:54: warning 147: excess elements in array of chars initializer af
ter '_cIDS'
res\\vn\\str.h:54: warning 147: excess elements in array of chars initializer af
ter '_cIDS'
res\\vn\\str.h:54: warning 147: excess elements in array of chars initializer af
ter '_cIDS'
res\\vn\\str.h:54: warning 147: excess elements in array of chars initializer af
ter '_cIDS'
res\\vn\\str.h:54: warning 147: excess elements in array of chars initializer af
ter '_cIDS'
res\\vn\\str.h:54: warning 147: excess elements in array of chars initializer af
ter '_cIDS'
res\\vn\\str.h:54: warning 147: excess elements in array of chars initializer af
ter '_cIDS'
res\\vn\\str.h:54: warning 147: excess elements in array of chars initializer af
ter '_cIDS'
res\\vn\\str.h:54: warning 147: excess elements in array of chars initializer af
ter '_cIDS'
res\\vn\\str.h:54: warning 147: excess elements in array of chars initializer af
ter '_cIDS'
C:\SDCC\BIN\sdcc iax2.c -mz80 -c --std-c99 --codeseg CODE5
C:\SDCC\BIN\sdcc protocol.c -mz80 -c --std-c99 --codeseg CODE5
C:\SDCC\BIN\sdcc rtps.c -mz80 -c --std-c99 --codeseg CODE5
C:\SDCC\BIN\sdcc sips.c -mz80 -c --std-c99 --codeseg CODE5
C:\SDCC\BIN\sdcc auth.c -mz80 -c --std-c99 --codeseg CODE6
C:\SDCC\BIN\sdcc md5.c -mz80 -c --std-c99 --codeseg CODE6
C:\SDCC\BIN\sdcc rc4.c -mz80 -c --std-c99 --codeseg CODE6
C:\SDCC\BIN\sdcc sha1.c -mz80 -c --std-c99 --codeseg CODE6
C:\SDCC\BIN\sdcc hmac_sha1.c -mz80 -c --std-c99 --codeseg CODE6
C:\SDCC\BIN\sdcc pbkdf2_sha1.c -mz80 -c --std-c99 --codeseg CODE6
C:\SDCC\BIN\sdcc digitmap.c -mz80 -c --std-c99 --codeseg CODE7
C:\SDCC\BIN\sdcc rtpr.c -mz80 -c --std-c99 --codeseg CODE7
C:\SDCC\BIN\sdcc sipr.c -mz80 -c --std-c99 --codeseg CODE7
C:\SDCC\BIN\sdld -n -f linkmain
C:\SDCC\BIN\hex2bin main.bin -f0 -a0 -x6 -b32768 -e57344 main.ihx

C:\sdcc\src>..\bin\namebin main.bin ar168p sip vn

C:\sdcc\src>tftp -i 192.168.1.39 put ar168p sip us 056000
'tftp' is not recognized as an internal or external command,
operable program or batch file.

C:\sdcc\src>tftp -i 192.168.1.39 put ar168p sip us 056000
'tftp' is not recognized as an internal or external command,
operable program or batch file.
"
here is all command in DOS

Woodyposted on 2012-03-05 11:44:30 125.33.177.132
Enter safe mode, "ping 192.168.1.200" to make sure you are there, and use command line "tftp -i 192.168.1.200 put ar168p_sip_us_056000.bin" to recover it.

dungvt@postef.com.vnposted on 2012-03-05 15:31:37 117.5.63.186
Dear woody

In the safe mode, i was ping 192.168.1.200 but can't find the host destination.

Woodyposted on 2012-03-05 17:37:07 125.33.177.132
You need to set the IP address of your PC to something like 192.168.1.xxx.

dungvt@postef.com.vnposted on 2012-03-06 08:10:55 113.160.16.218
not good resuilts!

Enter the safe mode but i can't send file ar168p sip us 056000 to IP phone through tftp? What can i do now?

Thank you for your support

Woodyposted on 2012-03-06 11:27:03 125.33.177.132
Can you ping 192.168.1.200 now?

dungvt@postef.com.vnposted on 2012-03-06 16:46:10 117.5.63.186
Now i can ping and send file to the phone.

But it same like the default mode so i can't use many functions. Can't browse the menu, no speaker phone, ... only pick up the handset then dial the number,...

Woodyposted on 2012-03-06 17:36:20 125.33.177.132
I am confused now. Can you send the pictures of this "AR168P" IP phone to support@palmmicro.com?

dungvt@postef.com.vnposted on 2012-03-07 01:05:17 113.160.16.218
On the screen display like below:

"ar168p
809738
wood1234"

And can't use any function keys

With this acc, the IP phone was log on succefully and can you track for me the SIP messages to SIP server?

I gues this is a firmware for testing from you but i wonder if that i was send file with name "ar168p sip vn 056000"

Woodyposted on 2012-03-07 03:36:20 125.33.177.132
Can you send the detail image of the phone? We can not track your SIP messages here. We need more information on the hardware side to find out why the function keys do not work.

dungvt@postef.com.vnposted on 2012-03-07 05:51:28 113.160.16.218
Model we buy from you are AR168P

Using AR1688 (chip set) + AR1689 (Flash)

Origin FW: 045006 but now upgarde 056000 by myself.

IP phone using the Graphic LCD, Ethernet chip set is KSZ8842-16MQL, FLASH is SST39VF1681-70-4c-eke .

Two RJ45 port, ....

Woodyposted on 2012-03-07 07:33:28 125.33.177.132
Function keys not working after upgrade ar168p_sip_us_056000.bin?

dungvt@postef.com.vnposted on 2012-03-07 09:39:12 113.160.16.218
yes, even through tftp in the safe mode?

Woodyposted on 2012-03-07 18:14:12 125.33.177.132
Can you try to update 0.46 AR168P software?

dungvt@postef.com.vnposted on 2012-03-08 01:12:31 113.160.16.218
Dear Woody

I just upgrade the 0.46 AR168P follow your link but the phone still have same problem?

Woodyposted on 2012-03-08 06:23:37 125.33.177.132
I guess that you had changed the MAC address of the AR168P at some stage, can you change it back? The standard software will check MAC address, if it does not match, many functions including those function keys will be disabled.

dungvt@postef.com.vnposted on 2012-03-08 09:17:17 113.160.16.218
OK, i'll do it like your guides.

More options? Please login or register account. metropolitan-tundra