Recent content by DtotheAmbrose

  1. report showing extension status change

    Any chance of this happening?

  2. Solved Multiple Invites from the same call in under a second

    After going back and forth a few times with Vitelity here is the solution, The settings provided from Vitelity to enter into the SIP trunk are a little off. For the outbound calls you need to setup a different trunk which does not register with Vitelity. What was happening is our account...

  3. Solved Multiple Invites from the same call in under a second

    I think this may be more of a problem with the provider. We just lost the outbound calls again with a different errors This happened first. 10/20/2017 2:05:23 PM - Call to T:Line:10001>>1@[Dev:sip:[email protected]:5060] from L:44.1[Extn:100] failed, cause: Cause: 403...

  4. Solved Multiple Invites from the same call in under a second

    I forgot to add one thing. If I refresh the registration with vitelity the outbound calls work again.

  5. Solved Multiple Invites from the same call in under a second

    This is the first day we have used the 3cx server in a live environment. We had tested it for a week with in-bound and outbound had no problems. We ported over 2 numbers from comcast which completed this morning. This did create a problem with a credentials dont match error which required...

  6. Solved Multiple Invites from the same call in under a second

    I am chasing down a problem we have with outbound calls which has started up today (we switched over from elastix to 3cx recently) 3cx V15.5 Vitelity is the provider Yealink 32/38 phones which have the newest firmware When we call outbound we get a rejection from Vitelity as the outbound call...

  7. Inbound busy signal V15 and Vitelity

    Removed

  8. Inbound busy signal V15 and Vitelity

    @hwcltjn I dont have another provider to check. Our current system is through comcast which we are working on getting rid of. The firewall checker in 3cx is all green with no problems and the outbound calls which use the same ports are working so I dont think it is the firewall causing a problem.

  9. Inbound busy signal V15 and Vitelity

    On the log I should clarify, it is the capture log from the activity screen from 3cx, I opened it in wireshark to view it.

  10. Inbound busy signal V15 and Vitelity

    @hwcltjn For the codecs we have them in the priority in the trunk of G.711 U-law G.711 A-law GSM-FR G729 The DID is in the trunk settings.

  11. Inbound busy signal V15 and Vitelity

    @YiannisH_3CX 1 trunk, we purchased a single number to do testing. The DID is configured just to that trunk. Yes the incoming number is setup exactly (cut and paste with making sure there were no extra spaces).

  12. Inbound busy signal V15 and Vitelity

    I have the inbound rule pointed to an extension which registers in the 3cx admin panel. I have the trunk settings set to 10. codecs active GSM-FR G729 G.711 U-Law G.711 A-Law G722 I could not find anything specific about the codecs supported between Vitelity and 3cx but both say their systems...

  13. Inbound busy signal V15 and Vitelity

    I got wireshark installed and ran a test call. Looks like the inbound is being rejected but I dont know enough to understand what is doing the rejecting.

  14. Inbound busy signal V15 and Vitelity

    I am working on setting up 3cx V15 and we are having problems with inbound where it goes to a busy signal on any inbound call. I have searched the forums and found several instances of people having a problem with inbound calls from Vitelity going to a busy signal like we are getting. This one...
See more
3CX Logo Footer Copyright © Sitemap Privacy
Top Bottom