Jeff swicegood
asked on
POTS trunk returns "Answered" ruining a ringall strategy --FreePBX
POTS trunk (OBi110 device) returns "Answered" ruining a ringall strategy --FreePBX. I am trying to ring some local IP phones and 3 trunks in a ringall stratedgy. But as soon as a call goes out on the OBi110 it reports "answered" and the call gets connected. It isn't really "answered". The ringall stops. This happens even though I have specified "Confirm Calls" in the ring group.
ASKER
Yes, I can make calls, no problem.
No, none of the numbers are getting a dialing error. Maybe some setting in the OBi about how it reports to the PBX?
No, none of the numbers are getting a dialing error. Maybe some setting in the OBi about how it reports to the PBX?
Look at your console and check when you make a normal call from an extension, when does the call show to be completed. Immediately or when the called party actually answers? I do not know that device but it appears to be a simple ATA. If it shows connected immediately, it is probably a configuration issue on the ATA. If not, I would look at the PBX call processing.
Do the same test with a call into the call distro group. If you reduce the number of external calls to one, does it still happen? Add a second external, does it still happen. Just trying to walk through it logically for lack of specific detail on the device or your PBX config.
Do the same test with a call into the call distro group. If you reduce the number of external calls to one, does it still happen? Add a second external, does it still happen. Just trying to walk through it logically for lack of specific detail on the device or your PBX config.
ASKER
Without using the ring group.
When I dial the number itself it does what it is supposed to and does not show connect until the call is answered.
But when I dial the Custom extension I have set up "1304" in which the dial field is configured Local/1336XXXXXXX@outbound
2013-12-28 21:44:22 Local/1336XXXXXXX@outbound
and then when the call is actually ended, a second entry for the call shows up in the call report:
2013-12-28 21:44:22 SIP/972-0a097370 972 "Jaga-room" <972> 1304 Local/1336XXXXXXX@outbound
When I dial the number itself it does what it is supposed to and does not show connect until the call is answered.
But when I dial the Custom extension I have set up "1304" in which the dial field is configured Local/1336XXXXXXX@outbound
2013-12-28 21:44:22 Local/1336XXXXXXX@outbound
and then when the call is actually ended, a second entry for the call shows up in the call report:
2013-12-28 21:44:22 SIP/972-0a097370 972 "Jaga-room" <972> 1304 Local/1336XXXXXXX@outbound
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
OK, that seems to work. Thanks a lot!
Glad to hear it... I have never tried it with Custom Extensions associated with External numbers. My guess is that the Custom Extension is still an extension on the system and as such tries to answer the inbound call before it processes the reason it is special. ?!?!?
Are one of the numbers you are dialing not ringing but getting an dialing error?