Search results

Hi @rollyt, Not knowing Simwood I am assuming they are a SIP provider. That being the case there should not be any specific configuration required to get them to work. Ensure that 1. You have your gateway configured (which will be the details that Simwood will have provided to you for the...

Hi @jeetz, What end devices are the clients using? Is there an option to display the company based on what @Adrian Fretwell said to the CLI of the end device? Depending on the end device you could have multiple lines configured for each ring group, but that could get quite messy. If this is...

Hi cnkrc, extension to extension calls ( be that soft phone ie MicroSip, Physical Sip Phone, ATA etc) should work as long as the extensions are registered. They should not need to have the IP Address added to the ACL as they register on 5060 which is the internal ACL and by default this is...

Ahh yes it does as MicroSIP is the provider sending the call to Fusion. You have given more detail on the exact same thing.

Provided that you only need to add the line <action application="sched_hangup" data="[+]<time>[ <hangup_cause>]"/> into the dial plan then in theory yes. I believe you will need to set a condition to match the extension in the dial plan that you don't want the hangup to apply to and a another...

It needs to be the IP from MicroSip as they are the ones sending you the call.

Don't mind me.... talk about going off half cocked! I compared the inbound calls from a working trunk with this new one and the invite message was different. I checked and saw that they were registered on a different server with our supplier. When I changed over the server it worked as...

Hi Adrian, How do you explain all of other inbound destinations that I have constructed in the exact same manner that operate correctly? Here is one of the other inbound routes that is build in the same way and works correctly. The difference with this is its destination, instead of an...

Hi Adrian, The 0 is only in the description of number and not in the regex section. Please see the snapshot. The destination is set by [caller_destination]=[61731800576]. This is what is received by the sip trunk in the invite message. I have set up the destination 2 ways to capture this (...

Hi All, I have a puzzling issue. I have just added a new trunk to our instance of Fusion and added in the destinations for the DID however the regex seems to be failing even though it matches. Please see the log excerpt below. I have tested both of the regex configurations on regex101.com...