CTI Mode and cisco vlan

Discussion in 'Windows' started by klimdos, Nov 20, 2013.

Thread Status:
Not open for further replies.
  1. klimdos

    Joined:
    Sep 9, 2013
    Messages:
    6
    Likes Received:
    0
    Hello.
    If 3cx client and the telephone is comon subnet - CTI works in both directions - incoming call works and a set of numbers from the 3cx client - works.

    If the telephone and 3cx client is in a different vlan for an incoming call on the client displays information about the caller to dial a number but I can not - the information is not transferred to the telephone.

    ________________-

    I also do not understand why some clients get the internal address, and the rest - the address of my firewall to connect to the global network

    [​IMG]

    that route table in cisco router
    ciscodhcp#sh ip route
    Gateway of last resort is 192.168.254.249 to network 0.0.0.0
    C 192.168.12.0/24 is directly connected, Vlan6
    S 192.168.13.0/24 [1/0] via 192.168.12.220
    C 192.168.14.0/24 is directly connected, Vlan7
    C 192.168.10.0/24 is directly connected, Vlan3
    C 192.168.11.0/24 is directly connected, Vlan2
    C 192.168.21.0/24 is directly connected, Vlan20
    C 192.168.0.0/24 is directly connected, Vlan4
    192.168.254.0/29 is subnetted, 1 subnets
    C 192.168.254.248 is directly connected, GigabitEthernet1/0/12
    S* 0.0.0.0/0 [1/0] via 192.168.254.249


    that route table in my firewall

    Постоянные маршруты:
    Сетевой адрес Маска Адрес шлюза Метрика
    192.168.10.0 255.255.255.0 192.168.254.250 1
    192.168.11.0 255.255.255.0 192.168.254.250 1
    192.168.12.0 255.255.255.0 192.168.254.250 1
    192.168.15.0 255.255.255.0 192.168.254.250 1
    192.168.0.0 255.255.255.0 192.168.254.250 1
    80.76.154.169 255.255.255.255 84.52.127.65 1
    80.76.156.73 255.255.255.255 84.52.127.65 1
    8.8.4.4 255.255.255.255 84.52.127.65 1
    8.8.8.8 255.255.255.255 84.52.127.65 1
    192.168.21.0 255.255.255.0 192.168.254.250 1
    192.168.14.10 255.255.255.255 192.168.254.250 1
    91.221.67.141 255.255.255.255 84.52.127.65 1
    0.0.0.0 0.0.0.0 80.246.254.145 261
    192.168.14.120 255.255.255.255 192.168.254.250 1
    192.168.14.121 255.255.255.255 192.168.254.250 1
    192.168.14.122 255.255.255.255 192.168.254.250 1
     
  2. elounda

    Joined:
    Dec 13, 2013
    Messages:
    10
    Likes Received:
    1
    Hi klimdos.
    I think that the problem maybe is on your Vlan Setup.

    For example
    1.)I have a server with the 3cx application and ip 192.168.1.2 (Vlan1)
    2.)i have a client with the 3cx software and ip 192.168.1.3 (Vlan1)
    3.) i have a client with the 3cx software and ip 192.168.2.4 (Vlan2)

    When i apply in my router the vlan scenario then Vlan2 cannot see Vlan1, but i have my server running on Vlan1, that makes the difference between the local and the public ip, the first client on Vlan1 will connect directly with the lan Ip because it belongs to the same network but the second client on Vlan2 can't and for that reason he connects with the Public IP, to make sure u have a right setup (in the case u want local ip for all machines in your local network) u must be able to ping the server ip from the client machine, if not your server must belong to multiple Vlan's or the clients running 3cx must belong to the same vlan.
     
  3. klimdos

    Joined:
    Sep 9, 2013
    Messages:
    6
    Likes Received:
    0

    elounda, thank you very much. You gave me the impetus to understanding the problem. A Problem in hiding is not cisco. TMG client installed on all machines in the network forced to work through a proxy softphone.
    It remains to understand how to eliminate 3cx phone from the list of programs being processed.

    Once again thank you elounda, Merry Christmas and happy new year.
     
Thread Status:
Not open for further replies.