Recent content by neiltancock

Hi folks, I hope you're all keeping safe and well. Would anyone be prepared to spend a few hours online with me helping me get to grips with some thihngs I just don't understand with FusionPBX? I have it up and running, I've secured it and set up extensions and trunks and can call in and out...

Ok, after being dug out of a hole by @KonradSC I now have inbound calls working! Here are the Gateway settings, with [Advanced] selected: Gateway: <Your gateway name> Username: SIP AOR Username Password: SIP AOR Password Proxy: single-01.proxy.voip.co.uk Register: True Auth User Name: SIP...

Ok, from what I can see the regex is pulling the correct DDI but attaching the host/domain voip.co.uk to it. Is that right?

Here's the SIP invite: xINVITE sip:gw+2141c506-de0a-4fd8-9c74-dfd134407499@77.74.195.12:5080;transport=udp;gw=2141c506-de0a-4fd8-9c74-dfd134407499 SIP/2.0 193.203.210.39:5060 77.74.195.12:5080 xVia: SIP/2.0/UDP...

The call isn't getting as far as being entered into the CDR, this is the call in freeswitch.log: ----------------------<SNIP>-------------------- b3cf173a-8184-406c-b861-eebac754035f 2019-01-24 01:31:21.209854 [DEBUG] switch_channel.c:1296 EXPORT (export_vars) [call_direction]=[inbound]...

Hmm. I changed it so it looks like this now: I removed all the various combinations of destinations I had tried and just have a single destination of 02392008648. I get busy tone now. Here's the SIP invite: │INVITE...

The complete SIP invite: │INVITE sip:gw+2141c506-de0a-4fd8-9c74-dfd134407499@77.74.195.12:5080;transport=udp;gw=2141c506-de0a-4fd8-9c74-dfd134407499 SIP/2.0 193.203.210.29:6060 77.74.195.12:5080 │Via...

WOW! That is a lot of great information. sip_to_uri has the correct data, as does sip_to_user sip_to_uri = 02392008648@proxy.voip.co.uk sip_to_user = 02392008648

Thank you KonradSC. sngrep appears to show a correct interaction: INVITE 07931828049@proxy.voip.co 02392008648@proxy.voip.co 6 193.203.210.29:6060 xx.xx.xx.xx:5080 COMPLETED But the CDR data shows the To: as 5e0107773a which is the account username: Here's a grep of the...

Hey KonradSC, many thanks for the response. I'm ex-Asterisk so please forgive my newbie stumbling. I've got a log of an entire call coming in here: https://pastebin.com/7Cr6NbBY From what I can see it's picking up caller_destination incorrectly: [caller_destination]=[5e0107773a] It should be...

My SIP provider provides incoming destination/DDI information in a weird way. Instead of providing the DID in the DID value it provides the SIP account username. The DDI data is in the SIP To: part of the header. This is the Asterisk code I use to extract the correct DDI and then pass the call...

Ok, I have one more question please. This provider provides incoming destination/DDI information in a weird way. Instead of providing the DID in the DID value it provides the SIP account username. The DDI data is in the SIP To: part of the header. This is the Asterisk code I use to...

Thank you sir! Reinstalling as Debian 9 had me up and running and the new trunk registered. I'll RTFM about inbound and outbound and then post the settings here.

Thank you DigitalDaz! I'll take a look at the logs. Which OS do you think suits FusionPBX best? I use CentOS a lot but am happy with Ubuntu & Debian too.

Hi all, does anyone have experience of setting up with voip.co.uk / Firstccom Europe in the UK? I've used this provider for a while but this is my first time setting up using FusionPBX. The provider requires you to register for inbound and authenticate with a username and password for outbound...