Dismiss Notice
We would like to remind you that we’re updating our login process for all 3CX forums whereby you will be able to login with the same credentials you use for the Partner or Customer Portal. Click here to read more.

Strange Ringtone problem on the operator extension

Discussion in '3CX Phone System - General' started by maxita, Aug 24, 2011.

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

    Joined:
    Feb 2, 2011
    Messages:
    6
    Likes Received:
    0
    Hello, i have upgraded today from 3cx 9 to 10. i have a strange problem, as operator extension i have an ip phone thomson ST2030, not officially supported but ever worked.

    After the upgrading when there is some call that phone ringing with a strange MELODY. Not the ringtone that i have setup via web panel and doublecheked via display (coca cola ringtone) but just a crazy BEEP BEEP. I have try to reset/restart and change ringtone on the phone but incoming call just make it beeping.

    Someone know how to fix that? it was working with 3cx v9....
     
  2. willow

    willow Member

    Joined:
    Mar 1, 2011
    Messages:
    471
    Likes Received:
    0
    Sys log please. The version should play no part in the phone ringtone.
     
    Stop hovering to collapse... Click to collapse... Hover to expand... Click to expand...
  3. maxita

    Joined:
    Feb 2, 2011
    Messages:
    6
    Likes Received:
    0
    Thanks for the information, but the strange things its that with version 9 of 3cx the phone ringing well, the same day that we have updated to 3cx version 10 sp2 the phone started to give this problem of this strange ringtone.

    ANother info, internal calls are working with the correct setup ringtone and just calls from voip provider give this problem of this unkown and not setup ringtone. I have seen in the logs that the system recognized the THOMSON as Yealink, maybe this is the problem?!?!

    Code:
    17:42:10.085  Currently active calls [none]
    17:42:08.589  [CM503003]: Call(2): Call to sip:10@192.168.1.7:5060 has failed; Cause: 487 Request Cancelled; from IP:192.168.1.20:5060
    17:42:08.491  [CM503008]: Call(2): Call is terminated
    17:42:03.205  [CM505001]: Ext.10: Device info: Device Identified: [Man: Yealink;Mod: T20;Rev: General] Capabilities:[reinvite, no-replaces, unable-no-sdp, no-recvonly] UserAgent: [THOMSON ST2030 hw5 fw2.74 00-14-7F-00-27-28] PBX contact: [sip:10@192.168.1.7:5060]
    17:42:03.204  [CM503002]: Call(2): Alerting sip:10@192.168.1.20:5060;transport=udp;user=phone
    17:42:03.109  [CM503025]: Call(2): Calling Ext:Ext.10@[Dev:sip:10@192.168.1.20:5060;transport=udp;user=phone]
    17:42:03.106  [MS210002] C:2.2:Offer provided. Connection(transcoding mode): 192.168.1.7:7004(7005)
    17:42:03.074  [CM503004]: Call(2): Route 1: Ext:Ext.10@[Dev:sip:10@192.168.1.20:5060;transport=udp;user=phone]
    17:42:03.072  [CM503010]: Making route(s) to <sip:10@192.168.1.7>
    17:42:03.071  [MS210000] C:2.1:Offer received. RTP connection: 85.18.47.247:56554(56555)
    17:42:03.068  Remote SDP is set for legC:2.1
    17:42:03.066  [CM505001]: Ext.11: Device info: Device Identified: [Man: Counterpath;Mod: X-Lite;Rev: General] Capabilities:[reinvite, no-replaces, unable-no-sdp, recvonly] UserAgent: [X-Lite 4 release 4.1 stamp 63214] PBX contact: [sip:11@192.168.1.7:5060]
    17:42:03.061  [CM503001]: Call(2): Incoming call from Ext.11 to <sip:10@192.168.1.7>
    17:42:03.042  [CM500002]: Info on incoming INVITE:
      INVITE sip:10@192.168.1.7 SIP/2.0
      Via: SIP/2.0/UDP 192.168.1.3:65430;branch=z9hG4bK-d8754z-36e07b741ad82ef1-1---d8754z-;rport=65430
      Max-Forwards: 70
      Contact: <sip:11@85.18.47.247:65430>
      To: <sip:10@192.168.1.7>
      From: "11"<sip:11@192.168.1.7>;tag=097a28f6
      Call-ID: NzVhZDczYzk2MjJlMmFjYjJiNTE2YTQzYWZkMmU1YTM.
      CSeq: 2 INVITE
      Allow: INVITE, ACK, CANCEL, OPTIONS, BYE, REFER, NOTIFY, MESSAGE, SUBSCRIBE, INFO
      Proxy-Authorization: Digest username="11",realm="3CXPhoneSystem",nonce="414d535c0469a14a77:11fea95c63e18837cf4b8b3f3e8726ee",uri="sip:10@192.168.1.7",response="2898270ca108e77926e1a5eba2055e98",algorithm=MD5
      Supported: replaces
      User-Agent: X-Lite 4 release 4.1 stamp 63214
      Content-Length: 0
      
    17:41:57.900  [CM503003]: Call(1): Call to sip:10@192.168.1.7:5060 has failed; Cause: 487 Request Cancelled; from IP:192.168.1.20:5060
    17:41:57.800  [CM503008]: Call(1): Call is terminated
    17:41:51.314  [CM505001]: Ext.10: Device info: Device Identified: [Man: Yealink;Mod: T20;Rev: General] Capabilities:[reinvite, no-replaces, unable-no-sdp, no-recvonly] UserAgent: [THOMSON ST2030 hw5 fw2.74 00-14-7F-00-27-28] PBX contact: [sip:10@192.168.1.7:5060]
    17:41:51.313  [CM503002]: Call(1): Alerting sip:10@192.168.1.20:5060;transport=udp;user=phone
    17:41:51.222  [CM503025]: Call(1): Calling Ext:Ext.10@[Dev:sip:10@192.168.1.20:5060;transport=udp;user=phone]
    17:41:51.218  [MS210002] C:1.2:Offer provided. Connection(transcoding mode): 192.168.1.7:7000(7001)
    17:41:51.155  [CM503004]: Call(1): Route 1: Ext:Ext.10@[Dev:sip:10@192.168.1.20:5060;transport=udp;user=phone]
    17:41:51.139  [MS210000] C:1.1:Offer received. RTP connection: 213.254.211.87:33338(33339)
    17:41:51.137  [CM503010]: Making route(s) to <sip:10@192.168.1.7:5060>
    17:41:51.132  Remote SDP is set for legC:1.1
    17:41:51.128  [CM505003]: Provider:[VOIP Voice - IT] Device info: Device Not Identified: User Agent not matched; Capabilities:[reinvite, replaces, able-no-sdp, recvonly] UserAgent: [Cirpack/v4.42d (gw_sip)] PBX contact: [sip:0110133100@85.18.47.247:5060]
    17:41:51.125  [CM503001]: Call(1): Incoming call from 01119706159@(Ln.10000@VOIP Voice - IT) to <sip:10@192.168.1.7:5060>
    17:41:50.954  [CM503012]: Inbound office hours rule (unnamed) for 10000 forwards to DN:10
    17:41:50.951  Looking for inbound target: called=0110133100; caller=01119706159
    17:41:50.947  [CM500002]: Info on incoming INVITE:
      INVITE sip:0110133100@192.168.0.2:5060;transport=udp;rinstance=85315373097d4a7e SIP/2.0
      Via: SIP/2.0/UDP 213.254.211.80:5060;branch=z9hG4bK-XVYX-057e87bb-2c0ac826
      Max-Forwards: 29
      Record-Route: <sip:C=on;t=XVYXX@213.254.211.80:5060;lr>
      Contact: <sip:213.254.211.82:5060>
      To: <sip:0110133100@127.0.0.1;user=phone>
      From: "01119706159"<sip:01119706159@sip.voipvoice.it;user=phone>;tag=00625-UL-00ed338f-39a4dd273
      Call-ID: 00625-EN-00ed338e-075729193@sip.voipvoice.it
      CSeq: 15193528 INVITE
      Session-Expires: 600
      Min-SE: 90
      Allow: UPDATE, REFER
      Supported: timer
      User-Agent: Cirpack/v4.42d (gw_sip)
      Content-Length: 0
      
    17:41:38.085  Currently active calls [none]
    17:41:28.809  [CM504004]: Registration succeeded for: 10000@VOIP Voice - IT
    17:41:28.490  [CM504003]: Sent registration request for 10000@VOIP Voice - IT
    
     
  4. maxita

    Joined:
    Feb 2, 2011
    Messages:
    6
    Likes Received:
    0
    This is what i have asked via ticket to the 3cx support:

     
  5. nbailey

    nbailey Member

    Joined:
    Jan 31, 2011
    Messages:
    359
    Likes Received:
    0
    Hello,

    Here is the information regarding the distinctive ringing feature in 3CX V10 http://www.3cx.com/blog/voip-howto/caller-id-processing-distinctive-ringing-alert-info/

    I doubt anything can be done because your phones are not a supported phone, making changes for this phone would mean testing in house and configuring properly and this just isn't possible. This is the reason we give a list of supported phones at http://www.3cx.com/blog/support so issues like this don't happen, we can't test every phone on the market.

    Thanks,

    Nate
     
    Stop hovering to collapse... Click to collapse... Hover to expand... Click to expand...
  6. maxita

    Joined:
    Feb 2, 2011
    Messages:
    6
    Likes Received:
    0
    I fixed the problem with thomson st2030, putting in "system melody" a melody called "external". I discovered (is not documented) that the V10 of 3cx, sends an "alarm-info: external" for calls originating from VoIP trunks. Would be to insert a flag in the options of VoIP trunks to activate / deactivate the alert-info and it will avoid many problems with non-certified phones from 3cx.
    I understand that the 3cx can not test all the phones on the market but if you can extend the compatibility of their systems to wider range of hardware, without creating problems for phones certificates. I think the benefit of all.
     
  7. nbailey

    nbailey Member

    Joined:
    Jan 31, 2011
    Messages:
    359
    Likes Received:
    0
    Glad you sorted it out but to clarify some things here. First the alert info tag is document here and has been since before V10 was released. http://www.3cx.com/blog/voip-howto/caller-id-processing-distinctive-ringing-alert-info/

    We already have a large range of supported phones that work with 3CX and we document it in many locations on the forums and our blog that to make installation easy and to avoid issues like this supported phones should be used. Obviously this is up to the administrator or customer, but it doesn't make sense to not use a supported phone.

    Thanks,
    Nate
     
    Stop hovering to collapse... Click to collapse... Hover to expand... Click to expand...
  8. DIALOGSoftware

    Joined:
    Nov 9, 2010
    Messages:
    3
    Likes Received:
    0
    We've got exactly the same problem. We fixed the problem with the external melody but it remains one problem : the melody volume is set to max by default when there is a alarm-info external.
    Have you got the same issue ?
     
Thread Status:
Not open for further replies.