Dale Fredrikson
New Member
- Joined
- Nov 30, 2009
- Messages
- 16
- Reaction score
- 0
I've run into a problem with inbound calling that I've never seen before, and I'm hoping someone understands it better than I do. Two scenarios may shed light:
1) Inbound route is pointed at an extension with a phone registered. On an inbound call:
-- Caller hears ring tones.
-- Target phone rings.
When target phone is answered:
-- Caller continues to hear ring tones.
-- Target phone stops ringing.
-- Call is not connected.
2) Inbound route is pointed at an IVR. On an inbound call:
-- IVR does not play recording (at least, if it does, the caller can't hear it).
-- Dialable options have no effect.
-- Caller hears 20+ seconds of silence followed by that old ascending 3-tone beep of death that we've all heard.
-- Call is disconnected.
The PBX is a fresh install of IncrediblePBX 13-13.8 (Scientific Linux) on dedicated hardware behind a PfSense firewall, with trunks connected to Skyetel. And it's hard to find anything wrong. Outbound calls work no problem, with 2-way audio. The external and LAN IPs are properly entered in Asterisk SIP Settings and in sip_general_custom.conf. Port 5060 is forwarded to the pbx. Iptables has been updated to allow connection to Skyetel, and Skyetel shows 3 green lights for endpoint health, and also shows the DID has a green light for "inbound activity registered". The PBX shows peer connectivity for some, at least, of the Skyetel IPs:
Skyetel-EU 35.156.192.164 Yes Yes 5060 UNREACHABLE
Skyetel-Inbound 50.17.48.216 Yes Yes 5060 OK (41 ms)
Skyetel-NE 52.60.138.31 Yes Yes 5060 UNREACHABLE
Skyetel-NW 52.41.52.34 Yes Yes 5060 OK (76 ms)
Skyetel-SE 50.17.48.216 Yes Yes 5060 OK (41 ms)
Skyetel-SW 52.8.201.128 Yes Yes 5060 OK (59 ms)
For kicks, I tried my best to take the firewalls out of the picture to see if that would eliminate the problem. I (temporarily) replaced all the iptables rules with an "allow all" rule, and on the PfSense box I currently have TCP/UDP 5000-5082 & 10000-20000 forwarded to the PBX, with linked firewall rules -- even though I know neither TCP nor RTP should need to be forwarded. Result: No dice -- same behavior.
The log doesn't shed much light for me but it might for someone else, so I've attached log dumps for the 2 scenarios.
I'm stumped. Can anyone help me?
Regards,
Dale
1) Inbound route is pointed at an extension with a phone registered. On an inbound call:
-- Caller hears ring tones.
-- Target phone rings.
When target phone is answered:
-- Caller continues to hear ring tones.
-- Target phone stops ringing.
-- Call is not connected.
2) Inbound route is pointed at an IVR. On an inbound call:
-- IVR does not play recording (at least, if it does, the caller can't hear it).
-- Dialable options have no effect.
-- Caller hears 20+ seconds of silence followed by that old ascending 3-tone beep of death that we've all heard.
-- Call is disconnected.
The PBX is a fresh install of IncrediblePBX 13-13.8 (Scientific Linux) on dedicated hardware behind a PfSense firewall, with trunks connected to Skyetel. And it's hard to find anything wrong. Outbound calls work no problem, with 2-way audio. The external and LAN IPs are properly entered in Asterisk SIP Settings and in sip_general_custom.conf. Port 5060 is forwarded to the pbx. Iptables has been updated to allow connection to Skyetel, and Skyetel shows 3 green lights for endpoint health, and also shows the DID has a green light for "inbound activity registered". The PBX shows peer connectivity for some, at least, of the Skyetel IPs:
Skyetel-EU 35.156.192.164 Yes Yes 5060 UNREACHABLE
Skyetel-Inbound 50.17.48.216 Yes Yes 5060 OK (41 ms)
Skyetel-NE 52.60.138.31 Yes Yes 5060 UNREACHABLE
Skyetel-NW 52.41.52.34 Yes Yes 5060 OK (76 ms)
Skyetel-SE 50.17.48.216 Yes Yes 5060 OK (41 ms)
Skyetel-SW 52.8.201.128 Yes Yes 5060 OK (59 ms)
For kicks, I tried my best to take the firewalls out of the picture to see if that would eliminate the problem. I (temporarily) replaced all the iptables rules with an "allow all" rule, and on the PfSense box I currently have TCP/UDP 5000-5082 & 10000-20000 forwarded to the PBX, with linked firewall rules -- even though I know neither TCP nor RTP should need to be forwarded. Result: No dice -- same behavior.
The log doesn't shed much light for me but it might for someone else, so I've attached log dumps for the 2 scenarios.
I'm stumped. Can anyone help me?
Regards,
Dale