This thread has been locked.

If you have a related question, please click the "Ask a related question" button in the top right corner. The newly created question will be automatically linked to this question.

video codec

Guys,

below are the specs for video CODEC, pls suggest part from TI.

IP ATA should connect to IP network on one end and another end should  be connected to analog subscribers on FXS ports

Two nos. of RJ45 100 Base-T Fast Ethernet ports full duplex with auto negotiation: One LAN port for management and one WAN port for connecting to network

8 analog ports: FXS RJ11 interface for 8 POTS subscribers with better than 1500 ohms loop limit on every port, to support up to a distance of  10 kms

  • Hi Syed,

    My group does not have any parts that support 100Base-T applications but our Ethernet team may.

    Nasser,

    Do you guys have a part to recommend to Syed?

    Regards,

    Mike

  • We have several devices in our Ethernet portfolio that support 100Base-T.  The landing page with parametric tables can be found at:

    http://www.ti.com/lsds/ti/interface/ethernet-products.page

    What are the key requirements for the device?  For example:

    • Operating temperature
    • Cable reach
    • MAC interface
    • # of LEDs
    • Package preference

    Once we have some of those requirements identified, we can recommend some possible devices.

    Patrick

  • Hi Patric thanks for your kind revert below are the spces,

     

    General Specifications

    Power consumption should be less than 20 watts when all 8 lines are extended  to 10km

    It should support Caller Line Identification and Presentation (CLIP)

    It should support Firmware upgrade via HTTPS

    It should support DTMF tone detection and generation

    ATA should function in standalone mode whenever IPPBX or Ethernet port or L2 switch fails.

    ATA should function like a standalone PABX by providing switching capability for the locally connected FXS ports.

    It should support Auto firmware and auto configuration upgrade via HTTPS

    Protocols Support 

    SIP 2.0 (RFC 3261), IP, UDP, SDP, TCP, RTP, RTCP, HTTP, HTTPS, ARP, RARP, ICMP, DHCP (client), 802.1x, NAT.

    Management: Secured Web based management (https) should be supported

    It should support 802.1 p/Q VLAN tagging

     QoS functionality: DiffServ, TOS should be supported

    It should support SIP over UDP, TCP and TLS

    It should support SNMPv2/v3 for FCAPS functionality from NMS

    It should support SRTP

     It should be Upgradable to IPv6

    It should support T.38 (v2 essential for G3 fax & v3 desirable for Super G3 fax) and pass through Fax Over IP (FoIP).

     

    Registration & Authentication:

    Analog extensions connected to IP ATA should get registered to IP PABX using

    SIP protocol minimum for 2 IP PABXs. This is to have redundancy so that if one IP PABX fails, service will be provided by other IP PABX

    Each analog extension should have a separate SIP account in IP PABX.

    It should support digest authentication

     

  • I should have been more clear in my request.  I am looking for more guidance on the specs for the Ethernet Phy itself.  The information provided is all far above the level of functionality contained in the Phy.  Please take a look at the products available at:

    http://www.ti.com/lsds/ti/interface/ethernet-products.page

    Once you have an idea of the choices available in the current Ethernet Phy portfolio, I can help narrow down the options.

    Patrick

  • Syed,

    Have you had an opportunity to review the Ethernet product offerings?  Is there any additional information I can provide to help you narrow down your selection?

    Patrick

  • Hi patrick,

    Sorry i counld not respond you back for your previos post,

    yes i reviewed the Ethernet products i am yet to finalize my design,

    Once i finalize my design i will let you if any help needed from you.

     

    regars,

    syed hamad.