Search results

It's not strange at all actually. When you reboot, you are clearing your routers/firewalls sessions. You are facing a networking issue; not one with the phones or PBX (which you can find the same reply to countless posts on this forum). I would recommend lowering your register time to 120 and...

I don't get what your issue is here? Both are valid implementations in Freeswitch; just depends on FusionPBX version.

@Newtovoip Toggle "Allow Abandon" and try again. There have been reports that a call will not reach an agent if that is set to default. Is this literally what it says, or has this been URL encoded or something by you pasting here?

Entirely depends on your delay. Send a screenshot of your setup to save time. I can't help with this. Plenty of active threads around that topic on this forum if you search.

That's how it is meant to work. Use "Follow Me" instead. On the first row, place your mobile number and set it to timeout sooner than the mobile voicemail time (probably 20 seconds or 50 seconds) On the second row, do *99<your_extension_number> with a "delay" of whatever your first timeout was.

Or Windows? XD

Are you saying it's successful in creating a domain? This used to happen on very old version of Fusion, but PHP running in the backend would still manage to create the domains; irrespective of the 504.

Can't you just use the in-built Caller ID Name and Caller ID Number that already exist in Ring Groups??

You've possibly blocked Fusion from creating the CDR entry. Run curl 127.0.0.1. If you get text back, then it's not that.

@DoktorBen it would better if you posted the solution to your own question so when this thread comes up in a site search or a major search engine there is an answer, instead of "please ignore".

Code hasn't been updated in two years; though Fusion has been updated daily. This shouldn't be a surprise but it might take a lot of work to get Vtiger running on the latest Fusion.

I have no idea what you are doing. Are you pasting XML into your terminal?

Come on DigiDaz, move all your customers to a single instance just for the experiment! :p

He's clocked a couple of hours on Fusion and Freeswitch. I would trust him too :p

From what I can see, you are forwarding the external call to another external party. Is that correct?

Not enough info in the half-log you submitted

For that, you will need to do some AJAX to open up a background request without updating the page. You'll have to implement a little bit of Javascript for that.

Hey @Johnpbx. How about opening a new thread instead of responding to a dead thread from over a year ago? A simple reference to this thread (even though it's entirely irrelevant) will do.

That's not the log. Find the call in /var/log/freeswitch/freeswitch.log. We need to know why Freeswitch is sending BUSY, not that it is sending busy.

Did you remove and try re-add the DID? Provide a example call log of the call returning busy.