When Dialing out 1+ the number i get the following
– Executing [12027796632@from-internal:1] Verbose(“SIP/4227-0001a9d3”, “11,----- Remote-Ext, Performing dundi lookup PRIMARY -----”) in new stack
> ----- Remote-Ext, Performing dundi lookup PRIMARY -----
– Executing [12027796632@from-internal:2] GotoIf(“SIP/4227-0001a9d3”, “1?checkBackup”) in new stack
– Goto (from-internal,12027796632,4)
– Executing [12027796632@from-internal:4] Verbose(“SIP/4227-0001a9d3”, “11,----- Remote-Ext, Performing dundi lookup BACKUP -----”) in new stack
> ----- Remote-Ext, Performing dundi lookup BACKUP -----
– Executing [12027796632@from-internal:5] GotoIf(“SIP/4227-0001a9d3”, “1?invalidExt”) in new stack
– Goto (from-internal,12027796632,7)
– Executing [12027796632@from-internal:7] Verbose(“SIP/4227-0001a9d3”, “2,----INVALID (dundi) results returned ----”) in new stack
== ----INVALID (dundi) results returned ----
– Executing [12027796632@from-internal:8] Goto(“SIP/4227-0001a9d3”, “i,1”) in new stack
– Goto (from-internal,i,1)
– Executing [i@from-internal:1] Playback(“SIP/4227-0001a9d3”, “invalid”) in new stack
if i dial the # without the 1 calls complete as expected but why would dundi be trying to look up a 1+ when there are no outbound routes with a 1 as the specific dial pattern all of our internal extensions start at 4