Thanks Steve,

am I correct in assuming that Asterisk will ignore this packet? It will not have any harmful effect if the caller is on hold for an hour (120 packets)?

In order to feed back to Grandstream, is there a "correct" format for a keepalive message or is this one adequate?

regards,

Drew



Steve Langstaff wrote:
Your Grandstream device is using a UDP message of 8 x 0x00 bytes as it's RTP keepalive message. When Asterisk tries to read this it logs a warning because it is expecting a valid RTP packet.
    *From:* [EMAIL PROTECTED]
    [mailto:[EMAIL PROTECTED] *On Behalf Of
    *Drew Gibson
    *Sent:* 30 July 2007 19:55
    *To:* Asterisk Users Mailing List - Non-Commercial Discussion
    *Subject:* Re: [asterisk-users] Grandstream RTP keepalive
    packetscausing Asteriskwarning

    Hi Steve,

    The following packets match the offending warnings on the *
    console by time and number of occurrences and . The SRC and DST
    ports vary between calls (naturally) but the rest remains the same.


    Frame 3 (60 bytes on wire, 60 bytes captured)
    Ethernet II, Src: Grandstr_0b:a5:3e (00:0b:82:0b:a5:3e), Dst:
    Dell_3e:05:ac (00:13:72:3e:05:ac)
    Internet Protocol, Src: 10.1.10.184 (10.1.10.184), Dst: 10.1.10.1
    (10.1.10.1)
    User Datagram Protocol, Src Port: avt-profile-1 (5004), Dst Port:
    13608 (13608)
        Source port: avt-profile-1 (5004)
        Destination port: 13608 (13608)
        Length: 16
    Checksum: 0x8e5f [correct]
    Data (8 bytes)

    Data is 8 x null (00)

    regards,

    Drew



    Steve Langstaff wrote:
    Grab a network trace (with e.g. Wireshark) and look at the payload type
    and lengths of the RTP keepalive messages - if you post this information
    to the list I'm sure someone will comment on what's happening.

    -----Original Message-----
From: [EMAIL PROTECTED] <mailto:[EMAIL PROTECTED]> [mailto:[EMAIL PROTECTED] On Behalf Of Drew Gibson
    Sent: 26 July 2007 19:23
    To: Asterisk Users Mailing List - Non-Commercial Discussion
Subject: [asterisk-users] Grandstream RTP keepalive packets causing Asteriskwarning

Grandstream GXP-2000 with firmware 1.1.4.18 (beta) fixes an issue where the phone did not send rtp keepalives when on mute (resulting in disconnect from tech support hold and concalls)

A side effect seems to be that Asterisk pops the following warning on the console...

Jul 26 14:06:35 WARNING[31654]: rtp.c:463 ast_rtp_read: RTP Read too short

Grandstream say they are not sure what it is but "it should not affect anything".

    In other words, "Don't worry, be happy!".

    Any thoughts/experience on this?

    regards,

    Drew

    --
    Drew Gibson

    Systems Administrator
    OANDA Corporation
    416-593-6767 x322
    www.oanda.com <http://www.oanda.com>


    _______________________________________________
    --Bandwidth and Colocation Provided by http://www.api-digital.com--

    asterisk-users mailing list
    To UNSUBSCRIBE or update options visit:
       http://lists.digium.com/mailman/listinfo/asterisk-users

    _______________________________________________
    --Bandwidth and Colocation Provided by http://www.api-digital.com--

    asterisk-users mailing list
    To UNSUBSCRIBE or update options visit:
       http://lists.digium.com/mailman/listinfo/asterisk-users


-- Drew Gibson

    Systems Administrator
    OANDA Corporation
    416-593-6767 x322
    www.oanda.com <http://www.oanda.com>
------------------------------------------------------------------------

_______________________________________________
--Bandwidth and Colocation Provided by http://www.api-digital.com--

asterisk-users mailing list
To UNSUBSCRIBE or update options visit:
   http://lists.digium.com/mailman/listinfo/asterisk-users


--
Drew Gibson

Systems Administrator
OANDA Corporation
416-593-6767 x322
www.oanda.com

_______________________________________________
--Bandwidth and Colocation Provided by http://www.api-digital.com--

asterisk-users mailing list
To UNSUBSCRIBE or update options visit:
   http://lists.digium.com/mailman/listinfo/asterisk-users

Reply via email to