Recent content by AhmedYassine

  1. A

    Suggestion: SIP Trunk Gateway Status in FusionPBX

    Hi, I would like to suggest an enhancement regarding the configuration of a SIP trunk with an endpoint gateway without SIP registration in FusionPBX. Currently, when the gateway is configured without registration, FusionPBX does not provide a clear status indicator to show whether the SIP...
  2. A

    SOLVED Outbound Caller ID per Extension

    Hi, I would like to configure each extension to present a specific outbound Caller ID number. For example: 8000 → 0780002833 8001 → 0780002834 8002 → 0780002835 I tried implementing this using outbound dialplan rules, but all my attempts have failed so far. Does anyone have any...
  3. A

    SOLVED Routing MSC Number Range to FusionPBX Extensions

    I did it without result : error :"UNALLOCATED_NUMBER" name="MSC_to_8001" destination_number" ="^780002834$"> action application="transfer" data="8001 XML default" i have create the dialplan on the inbound
  4. A

    SOLVED Routing MSC Number Range to FusionPBX Extensions

    Hi, The MSC is sending me the number range 7800028[3-7]. I would like calls to these numbers to be routed to the 800x extensions on FusionPBX. Could you please tell me where and how to create the dialplan in FusionPBX to route this range received from the MSC to the corresponding extensions...
  5. A

    silenceSupp to "ON"

    fixed with making : In FusionPBX, go to Advanced → Variables or edit the sofia profile directly: Navigate to Status → SIP Profiles Edit the relevant profile (e.g., internal or external) Look for or add the variable: suppress-cng = false
  6. A

    silenceSupp to "ON"

    Hi, How can I set "silenceSupp" to on instead of off? This parameter might be causing an issue with the SIP INVITE. v=0 o=FreeSWITCH 1781749491 1781749492 IN IP4 172.16.67.154 s=FreeSWITCH c=IN IP4 172.16.67.154 t=0 0 m=audio 24702 RTP/AVP 8 0 101 a=rtpmap:8 PCMA/8000 a=rtpmap:0 PCMU/8000...
  7. A

    Network out of order Error

    Hi, I received the following error from my provider. Is there any configuration required on FusionPBX to avoid this issue, or should the configuration be handled on the provider’s side? SIP/2.0 500 Server Internal Error Via: SIP/2.0/UDP 172.16.60.60;branch=z9hG4bK70NFB9vK9X5je;rport=5060...
  8. A

    Changing Internal SIP Port (FusionPBX)

    It is a strange behavior. I configured the same setup without registration, but the SIP trunk still does not come up. Based on your screenshot, the only difference I noticed is that in my case I am using an IP address instead of a hostname (machine name). Could this be the cause of the issue, or...
  9. A

    Changing Internal SIP Port (FusionPBX)

    Hi, Thank you for your feedback. I have changed the internal SIP port to 5070, and the softphones are now successfully registered after updating their configuration. However, I am still facing some confusion regarding the SIP trunk setup with my gateway provider. Specifically, I have not found a...
  10. A

    Changing Internal SIP Port (FusionPBX)

    Hi, Is it possible to change the default internal SIP port (5060) to another port? If yes, could you please advise how to configure the softphones to connect to FusionPBX using the new port? The objective is to free up port 5060 for use with the external profile. Thank you.
  11. A

    Create a new Trunk to MSC

    Hi, After checking with IT Security, I am now receiving SIP OPTIONS from the MSC. However, FreeSWITCH is not sending any response. During my investigation, I found that configuring an ACL on the server might be required. Could you please confirm whether adding an ACL would resolve this issue, or...
  12. A

    Create a new Trunk to MSC

    Hi, Currently, I am using port 5055 as the SIP source port on the external profile. On the gateway configuration, I am sending traffic to my proxy using destination IP:5060. The security team has confirmed that port 5060 is open, and I have also verified it using telnet, which confirms...
  13. A

    Create a new Trunk to MSC

    For port 5080, it cannot be used (only ports 5001 to 5064 are allowed from their side). I have already updated the ACL and iptables accordingly. Do you suggest using another port instead of 5080?
  14. A

    Create a new Trunk to MSC

    Attached the Logs requested
  15. A

    Create a new Trunk to MSC

    So what is missing, why I can't reach my endpoint destination?