POLY ccx500 phone
Managed to register. Under address i had put in the freepbx ip So I changed and put the extn number. And it registered. Thank you all for the support
View ArticleProvider Not accepting response to 401 Auth challenge
bpatterson117: I don’t know where that contact sip:s@216.107.220.XXX is coming from. That’s what Asterisk sends by default (on a REGISTER request). If you have only one DID with the provider, set...
View ArticleFreePBX17 Two Transport RTP issue
Good afternoon, I have a setup with two Transports (Two Ethernet Cards) where the first is the PBX server and the second is my provider SIP trunk. The first one is 172.xx.xx.0/24 where the PBX server...
View ArticleSIP Trunk Registration Issue with BTCL (No Response from 10.200.10.4)
FreePBX Version: 17 Asterisk Version: 21 SIP Protocol Used: PJSIP / Chan_SIP Firewall/NAT Setup: Mikrotik Router Issue: I have successfully configured a SIP trunk with another provider (A), but BTCL...
View ArticleDAHDI struggles and getting an analog Sangoma A200 to work
Sorry, just saw this. Did you install with the --dahdi option ? It should work, do you have a case with us to take a look at your system ?
View ArticleProvider Not accepting response to 401 Auth challenge
The provider should not care about the user part of the contact; they should simply return the whole value, as the request URI, when sending incoming calls to you. Unfortunately, some providers try...
View ArticleDAHDI struggles and getting an analog Sangoma A200 to work
Yes, I installed with the --dahdi option. it does see the card on the first boot and seems to partially work but anytime i restart asterisk or make a change it won’t start again. I do have a case,...
View ArticleDAHDI struggles and getting an analog Sangoma A200 to work
Yes please, give me the case number so I can take a look. Thanks =)
View ArticleDAHDI struggles and getting an analog Sangoma A200 to work
Of course, right when you asked I did get a message that they are troubleshooting but case: 01799906 - Let me know if you have any questions about the system. Just a fresh load of Debian and followed...
View ArticleSIP Trunk Registration Issue with BTCL (No Response from 10.200.10.4)
I know nothing about BTCL, but for other IMS systems you would use something like: Username: +88024110XXXX SIP Server: ims.btcl.net.bd Outbound Proxy: sip:10.200.10.4\;lr\;hide From Domain:...
View ArticleSIP Trunk Registration Issue with BTCL (No Response from 10.200.10.4)
Do you have some connection with this provider to be on the same non-public space? Because that IP in the outbound proxy isn’t routable over the public Internet.
View ArticleSIP Trunk Registration Issue with BTCL (No Response from 10.200.10.4)
BlazeStudios: Because that IP in the outbound proxy isn’t routable over the public Internet. Sure, but the OP said he could ping it, so I assumed that BTCL is also his ISP.
View ArticleDAHDI struggles and getting an analog Sangoma A200 to work
It should be working now @jt-tech Make some tests, reboot your server, and let me know please =) Here is what I did: wanrouter hwprobe --verbose wancfg_dahdi At the end, I selected option 3 to stop...
View ArticleSIP Trunk Registration Issue with BTCL (No Response from 10.200.10.4)
theashikd: Checked network reachability (ping 10.200.10.4). ICMP or UDP ping? theashikd: +88024110XXXX@ims.btcl.net.bd User names containing @ are problematic. In any case, no response indicates a...
View ArticleSIP Trunk Registration Issue with BTCL (No Response from 10.200.10.4)
May be relevant: PBXact Ignoring phones on a specific subnet and therefore they cannot register - #4 by Lutiana
View ArticleSIP Trunk Registration Issue with BTCL (No Response from 10.200.10.4)
So it turns out that Sangoma’s support stuff uses 10.200.xx.yy for something, and when the support VPN is on, they push down a route to this subnet on their end. So check your routes on the PBX (cli:...
View ArticleSIP Trunk Registration Issue with BTCL (No Response from 10.200.10.4)
net-tools is deprecated in current OS’ and replaced by iproute2, so ip route if route -n doesn’t work
View ArticleSIP Trunk Registration Issue with BTCL (No Response from 10.200.10.4)
Good point, and just for reference the output for ip route would look like this: 10.200.0.0/24 via 172.16.0.1 dev tun0
View Article