TE40 caller : 188.8.131.52, E.164: 02510000
TE40 caller : 192.168.0.109, E.164: 02510000
H600 callee : 192.168.0.105, E.164: 654320
Pcap file was captured on H600 side.
All exchanged signaling commands between H600 and VP9650:
…Twenty seconds later…
(h225 or h245) and ((ip.dst eq 192.168.0.105 and ip.src eq 184.108.40.206) or (ip.src eq 192.168.0.105 and ip.dst eq 220.127.116.11))
H600 after received TCS from VP9650 did not response with any further commands, and led to a ReleaseComplete of VP9650.
Checked the facility commands of VP9650, found that its Q.931 crv value was 0, but with a facility reason of 5(startH245)
But we did not support that kind of rules.
Checked the ITU/T documents, found out it’s a standard procedure.
You know what should be done.
Details of the issue:
The situation is H600 can establish H.460 calls with most of the GKs around the world, but failed to a Polycom GK.
Allow me to explain the details of this issue:
1. Caller: Group500, callee: H600, GK/MCU: Polycom RMX 2000
2. Group500 sent a call to GK with callModel set to gatekeeperRouted, calling target: H600
3. GK sent H.460 SCI to H600
4. H600 replied SCR to GK
5. H600 established a H.225 TCP connection to the Polycom GK successfully
6. H600 sent facility to GK.
7. Polycom GK shutdown the H.225 TCP connection from H600 actively, and call terminated. Continue reading “Failed to establish H.460 call through Polycom MCU issue”
I submitted a patent paper, Data transmission method for video conferencing and video conferencing systems, to my parent agent early at Sep, 2014.
It is a patent with H.460 involved, origin from the V5.0 platform system.
But did not get any feedback until the Chinese New Year of 2015.
And after a few days of discussion and revision, finally got it finished. So, yes, the efficiency of patent agent could also be great once they decided to start.
Here is the Patent Application No. 201510096936.3