VRSEngineer
Member
- Joined
- Mar 29, 2010
- Messages
- 95
- Reaction score
- 0
I was reading the Sorenson nTouch mobile faqs both for Android and iPhone/iOS and they both state:
Question: "Will I be able to make calls to other videophones (VP-to-VP or point-to-point calls)?"
Answer: "Yes, you will be able to call any VP-200 and/or any videophone or endpoint device that supports industry video standards (H.323 and H.264). The device must also have been provisioned with the NeuStar database (provisioning is handled by the default VRS provider for a given phone number)."
To view the original text click on the links below and expand the "Features" section then scroll down to the listed question:
Sorenson ntouch faq for Android Phones
Sorenson ntouch faq for iPhone
Could it be that they have now added H.263 support into the nTouch mobile, or is the Sorenson faq just flat out incorrect?
I started to answer your question last night, but decided it best to wait until I made it in to the office to do a proper sniff to give you accurate information.
Presently, when a Sorenson nTouch Mobile client on Android places a call, the Sorenson gateway 209.169.242.13 makes an H.323 H.225 Call Setup TCP port connection to 1720 and sends a SETUP message with the H.245 "fast start" capability set advertising only the genericVideoCapability (H.264). There is no H.263 offered in the capability set.
From the perspective of an H.323 sniff, the Sorenson FAQ is just flat out incorrect.
This is a factual statement given experimental data gathered from numerous call attempts today:
h245Control: 2 items
Item 0
H245Control item: 130 octets
H.245
PDU Type: request (0)
request: terminalCapabilitySet (2)
terminalCapabilitySet
sequenceNumber: 1
protocolIdentifier: 0.0.8.245.0.13 (h245 version 13)
mcCapability
..0. .... centralizedConferenceMC: False
...0 .... decentralizedConferenceMC: False
.... 0... rtcpVideoControlCapability: False
mediaPacketizationCapability
.... ..0. h261aVideoPacketization: False
rtpPayloadType: 2 items
Item 0
RTPPayloadType
payloadDescriptor: oid (2)
oid: 0.0.8.241.0.0.0.0 (iPpacketization_h241AnnexA(single NAL unit mode))
payloadType: 96
Item 1
RTPPayloadType
payloadDescriptor: oid (2)
oid: 0.0.8.241.0.0.0.1 (iPpacketization_RFC3984NonInterleaved)
payloadType: 96
0... .... logicalChannelSwitchingCapability: False
1... .... t120DynamicPortCapability: True
capabilityTable: 5 items
Item 0
CapabilityTableEntry
capabilityTableEntryNumber: 1
capability: receiveVideoCapability (1)
receiveVideoCapability: genericVideoCapability (5): ITU-T Rec. H.241 H.264 Video Capabilities
genericVideoCapability
capabilityIdentifier: standard (0)
standard: 0.0.8.241.0.0.1 (h264 generic-capabilities) - ITU-T Rec. H.241 H.264 Video Capabilities
maxBitRate: 2560
collapsing: 2 items
Item 0: Profile
collapsing item
parameterIdentifier: standard (0)
standard: 41 - Profile
parameterValue: booleanArray (1)
booleanArray: 64
Profile: 0x40, Baseline Profile
The other 4 capabilities are receiveUserInputCapability hookflash, basicString, dtmf, and encryptedIA5String. There are no other video capabilities.
Note that the RTP is also dynamic payload type 96 only (there is no payload type 34 for H.263 RFC2190 offered).
Simply put, no H.263. The Sorenson FAQ appears to be misrepresenting reality.