Search results

  1. SMS Closed by System

    @OlegR_3CX Where is the option in v20 to auto-close chats? In v18 it was in Reporting / Chat Logs / Settings, but I don't see anything similar to that in v20.

  2. Inbound Calls to RG Not Following Plan

    There were 2 users in the ring group that were not showing as available in the web client. I removed them from the ring group and the call handling is now working as desired. This is a concern, though, as an unregistered extension apparently now causes this processing to fail. What should be...

  3. Inbound Calls to RG Not Following Plan

    @TheodorosG_3CX The value of that parameter is 0.

  4. Inbound Calls to RG Not Following Plan

    @TheodorosG_3CX, there shouldn't be, but there are over 900 parameters. How could I tell if something has been modified, or is there a particular parameter that you suspect? Also, since I created the new ring group yesterday, the client advised the following today: I have had a few customers...

  5. Inbound Calls to RG Not Following Plan

    Thanks, @JohnS_3CX. I created another ring group and moved one of the DIDs to it. It exhibits the same behavior. I have attached screenshots showing what I'm seeing. 8001 is the original RG and 8002 is the one I just created. Please advise.

  6. Inbound Calls to RG Not Following Plan

    Inbound calls to a ring group are supposed to ring all extensions in the RG for 20 seconds and then forward to the voicemail for one of the extensions if no one answers. After upgrading to V20 (20.0 Update 0, Build 1620), this no longer works. Inbound calls made to one of the assigned DIDs now...

  7. Solved Cannot Move Phone to Different Extension

    I just had one of the people onsite unplug the phone for 5 minutes and then manually reset it. It is now associated with the correct extension.

  8. Solved Cannot Move Phone to Different Extension

    There are no entries on the IP Blacklist. I also reconfirmed that there is no IP phone configured for x1010 and that the correct MAC address is entered for the IP phone for the x1017 user. I reset the phone to factory defaults again and it still seems to be (mostly) provisioned for x1010 and...

  9. Solved Cannot Move Phone to Different Extension

    That was the first thing I did ("I removed the "bad" IP phone from x1017 and removed the "good" IP phone from x1010, so that neither extension had any IP phones defined.") I also mentioned that I reset the phone to factory defaults, and the issue persists.

  10. Solved Cannot Move Phone to Different Extension

    System: Enterprise 16 SIM Version: 20.0 Update 0 (Build 1620 Release) One of our clients running on V20 had a phone break on them and they wanted one of the infrequently used phones moved to the user's extension with the broken phone. I removed the "bad" IP phone from x1017 and removed the...
    • RHopkinson
    • Thread
    • phone snom 3cx
    • Replies: 5
    • Forum: Snom

  11. Emails Not Sent to Specific Email Address

    Hi All, We have a client running 3CX Enterprise v18.0 (Build 20) in AWS (Debian 9). They reported that welcome emails sent to one extension were never received by the associated email address. I performed a message trace and found no messages from 3CX delivered to the end user's Microsoft 365...

  12. DID Issues with SMS

    Changing the "CalledNum" value in the trunk from Request Line URI: User Part to To: User Part resolved the issue.

  13. DID Issues with SMS

    But that contradicts what they have in the document link I posted:

  14. DID Issues with SMS

    Thanks for the reply, @Charles_3CX. The link you provided seems to be specific to Bandwidth configuration, and it mentions nothing about DIDs. We're using SIPTrunk.com (Flowroute), and their documentation advises changing the inbound parameters...

  15. DID Issues with SMS

    We have SMS configured and working for selected extensions. SMS works fine when we add the user's DID to their extension in e164 format (e.g., +13205551212), but that does not allow inbound calls to ring to their extension (the inbound rule apparently doesn't match the e164 formatted version)...
    • RHopkinson
    • Thread
    • sms message did
    • Replies: 7
    • Forum: SMS

  16. Inbound Calls to SMS Number Not Routing to Extension

    I determined the calls were being routed by the destination associated with the trunk itself. It seemed that the DID rule was simply not firing. I managed to get this to work by adding the same 10-digit number to the trunk in wildcard (*NPANXX9999) format instead of e164 (+1NPANXX9999) format...

  17. Inbound Calls to SMS Number Not Routing to Extension

    All three trunks have different registrations. I checked the CDR records on the provider and verified that the call is coming in on the "SMS" trunk. In addition, I verified (using the test CID rule) that it processes the inbound call only when on the "SMS" trunk--not when on the "Local" trunk.

  18. Inbound Calls to SMS Number Not Routing to Extension

    A little more info: I tried adding the DID back to the "local" trunk and added it as a DID for his extension (which now has two DIDs with the same 10-digit number). I placed a test call but the call still rings to ring group 0001. Just to make sure the extension is able to receive external...

  19. Inbound Calls to SMS Number Not Routing to Extension

    @cat5king No, the extension is not set up to forward to any ring groups, and is not even a part of the ring group to where the calls are going. I'd be more than happy to jump on a screen share. Thanks.

  20. Inbound Calls to SMS Number Not Routing to Extension

    There are three trunks in this system (Local, TF, and SMS). The SMS trunk currently has only one DID, the number in question, in E.164 format. That DID is also defined only to this trunk and not to any other trunks.
3CX Logo Footer Copyright © Sitemap Privacy
Top Bottom