Atsak,
I have been going back and forth with vitelity. The DIDWW site allows for mapping their number to a provider. Their default is
[email protected]. From my understanding that would push it into vitelity, vitelity would be able to route it to me. So I went down that path and then finally realized that the sip5.vitelity.net is not the same inbound that I have from vitelity
I changed it to that, worked with DIDWW and finally came up with it is being rejected by Vitelity. After talking to vitelity, I got 3 different answers frooooom 3 different people in their tech support department. I got a yes, a no and a maybe. So the yes person, after going back and forth stated that they could, but it would be some custom map that they would have to do and I would have to have a dedicated did for it. They stated it would be did@ip address. I have been waiting 3 days for them to figure that out.
I am starting to give up on them for this
So I am trying to figure out how to implement what you posted above.
I went into FreePBx. I took the sip.conf setup and put it in the sip_custom.conf file. I did not take the extension.conf setting at all. I restarted FreePBX. I went into reports/asterisk info/sip peers.
Here is what I see:
Name/username Host Dyn Forcerport ACL Port Status
103/103 x.x.x.x D N A 5060 OK (122 ms)
104/104 x.x.x.x D A 1024 OK (128 ms)
108/108 192.168.1.2 D A 5060 UNREACHABLE
3102/3102 (Unspecified) D N A 0 UNKNOWN
46.19.209.10 46.19.209.10 N 5060 Unmonitored
46.19.209.11 46.19.209.11 N 5060 Unmonitored
46.19.209.12 46.19.209.12 N 5060 Unmonitored
46.19.209.13 46.19.209.13 N 5060 Unmonitored
46.19.209.14 46.19.209.14 N 5060 Unmonitored
46.19.209.15 46.19.209.15 N 5060 Unmonitored
46.19.209.75 46.19.209.75 N 5060 Unmonitored
46.19.209.76 46.19.209.76 N 5060 Unmonitored
46.19.209.77 46.19.209.77 N 5060 Unmonitored
46.19.209.78 46.19.209.78 N 5060 Unmonitored
46.19.209.79 46.19.209.79 N 5060 Unmonitored
46.19.209.80 46.19.209.80 N 5060 Unmonitored
46.19.210.10 46.19.210.10 N 5060 Unmonitored
46.19.210.11 46.19.210.11 N 5060 Unmonitored
46.19.210.12 46.19.210.12 N 5060 Unmonitored
46.19.210.13 46.19.210.13 N 5060 Unmonitored
46.19.210.14 46.19.210.14 N 5060 Unmonitored
46.19.210.15 46.19.210.15 N 5060 Unmonitored
46.19.210.75 46.19.210.75 N 5060 Unmonitored
46.19.210.76 46.19.210.76 N 5060 Unmonitored
46.19.210.77 46.19.210.77 N 5060 Unmonitored
46.19.210.78 46.19.210.78 N 5060 Unmonitored
46.19.210.79 46.19.210.79 N 5060 Unmonitored
46.19.210.80 46.19.210.80 N 5060 Unmonitored
vitel-inbound/x 64.2.142.28 N 5060 Unmonitored
vitel-outbound/x 64.2.142.87 N 5060 Unmonitored
30 sip peers [Monitored: 2 online, 2 offline Unmonitored: 26 online, 0 offline]
So things look good here
In Freepbx, I have an inbound route. That route is the full Chinese number with country/area code - 861084054888 - I have that route go to an IVR.
At Diddww - I have a custom server for mapping. The customer server settings are:
Ip Address or domain - my PBXiaf at RentPBX
Protocol: Sip
Preferred Server: USA
CLI Format: raw (I have tried e164)
I am getting fails to connect.
At this point, I just want it to work. If I have to get another company other than Vitelity to take the inbound call, that's fine. If I can get it to work as an inbound with PBXiaf, that is fine.
Any ideas?
Thanks.
dave