sanitycheck
Member
- Joined
- Mar 15, 2008
- Messages
- 71
- Reaction score
- 0
Problem: Asteridex pops up window saying it's ringing the extension, then disappears. The extension does not ring; no call is placed.
Gear: I have an Orgasmatron 2 system with a Digium TDM400 (1 FXO, 1 FXS) installed, one analog POTS trunk configured for inbound/outbound, and the VoicePulse FreePBX module configured for outbound dialing (only).
FreePBX has been upgraded to 2.5, and updated. Update-scripts and update-fixes have been run. Two extensions are configured, one SIP (701) and one for an analog phone in the FXS module (702).
All functions on the system work fine, with the exception of Asteridex. I configured Asteridex according to the Asteridex4 setup instructions, which included identifying and mapping the outbound trunk numbers into extensions_custom.conf. In this case I use 3 and 5 for the VoicePulse trunks. (The trunks probably don't matter at this point since Asteridex can't ring the extension, so an outbound call is never attempted.)
I did set the cookie by specifying the trunk (SIP/701). I also tried the analog extension as ZAP/702 with the same results. The default is the SIP/701 extension.
Clicking on a stock (airline phone number) entry, or a new entry make, brings up the pop-up window as expected:
The pop-up disappears after a few seconds.
Just yesterday I did a fresh Orgasmatron 2 install, and configured it with a similar TDM400 (1 FXO, 3 FXS) and the VoicePulse module (with account different from system above). It has one analog FXS port configured as extension 302. I set Asteridex to ZAP/302 in this case, but got the same results. The pop-up appears, but the extension does not ring. On this system I notice the (0) does not appear in the message, however.
I can't think of any modifications I made that would prevent Asteridex from ringing the extensions.
Any ideas?
Gear: I have an Orgasmatron 2 system with a Digium TDM400 (1 FXO, 1 FXS) installed, one analog POTS trunk configured for inbound/outbound, and the VoicePulse FreePBX module configured for outbound dialing (only).
FreePBX has been upgraded to 2.5, and updated. Update-scripts and update-fixes have been run. Two extensions are configured, one SIP (701) and one for an analog phone in the FXS module (702).
All functions on the system work fine, with the exception of Asteridex. I configured Asteridex according to the Asteridex4 setup instructions, which included identifying and mapping the outbound trunk numbers into extensions_custom.conf. In this case I use 3 and 5 for the VoicePulse trunks. (The trunks probably don't matter at this point since Asteridex can't ring the extension, so an outbound call is never attempted.)
I did set the cookie by specifying the trunk (SIP/701). I also tried the analog extension as ZAP/702 with the same results. The default is the SIP/701 extension.
Clicking on a stock (airline phone number) entry, or a new entry make, brings up the pop-up window as expected:
Code:
(0)
Extension SIP/701 is ringing now.
When SIP/701 answers, call to 18002478726 will be placed.
Just yesterday I did a fresh Orgasmatron 2 install, and configured it with a similar TDM400 (1 FXO, 3 FXS) and the VoicePulse module (with account different from system above). It has one analog FXS port configured as extension 302. I set Asteridex to ZAP/302 in this case, but got the same results. The pop-up appears, but the extension does not ring. On this system I notice the (0) does not appear in the message, however.
I can't think of any modifications I made that would prevent Asteridex from ringing the extensions.
Any ideas?