Extension Outbound Dialing No longer works after SIP ISN dialing is enables

dbaum

Guru
Joined
Jan 11, 2009
Messages
124
Reaction score
2
I installed the extension based ISN dialing support and ISN dialing works perfectly. Inbound ISN calls are properly delivered, and outbound calls are completed correctly.

HOWEVER, now I cannot originate a non-ISN outbound call. The call fails and returns congestion tone.

Log shows:
Executing [7039794466@from-internal:1] NoOp("SIP/2102-0935dde8", "Received incoming SIP connection from unknown peer to 7039794466") in new stack
-- Executing [7039794466@from-internal:2] Set("SIP/2102-0935dde8", "DID=7039794466") in new stack
-- Executing [7039794466@from-internal:3] Goto("SIP/2102-0935dde8", "s|1") in new stack
-- Goto (from-internal,s,1)
-- Executing [s@from-internal:1] Macro("SIP/2102-0935dde8", "hangupcall") in new stack
-- Executing [s@macro-hangupcall:1] GotoIf("SIP/2102-0935dde8", "1?skiprg") in new stack
-- Goto (macro-hangupcall,s,4)
-- Executing [s@macro-hangupcall:4] GotoIf("SIP/2102-0935dde8", "1?skipblkvm") in new stack
-- Goto (macro-hangupcall,s,7)
-- Executing [s@macro-hangupcall:7] GotoIf("SIP/2102-0935dde8", "1?theend") in new stack
-- Goto (macro-hangupcall,s,9)
-- Executing [s@macro-hangupcall:9] Hangup("SIP/2102-0935dde8", "") in new stack

This appears to be coming from [from-sip-external] context and should not be applied to this call.

:cryin:
 
I would check your context names for conflicts - example: same name used for a SIP trunk vs. ISN or username the same in both.
 

Members online

No members online now.

Forum statistics

Threads
26,688
Messages
174,412
Members
20,257
Latest member
Dempan
Get 3CX - Absolutely Free!

Link up your team and customers Phone System Live Chat Video Conferencing

Hosted or Self-managed. Up to 10 users free forever. No credit card. Try risk free.

3CX
A 3CX Account with that email already exists. You will be redirected to the Customer Portal to sign in or reset your password if you've forgotten it.
Back
Top