Ishfaq Malik wrote: > Ishfaq Malik wrote: > >> Hi >> >> We run a hosted VoIP service for multiple customers off the same server >> and I'm having an odd issue with just one customer in particular. We're >> using realtime in a MySQL DB and this is their dialplan >> >> *************************** 1. row *************************** >> context: pcsu-Identifier >> exten: s >> priority: 1 >> app: Answer >> appdata: >> *************************** 2. row *************************** >> context: pcsu-Identifier >> exten: s >> priority: 2 >> app: Wait >> appdata: 2 >> *************************** 3. row *************************** >> context: pcsu-Identifier >> exten: s >> priority: 3 >> app: Set >> appdata: CALLERID(num)=${CALLERID(num)} >> *************************** 4. row *************************** >> context: pcsu-Identifier >> exten: s >> priority: 4 >> app: GotoIfTime >> appdata: 08:30-17:30|mon-fri|*|*?pcsu-Identifier-work|s|1 >> *************************** 5. row *************************** >> context: pcsu-Identifier >> exten: s >> priority: 5 >> app: Playback >> appdata: pcsu-voicemail-file >> *************************** 6. row *************************** >> context: pcsu-Identifier >> exten: s >> priority: 6 >> app: Voicemail >> appdata: 2...@pcsu-local|s >> *************************** 7. row *************************** >> context: pcsu-Identifier >> exten: s >> priority: 8 >> app: Hangup >> appdata: >> *************************** 8. row *************************** >> context: pcsu-Identifier-work >> exten: s >> priority: 1 >> app: Dial >> appdata: >> SIP/ukgeonum...@carrier&SIP/ukgeonum...@carrier&SIP/PCSU200&SIP/PCSU201&SIP/PCSU202&SIP/PCSU203&SIP/PCSU204&SIP/PCSU205&SIP/PCSU206|15 >> *************************** 9. row *************************** >> context: pcsu-Identifier-work >> exten: s >> priority: 2 >> app: Dial >> appdata: >> SIP/ukgeonum...@carrier&SIP/ukgeonum...@carrier&SIP/ukgeonum...@carrier&SIP/PCSU200&SIP/PCSU201&SIP/PCSU202&SIP/PCSU203&SIP/PCSU204&SIP/PCSU205&SIP/PCSU206|20 >> *************************** 10. row *************************** >> context: pcsu-Identifier-work >> exten: s >> priority: 3 >> app: Playback >> appdata: pcsu-voicemail-file >> *************************** 11. row *************************** >> context: pcsu-Identifier-work >> exten: s >> priority: 4 >> app: Voicemail >> appdata: 2...@pcsu-local|s >> *************************** 12. row *************************** >> context: pcsu-Identifier-work >> exten: s >> priority: 5 >> app: Hangup >> appdata: >> >> >> I know how daft it looks but they insisted on ringing real UK geographic >> numbers in the same step as SIP extensions. A while back I changed the >> initial Answer step to NoOp as the Answer step was distorting our CDR >> and I hadn't realised that Answer wasn't implicitly required. After I >> did this the caller stopped hearing a ringing tone when ringing into >> this dial plan. When I put the Answer step back in instead of the NoOp >> the caller could hear the ringing tone when dialling in again. >> >> I've tried replacing the Answer with Ringing but I still got silence >> while the extensions and numbers were ringing. >> >> Any thoughts on this would be helpful and I will be trying to replicate >> this on out test system. >> >> Thanks in advance >> >> Ish >> >> > I should also add, we have no problems with the caller hearing ringing > with any of the other dial plans on this server even though they start > with NoOp and not Answer > > Ish > Fixed it by using an explicit r option in the dial steps
Ish -- Ishfaq Malik Software Developer PackNet Ltd Office: 0161 660 3062 -- _____________________________________________________________________ -- Bandwidth and Colocation Provided by http://www.api-digital.com -- asterisk-users mailing list To UNSUBSCRIBE or update options visit: http://lists.digium.com/mailman/listinfo/asterisk-users