Search results

  1. Solved Incoming calls on any DID land on main number in log; UserInfo in SIP "to" response shows correct DID

    Hi all, I have found the problem - Somehow when I deleted the "damaged" trunk, this action also has reset the inbound rules for each DID to point to the main number extension. As soon as I had this corrected, the calls landed again at the correct destination. Problem solved :-) I leave this...

  2. Solved Incoming calls on any DID land on main number in log; UserInfo in SIP "to" response shows correct DID

    Hi all, after the update to the newest "stable" 3CX V 16.05.389 today, our previously perfect working trunk showed the same problems as I had last time - Any incoming calls did ring on the internal extension but it could not be picked up. The last time's working remedy with setting the trunk to...

  3. Incoming calls (from external) ring but get immediately hung up when trying to answer (via 3cx softphone and webclient)

    Hi all, a quick update on this issue. As we checked with our VoiP provider, they checked our 3CX logs and told me that the internal phone is ending the call (they pointed at some log entries which suggested this). But as we clearly don't hang up the phones this could not be the error. I then...

  4. Incoming calls (from external) ring but get immediately hung up when trying to answer (via 3cx softphone and webclient)

    Hi Frederick, thanks for your feedback. The 3CX client (softphone) is connecting via 3CX tunnel - so it is encrypted but I don't know if inside the tunnel it is also using SIP TLS / SRTP or not. . Trunk is unfortunately not encryptable with this provider (they don't provide TLS/SRTP). I have...

  5. Incoming calls (from external) ring but get immediately hung up when trying to answer (via 3cx softphone and webclient)

    Hi all, I have a very strange problem with our on-premises - 16.0.4.493 - 3cx which I detected today (we have rarely calls coming in so I don't know for how long this problem really exists) but I never have seen this with 3cx versions before 16.0.4.493 and this has still worked 2 months ago)...

  6. Solved Allowing internal calls 24/7 but restrict calls from external to be allowed only during business hours; exceptions for specific external numbers

    Hi @INDY_Mathieu, that has perfectly worked. Selected CIDs can pass through 24/7, Rest get blocked out of Office hours. Internal 24/7 calls I have not yet tested. Thanks again, John

  7. Solved Allowing internal calls 24/7 but restrict calls from external to be allowed only during business hours; exceptions for specific external numbers

    Hi @INDY_Mathieu , thanks for your feedback. I will test this and feedback here. with kind regards, John

  8. Solved Allowing internal calls 24/7 but restrict calls from external to be allowed only during business hours; exceptions for specific external numbers

    Good morning @leejor, I had a look into this. Maybe I don't fully understand what you say - but to explain the situation more precisely: We have multiple internal ring groups. Each of these ring groups have a DID assigned so they can be called from the outside and will ring the relevant phones...

  9. Solved Allowing internal calls 24/7 but restrict calls from external to be allowed only during business hours; exceptions for specific external numbers

    Good evening, with 3CX standard, is it possible to allow extensions to be called 24/7 from other internal extensions but allow them to be reached only during business hours from the outside - but allow certain known external numbers to reach these extensions also 24/7? (These extensions are...

  10. Solved Outbound Caller Id always shows main (trunk) number instead of individual outbound caller ids on remote phone

    Update: Our VoiP Provider - together with their upstream VoiP provider - has adjusted something on their side and now it works. Thanks for all your help here in the forum which pointed me into the right direction. With kind regards, John

  11. Solved Outbound Caller Id always shows main (trunk) number instead of individual outbound caller ids on remote phone

    Hi Carlos, thanks again - In the mean time I have taken a network trace outgoing from the 3CX to our provider and there it is clearly visible in the relevant SIP packet that the outbound caller id ("DisplayName" and "From") contains the correct outbound caller id (the one we have set in the 3CX...

  12. Solved Outbound Caller Id always shows main (trunk) number instead of individual outbound caller ids on remote phone

    Hi Carlos, thanks for this additional info. The two settings in our setup are already the same as in your screenshot. I believe that our VoiP provider currently blocks the ovewriting of the outbound caller id - but it surely has worked a year or two ago when I had last checked this. With kind...

  13. Solved Outbound Caller Id always shows main (trunk) number instead of individual outbound caller ids on remote phone

    Changing anything under P.asserted identity didn't change anything shown on the destination - I have now contacted our SIP provider and wait for their feedback.

  14. Solved Outbound Caller Id always shows main (trunk) number instead of individual outbound caller ids on remote phone

    Thanks - I will look into that also - as it is a not supported trunk. John

  15. Solved Outbound Caller Id always shows main (trunk) number instead of individual outbound caller ids on remote phone

    Ok, good suggestion. Thanks for such an extremely fast reply. John

  16. Solved Outbound Caller Id always shows main (trunk) number instead of individual outbound caller ids on remote phone

    This is on newest 3CX V16.1. I have just realized that - no mather what I have configured in the outbound caller id field in any of our extensions, when they call to an outside phone, always the main number of the trunk is shown to the called remote phone and not the one configured in each...
3CX Logo Footer Copyright © Sitemap Privacy
Top Bottom