Extension Transfer() with DeutschlandLAN/ ALLIP

Hello,
We are happy or not…german Telecom switched our connection from ISDN to SIP. In Asterisk we used the Transfer()- command to realize an “CallDeflection” if nobody is still in company. The CallDeflection restarted the call routing and was working very well until the change of connection type. Now it stopped and I get this output:

– Goto (nightswitch-application,s,1)
– Executing [s@nightswitch-application:1] NoOp(“SIP/SIP-PROVIDER-9086444935e53e6bd18daf-00000761”, “Night switch application”) in new stack
– Executing [s@nightswitch-application:2] Set(“SIP/SIP-PROVIDER-9086444935e53e6bd18daf-00000761”, “CDR(InternalCalleridNum)=s”) in new stack
– Executing [s@nightswitch-application:3] Set(“SIP/SIP-PROVIDER-9086444935e53e6bd18daf-00000761”, “_CALLED=s”) in new stack
– Executing [s@nightswitch-application:4] Goto(“SIP/SIP-PROVIDER-9086444935e53e6bd18daf-00000761”, “DIALPLAN-APPLICATION-118639992,s,1”) in new stack
– Goto (DIALPLAN-APPLICATION-118639992,s,1)
– Executing [s@DIALPLAN-APPLICATION-118639992:1] Transfer(“SIP/SIP-PROVIDER-9086444935e53e6bd18daf-00000761”, “0123456789”) in new stack
– Executing [s@DIALPLAN-APPLICATION-118639992:2] NoOp(“SIP/SIP-PROVIDER-9086444935e53e6bd18daf-00000761”, “SIP-Header:”) in new stack
– Executing [s@DIALPLAN-APPLICATION-118639992:3] NoOp(“SIP/SIP-PROVIDER-9086444935e53e6bd18daf-00000761”, “Transfer-command: 0123456789”) in new stack
– Executing [s@DIALPLAN-APPLICATION-118639992:4] NoOp(“SIP/SIP-PROVIDER-9086444935e53e6bd18daf-00000761”, “Tr-Status==> SUCCESS”) in new stack
– Executing [s@DIALPLAN-APPLICATION-118639992:5] Wait(“SIP/SIP-PROVIDER-9086444935e53e6bd18daf-00000761”, “3”) in new stack
– Auto fallthrough, channel ‘SIP/SIP-PROVIDER-9086444935e53e6bd18daf-0000075e’ status is ‘UNKNOWN’
– Executing [h@DIALPLAN-APPLICATION-118639992:1] Transfer(“SIP/SIP-PROVIDER-9086444935e53e6bd18daf-0000075e”, “0123456789”) in new stack
– Executing [h@DIALPLAN-APPLICATION-118639992:2] NoOp(“SIP/SIP-PROVIDER-9086444935e53e6bd18daf-0000075e”, “SIP-Header:”) in new stack
– Executing [h@DIALPLAN-APPLICATION-118639992:3] NoOp(“SIP/SIP-PROVIDER-9086444935e53e6bd18daf-0000075e”, “Transfer-command: 0123456789”) in new stack
– Executing [h@DIALPLAN-APPLICATION-118639992:4] NoOp(“SIP/SIP-PROVIDER-9086444935e53e6bd18daf-0000075e”, “Tr-Status==> FAILURE”) in new stack
– Executing [h@DIALPLAN-APPLICATION-118639992:5] Wait(“SIP/SIP-PROVIDER-9086444935e53e6bd18daf-0000075e”, “3”) in new stack
== Spawn extension (DIALPLAN-APPLICATION-118639992, h, 5) exited non-zero on ‘SIP/SIP-PROVIDER-9086444935e53e6bd18daf-0000075e’
– Auto fallthrough, channel ‘SIP/SIP-PROVIDER-9086444935e53e6bd18daf-0000075f’ status is ‘UNKNOWN’
– Executing [h@DIALPLAN-APPLICATION-118639992:1] Transfer(“SIP/SIP-PROVIDER-9086444935e53e6bd18daf-0000075f”, “0123456789”) in new stack
– Executing [h@DIALPLAN-APPLICATION-118639992:2] NoOp(“SIP/SIP-PROVIDER-9086444935e53e6bd18daf-0000075f”, “SIP-Header:”) in new stack
– Executing [h@DIALPLAN-APPLICATION-118639992:3] NoOp(“SIP/SIP-PROVIDER-9086444935e53e6bd18daf-0000075f”, “Transfer-command: 0123456789”) in new stack
– Executing [h@DIALPLAN-APPLICATION-118639992:4] NoOp(“SIP/SIP-PROVIDER-9086444935e53e6bd18daf-0000075f”, “Tr-Status==> FAILURE”) in new stack
– Executing [h@DIALPLAN-APPLICATION-118639992:5] Wait(“SIP/SIP-PROVIDER-9086444935e53e6bd18daf-0000075f”, “3”) in new stack
== Spawn extension (DIALPLAN-APPLICATION-118639992, h, 5) exited non-zero on ‘SIP/SIP-PROVIDER-9086444935e53e6bd18daf-0000075f’
– Auto fallthrough, channel ‘SIP/SIP-PROVIDER-9086444935e53e6bd18daf-00000760’ status is ‘UNKNOWN’
– Executing [h@DIALPLAN-APPLICATION-118639992:1] Transfer(“SIP/SIP-PROVIDER-9086444935e53e6bd18daf-00000760”, “0123456789”) in new stack
– Executing [h@DIALPLAN-APPLICATION-118639992:2] NoOp(“SIP/SIP-PROVIDER-9086444935e53e6bd18daf-00000760”, “SIP-Header:”) in new stack
– Executing [h@DIALPLAN-APPLICATION-118639992:3] NoOp(“SIP/SIP-PROVIDER-9086444935e53e6bd18daf-00000760”, “Transfer-command: 0123456789”) in new stack
– Executing [h@DIALPLAN-APPLICATION-118639992:4] NoOp(“SIP/SIP-PROVIDER-9086444935e53e6bd18daf-00000760”, “Tr-Status==> FAILURE”) in new stack
– Executing [h@DIALPLAN-APPLICATION-118639992:5] Wait(“SIP/SIP-PROVIDER-9086444935e53e6bd18daf-00000760”, “3”) in new stack
== Spawn extension (DIALPLAN-APPLICATION-118639992, h, 5) exited non-zero on ‘SIP/SIP-PROVIDER-9086444935e53e6bd18daf-00000760’
– Auto fallthrough, channel ‘SIP/SIP-PROVIDER-9086444935e53e6bd18daf-00000761’ status is ‘UNKNOWN’
– Executing [h@DIALPLAN-APPLICATION-118639992:1] Transfer(“SIP/SIP-PROVIDER-9086444935e53e6bd18daf-00000761”, “0123456789”) in new stack
– Executing [h@DIALPLAN-APPLICATION-118639992:2] NoOp(“SIP/SIP-PROVIDER-9086444935e53e6bd18daf-00000761”, “SIP-Header:”) in new stack
– Executing [h@DIALPLAN-APPLICATION-118639992:3] NoOp(“SIP/SIP-PROVIDER-9086444935e53e6bd18daf-00000761”, “Transfer-command: 0123456789”) in new stack
– Executing [h@DIALPLAN-APPLICATION-118639992:4] NoOp(“SIP/SIP-PROVIDER-9086444935e53e6bd18daf-00000761”, “Tr-Status==> FAILURE”) in new stack
– Executing [h@DIALPLAN-APPLICATION-118639992:5] Wait(“SIP/SIP-PROVIDER-9086444935e53e6bd18daf-00000761”, “3”) in new stack

This is the application (the “NoOp”- lines are for debugging only):

[DIALPLAN-APPLICATION-118639992]
exten => _[+0-9a-zA-Z*#]!,1,Transfer({DB(NIGHTCF/CF)}) exten => _[+0-9a-zA-Z*#]!,n,NoOp(SIP-Header:{SIP_HEADERS()})
exten => _[+0-9a-zA-Z*#]!,n,NoOp(Transfer-command: {DB(NIGHTCF/CF)}) exten => _[+0-9a-zA-Z*#]!,n,NoOp(Tr-Status==> {TRANSFERSTATUS})
exten => _[+0-9a-zA-Z*#]!,n,Wait(3)
exten => s,1,Transfer({DB(NIGHTCF/CF)}) exten => s,n,NoOp(SIP-Header:{SIP_HEADERS()})
exten => s,n,NoOp(Transfer-command: {DB(NIGHTCF/CF)}) exten => s,n,NoOp(Tr-Status==> {TRANSFERSTATUS})
exten => s,n,Wait(3)

I have no explanation why first is “success” and finaly “failure”…

Any suggestions are welcome.

Kind regards
SNR

Following fixed up for the assumed results of failing to use </> when posting to the forum:

exten => _[+0-9a-zA-Z*#]!,1,Transfer(${DB(NIGHTCF/CF)})

This pattern matches all the special extensions, including h, as well as s. It is very similar to “_.” which is discouraged for that reason.

You cannot do things which are only valid on a live channel from within the h extension.

This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.