DTMF not working anymore after SNOM new firmware

Discussion in '3CX Phone System - General' started by PNC, Apr 22, 2010.

Thread Status:
Not open for further replies.
  1. PNC

    PNC

    Joined:
    Jul 22, 2008
    Messages:
    34
    Likes Received:
    0
    hello,
    how can you solve the next problem below:
    i need to say we have installed firmware version SNOM320-7.3.30 (6059) and DTMF via SIP INFO is ON.
    we didn't had this problem with firmware version SNOM320-7.1.30 (14306)

    This message appears in the logfiles:
    (14:36:42.654 [MS211000] C:21.1: 192.168.200.42:55552 is delivering DTMF using RTP payload (RFC2833). In-Band DTMF tone detection is disabled for this call segment)

    We need to change to this firmware because the new shipments of SNOM dont work with the old FW version anymore

    Kindly place all server logs in code and /code tags, this time it has been done for you - MFM

    Code:
    14:36:42.904 Active calls counted toward license limit: [21]
    14:36:42.654 [MS211000] C:21.1: 192.168.200.42:55552 is delivering DTMF using RTP payload (RFC2833). In-Band DTMF tone detection is disabled for this call segment.
    14:36:41.577 Session 810 of leg C:21.1 is confirmed
    14:36:41.437 [CM503007]: Call(21): Device joined: sip:510@192.168.200.230:5060
    14:36:41.437 [CM503007]: Call(21): Device joined: sip:113@192.168.200.42:2056;line=lw0yhud1
    14:36:41.421 [MS210003] C:21.1:Answer provided. Connection(transcoding mode[unsecure]):192.168.200.2:7068(7069)
    14:36:41.421 [MS210001] C:21.2:Answer received. RTP connection[unsecure]: 192.168.200.230:4000(4001)
    14:36:41.421 Remote SDP is set for legC:21.2
    14:36:41.343 [CM505001]: Ext.510: Device info: Device Not Identified: User Agent not matched; Capabilities:[reinvite, replaces, able-no-sdp, recvonly] UserAgent: [] PBX contact: [sip:510@192.168.200.2:5060]
    14:36:41.343 [CM503002]: Call(21): Alerting sip:510@192.168.200.230:5060
    14:36:41.249 [CM503025]: Call(21): Calling Ext:Ext.510@[Dev:sip:510@192.168.200.230:5060]
    14:36:41.249 [MS210002] C:21.2:Offer provided. Connection(transcoding mode): 192.168.200.2:7070(7071)
    14:36:41.202 [CM503004]: Call(21): Route 1: Ext:Ext.510@[Dev:sip:510@192.168.200.230:5060]
    14:36:41.202 [CM503010]: Making route(s) to <sip:510@192.168.200.2;user=phone>
    14:36:41.202 [MS210000] C:21.1:Offer received. RTP connection: 192.168.200.42:55552(55553)
    14:36:41.202 Remote SDP is set for legC:21.1
    14:36:41.202 [CM505001]: Ext.113: Device info: Device Identified: [Man: Snom;Mod: 3xx series;Rev: General] Capabilities:[reinvite, replaces, able-no-sdp, recvonly] UserAgent: [snom320/7.3.30] PBX contact: [sip:113@192.168.200.2:5060]
    14:36:41.202 [CM503001]: Call(21): Incoming call from Ext.113 to <sip:510@192.168.200.2;user=phone>
    14:36:41.187 [CM500002]: Info on incoming INVITE:
    INVITE sip:510@192.168.200.2;user=phone SIP/2.0
    Via: SIP/2.0/UDP 192.168.200.42:2056;branch=z9hG4bK-m822td6sseeh;rport=2056
    Max-Forwards: 70
    Contact: <sip:113@192.168.200.42:2056;line=lw0yhud1>;reg-id=1
    To: <sip:510@192.168.200.2;user=phone>
    From: "113"<sip:113@192.168.200.2>;tag=j4lxrfkui2
    Call-ID: 3c2676743779-96d3ncapi4v4
    CSeq: 2 INVITE
    Session-Expires: 3600;refresher=uas
    Min-SE: 90
    Accept: application/sdp
    Allow: INVITE, ACK, CANCEL, BYE, REFER, OPTIONS, NOTIFY, SUBSCRIBE, PRACK, MESSAGE, INFO
    Proxy-Authorization: Digest username="113",realm="3CXPhoneSystem",nonce="414d535c01e0d3d975:ebc613388278330e946c65c25e5f1da0",uri="sip:510@192.168.200.2;user=phone",response="4513934f79ba669611026164d861f89a",algorithm=MD5
    Supported: timer, 100rel, replaces, from-change
    User-Agent: snom320/7.3.30
    Allow-Events: talk, hold, refer, call-info
    Content-Length: 0
    P-Key-Flags: keys="3"
     
  2. leejor

    leejor Well-Known Member

    Joined:
    Jan 22, 2008
    Messages:
    10,757
    Likes Received:
    286
    Have a look at this, note "Out of Band", point 2. http://www.3cx.com/blog/voip-howto/dtmf-rfc2833/

    Were the phones set to send SIP INFO or RFC2833 before the firmware upgrade? have you tried setting them to send RFC2833?
     
  3. PNC

    PNC

    Joined:
    Jul 22, 2008
    Messages:
    34
    Likes Received:
    0
    Version 7.1.30:
    DTMF via SIP INFO:On or Off (I use On)
    Version 7.3.30:
    DTMF via SIP INFO:On, Off or SIP INFO only
    If I use any of these options it doesn't work
     
  4. leejor

    leejor Well-Known Member

    Joined:
    Jan 22, 2008
    Messages:
    10,757
    Likes Received:
    286
    I don't know if this will help. http://asterisk.snom.com/index.php/Asterisk_1.2/DTMF
     
Thread Status:
Not open for further replies.