From: Kin Wai (kinwai@singnet.com.sg)
Date: Wed Jun 22 2005 - 16:03:51 GMT-3
IPCC is supported with CCME =)
I think I have solved the problem already after trial and error =/
I face the problem as the remote PC is issued with a LAN IP when I VPN into
the network.
It didn't work till I tried it with an WAN IP.
In short, I discovered that as long the remote PC is carrying a WAN IP on
its interface card.
It can successfully register itself with the CCME running on a WAN IP
(ip source-address x.x.x.x port 2000 , x.x.x.x is a wan ip)
I need not VPN into the network at all.
------
The above for home use still ok but in a live network I think quite
dangerous.
But If I change it all to LAN IP, issue with LAN addresses..
I will get the error below..
Anyone deployed CCME with VPN (issuing lan address) successfully before?
-----Original Message-----
From: Aleksander Klessa [mailto:aleksander.klessa@atm.com.pl]
Sent: Thursday, June 23, 2005 2:51 AM
To: Kin Wai
Cc: ccielab@groupstudy.com; cisco@groupstudy.com
Subject: Re: OT : IP communicator problem
Hi Kin
Are you using CME or CCM ???
I am not sure, but it looks like your IPC was trying to register to router -
IPC is not supported with CME
> Jun 22 09:15:28.366: New Skinny socket accepted [6] (5 active)
>
> Jun 22 09:15:28.366: sin_family 2, sin_port 1292, in_addr 218.186.54.x
>
> Jun 22 09:15:28.366: skinny_add_socket 6 218.186.54.x 1292
>
> Jun 22 09:15:28.410: socket_recv 92 bytes, expected 96
>
> Jun 22 09:15:28.410: Skinny Header was 96 0
> TFTP: Fa0/0 (wan ip of my router)
it looks that it is CME
> Telephony: WAN IP port 2000
olo
This archive was generated by hypermail 2.1.4 : Wed Jul 06 2005 - 14:43:42 GMT-3