Questo sito utilizza cookie di profilazione (propri e di terze parti) per ottimizzare la tua esperienza online e per inviarti pubblicità in linea con le tue preferenze. Continuando a utilizzare questo sito senza modificare le tue preferenze acconsenti all’uso dei cookie. Se vuoi saperne di più o negare il consenso a tutti o ad alcuni cookie clicca qui>
The website that you are visiting also provides Arabian language. Do you wish to switch language version?
يوفر موقع الويب الذي تزوره المحتوى باللغة العربية أيضًا. هل ترغب في تبديل إصدار اللغة؟
The website that you are visiting also provides Russia language Do you wish to switch language version?
Данный сайт есть в английской версии. Желаете ли Вы перейти на английскую версию?
The reported issue was reffering to the case when there are two TE30 devices trying to register to VP9630 MCU.
One of the TE30 was registering from the same physical LAN of the MCU wheter the second one was registering to the public IP of the MCU.
Upon further tests, whenever of the TE30's was trying to have a H.323 call with the other one then the call would fail.
Several steps for solving this issue were performed:
1. Made sure the correct IP addresses are assigned on the GE ports of the MCU (GE0 using the private IP address and GE1 using the public IP address)
2. Performed calling tests and captured packets in the network as to get the call signaling
Since the embedded GK of the MCU is limited in its action to the internal network (due to NAT processes) it was concluded that there is no other way to use the internal GK for H.323 calls between devices registering from the same physical LAN and the ones registering from public IP addresses)
The internal GK of the MCU does not support NAT translation therefore the devices are unable to perform H.323 calls to each other due to that.
One solution can can be provided:
1. Make sure the TE30's are not using the GK of the MCU - then call the device using the IP addreses assigned to them
Also, the below work-arounds can used for making the call:
1. Use an independent GK to which both of the TE30 devices would register hence the GK will properly relay the signaling and the media to each terminal in part (the use of an independent GK is a must thus might not be the best work-around - but will surely get the issue solved)
2. Call the devices only from the MCU web interface (however, this would mean that the callee are participants in a conference and not performing an actual H.323 call).