Hello, I finally solved it by using
<action application="hangup" data="${originate_disposition}"/> Best regards Peter Peter P GMX schrieb: > Hello Anthony, > > I did further testing on a second machine and found out the following: > After > <action application="set" data="sip_ignore_remote_cause=true"/> > <action application="hangup" data="NO_ANSWER"/> > > The called party receives a "NO_ANSWER" > and the calling party receives a "NORMAL_CLEARING" > > See the logs: > > Best regards > Peter > > > Logs: > ============================ > To called party: > U 82.xxx.9xx.163:5080 -> 82.xxx.9xx.165:5060 > CANCEL sip:0xxxxxxxxx...@21x.xx.xx.189:3273;line=fihb87zs SIP/2.0. > Via: SIP/2.0/UDP 82.xxx.9xx.163:5080;rport;branch=z9hG4bKg5SZ7829tHDae. > Route: <sip:82.xxx.9xx.165>. > Max-Forwards: 68. > From: "0xxxxxxxxx298" <sip:0xxxxxxxxx...@82.xxx.9xx.162>;tag=1mFgvS7t9Krtj. > To: <sip:0xxxxxxxxx...@21x.xx.xx.189:3273;line=fihb87zs>. > Call-ID: 9aab911f-22ce-122d-8686-001517956764. > CSeq: 120732503 CANCEL. > Reason: Q.850;cause=19;text="NO_ANSWER". > Content-Length: 0. > > To calling party: > U 82.xxx.9xx.163:5062 -> 82.xxx.9xx.165:5060 > SIP/2.0 480 Temporarily Unavailable. > Via: SIP/2.0/UDP 82.xxx.9xx.165;branch=z9hG4bKc08d.b2a0b296.0. > Via: SIP/2.0/UDP > 21x.xx.xx.189:2048;received=21x.xx.xx.189;branch=z9hG4bK-dnhr44fkakhd;rport=2048. > From: "0xxxxxxxxx298" <sip:0xxxxxxxxx...@mydomain.de>;tag=nvxy9h3rsk. > To: <sip:0xxxxxxxxx...@mydomain.de;user=phone>;tag=5y6B9FS9ZeUZB. > Call-ID: 3c49ea1f4563-8c3hia75cxuh. > CSeq: 2 INVITE. > User-Agent: FreeSWITCH-mod_sofia/1.0.trunk-14741M. > Allow: INVITE, ACK, BYE, CANCEL, OPTIONS, MESSAGE, UPDATE, INFO, > REGISTER, REFER, NOTIFY. > Supported: timer, precondition, path, replaces. > Allow-Events: talk, refer. > Reason: Q.850;cause=16;text="NORMAL_CLEARING". > Content-Length: 0. > > > 2009-09-23 12:51:37.008546 [NOTICE] switch_ivr_originate.c:2025 Hangup > sofia/external/0xxxxxxxxx...@21x.xx.xx.189:3273 [CS_CONSUME_MEDIA] > [NO_ANSWER] > 2009-09-23 12:51:37.008546 [DEBUG] switch_channel.c:1715 Send signal > sofia/external/0xxxxxxxxx...@21x.xx.xx.189:3273 [KILL] > 2009-09-23 12:51:37.008546 [DEBUG] switch_core_session.c:932 Send signal > sofia/external/0xxxxxxxxx...@21x.xx.xx.189:3273 [BREAK] > 2009-09-23 12:51:37.008546 [DEBUG] switch_ivr_originate.c:2169 Originate > Resulted in Error Cause: 19 [NO_ANSWER] > 2009-09-23 12:51:37.008546 [DEBUG] switch_core_state_machine.c:398 > (sofia/external/0xxxxxxxxx...@21x.xx.xx.189:3273) Running State Change > CS_HANGUP > 2009-09-23 12:51:37.008546 [INFO] mod_dptools.c:2098 Originate Failed. > Cause: NO_ANSWER > 2009-09-23 12:51:37.008546 [DEBUG] switch_core_state_machine.c:434 > (sofia/external/0xxxxxxxxx...@21x.xx.xx.189:3273) State HANGUP > EXECUTE sofia/internal/0xxxxxxxxx...@mydomain.de > set(sip_ignore_remote_cause=true) > 2009-09-23 12:51:37.008546 [DEBUG] mod_sofia.c:338 Channel > sofia/external/0xxxxxxxxx...@21x.xx.xx.189:3273 hanging up, cause: NO_ANSWER > 2009-09-23 12:51:37.008546 [DEBUG] mod_sofia.c:386 Sending CANCEL to > sofia/external/0xxxxxxxxx...@21x.xx.xx.189:3273 > 2009-09-23 12:51:37.008546 [DEBUG] switch_core_state_machine.c:46 > sofia/external/0xxxxxxxxx...@21x.xx.xx.189:3273 Standard HANGUP, cause: > NO_ANSWER > 2009-09-23 12:51:37.008546 [DEBUG] switch_core_state_machine.c:434 > (sofia/external/0xxxxxxxxx...@21x.xx.xx.189:3273) State HANGUP going to > sleep > 2009-09-23 12:51:37.008546 [DEBUG] switch_core_state_machine.c:479 > (sofia/external/0xxxxxxxxx...@21x.xx.xx.189:3273) State Change CS_HANGUP > -> CS_REPORTING > 2009-09-23 12:51:37.008546 [DEBUG] switch_core_session.c:932 Send signal > sofia/external/0xxxxxxxxx...@21x.xx.xx.189:3273 [BREAK] > 2009-09-23 12:51:37.008546 [DEBUG] switch_core_state_machine.c:398 > (sofia/external/0xxxxxxxxx...@21x.xx.xx.189:3273) Running State Change > CS_REPORTING > 2009-09-23 12:51:37.008546 [DEBUG] switch_core_state_machine.c:616 > (sofia/external/0xxxxxxxxx...@21x.xx.xx.189:3273) State REPORTING > 2009-09-23 12:51:37.008546 [DEBUG] switch_core_state_machine.c:53 > sofia/external/0xxxxxxxxx...@21x.xx.xx.189:3273 Standard REPORTING, > cause: NO_ANSWER > 2009-09-23 12:51:37.008546 [DEBUG] mod_dptools.c:748 > sofia/internal/0xxxxxxxxx...@mydomain.de SET > [sip_ignore_remote_cause]=[true] > 2009-09-23 12:51:37.008546 [DEBUG] switch_core_state_machine.c:616 > (sofia/external/0xxxxxxxxx...@21x.xx.xx.189:3273) State REPORTING going > to sleep > 2009-09-23 12:51:37.008546 [DEBUG] switch_core_state_machine.c:411 > (sofia/external/0xxxxxxxxx...@21x.xx.xx.189:3273) State Change > CS_REPORTING -> CS_DESTROY > 2009-09-23 12:51:37.008546 [DEBUG] switch_core_session.c:932 Send signal > sofia/external/0xxxxxxxxx...@21x.xx.xx.189:3273 [BREAK] > 2009-09-23 12:51:37.008546 [DEBUG] switch_core_session.c:1068 Session > 129 (sofia/external/0xxxxxxxxx...@21x.xx.xx.189:3273) Locked, Waiting on > external entities > 2009-09-23 12:51:37.008546 [NOTICE] switch_core_session.c:1086 Session > 129 (sofia/external/0xxxxxxxxx...@21x.xx.xx.189:3273) Ended > 2009-09-23 12:51:37.008546 [NOTICE] switch_core_session.c:1088 Close > Channel sofia/external/0xxxxxxxxx...@21x.xx.xx.189:3273 [CS_DESTROY] > EXECUTE sofia/internal/0xxxxxxxxx...@mydomain.de hangup() > 2009-09-23 12:51:37.008546 [DEBUG] switch_core_state_machine.c:559 > (sofia/external/0xxxxxxxxx...@21x.xx.xx.189:3273) Running State Change > CS_DESTROY > 2009-09-23 12:51:37.008546 [DEBUG] switch_core_state_machine.c:568 > (sofia/external/0xxxxxxxxx...@21x.xx.xx.189:3273) State DESTROY > 2009-09-23 12:51:37.008546 [DEBUG] mod_sofia.c:255 > sofia/external/0xxxxxxxxx...@21x.xx.xx.189:3273 SOFIA DESTROY > 2009-09-23 12:51:37.008546 [DEBUG] switch_core_state_machine.c:60 > sofia/external/0xxxxxxxxx...@21x.xx.xx.189:3273 Standard DESTROY > 2009-09-23 12:51:37.008546 [DEBUG] switch_core_state_machine.c:568 > (sofia/external/0xxxxxxxxx...@21x.xx.xx.189:3273) State DESTROY going to > sleep > 2009-09-23 12:51:37.008546 [NOTICE] mod_dptools.c:633 Hangup > sofia/internal/0xxxxxxxxx...@mydomain.de [CS_EXECUTE] [NORMAL_CLEARING] > 2009-09-23 12:51:37.008546 [DEBUG] switch_channel.c:1715 Send signal > sofia/internal/0xxxxxxxxx...@mydomain.de [KILL] > 2009-09-23 12:51:37.008546 [DEBUG] switch_core_session.c:932 Send signal > sofia/internal/0xxxxxxxxx...@mydomain.de [BREAK] > 2009-09-23 12:51:37.008546 [DEBUG] switch_core_state_machine.c:494 > (sofia/internal/0xxxxxxxxx...@mydomain.de) State EXECUTE going to sleep > 2009-09-23 12:51:37.008546 [DEBUG] switch_core_state_machine.c:398 > (sofia/internal/0xxxxxxxxx...@mydomain.de) Running State Change CS_HANGUP > 2009-09-23 12:51:37.008546 [DEBUG] switch_core_state_machine.c:434 > (sofia/internal/0xxxxxxxxx...@mydomain.de) State HANGUP > 2009-09-23 12:51:37.008546 [DEBUG] mod_sofia.c:338 Channel > sofia/internal/0xxxxxxxxx...@mydomain.de hanging up, cause: NORMAL_CLEARING > 2009-09-23 12:51:37.008546 [DEBUG] mod_sofia.c:397 Responding to INVITE > with: 480 > 2009-09-23 12:51:37.008546 [DEBUG] switch_core_state_machine.c:46 > sofia/internal/0xxxxxxxxx...@mydomain.de Standard HANGUP, cause: > NORMAL_CLEARING > 2009-09-23 12:51:37.008546 [DEBUG] switch_core_state_machine.c:434 > (sofia/internal/0xxxxxxxxx...@mydomain.de) State HANGUP going to sleep > 2009-09-23 12:51:37.008546 [DEBUG] switch_core_state_machine.c:479 > (sofia/internal/0xxxxxxxxx...@mydomain.de) State Change CS_HANGUP -> > CS_REPORTING > 2009-09-23 12:51:37.008546 [DEBUG] switch_core_session.c:932 Send signal > sofia/internal/0xxxxxxxxx...@mydomain.de [BREAK] > 2009-09-23 12:51:37.008546 [DEBUG] switch_core_state_machine.c:398 > (sofia/internal/0xxxxxxxxx...@mydomain.de) Running State Change CS_REPORTING > 2009-09-23 12:51:37.008546 [DEBUG] switch_core_state_machine.c:616 > (sofia/internal/0xxxxxxxxx...@mydomain.de) State REPORTING > 2009-09-23 12:51:37.008546 [DEBUG] switch_core_state_machine.c:53 > sofia/internal/0xxxxxxxxx...@mydomain.de Standard REPORTING, cause: > NORMAL_CLEARING > 2009-09-23 12:51:37.008546 [DEBUG] switch_core_state_machine.c:616 > (sofia/internal/0xxxxxxxxx...@mydomain.de) State REPORTING going to sleep > 2009-09-23 12:51:37.008546 [DEBUG] switch_core_state_machine.c:411 > (sofia/internal/0xxxxxxxxx...@mydomain.de) State Change CS_REPORTING -> > CS_DESTROY > 2009-09-23 12:51:37.008546 [DEBUG] switch_core_session.c:932 Send signal > sofia/internal/0xxxxxxxxx...@mydomain.de [BREAK] > 2009-09-23 12:51:37.008546 [DEBUG] switch_core_session.c:1068 Session > 128 (sofia/internal/0xxxxxxxxx...@mydomain.de) Locked, Waiting on > external entities > 2009-09-23 12:51:37.008546 [NOTICE] switch_core_session.c:1086 Session > 128 (sofia/internal/0xxxxxxxxx...@mydomain.de) Ended > 2009-09-23 12:51:37.008546 [NOTICE] switch_core_session.c:1088 Close > Channel sofia/internal/0xxxxxxxxx...@mydomain.de [CS_DESTROY] > 2009-09-23 12:51:37.008546 [DEBUG] switch_core_state_machine.c:559 > (sofia/internal/0xxxxxxxxx...@mydomain.de) Running State Change CS_DESTROY > 2009-09-23 12:51:37.008546 [DEBUG] switch_core_state_machine.c:568 > (sofia/internal/0xxxxxxxxx...@mydomain.de) State DESTROY > 2009-09-23 12:51:37.008546 [DEBUG] mod_sofia.c:255 > sofia/internal/0xxxxxxxxx...@mydomain.de SOFIA DESTROY > 2009-09-23 12:51:37.008546 [DEBUG] switch_core_state_machine.c:60 > sofia/internal/0xxxxxxxxx...@mydomain.de Standard DESTROY > 2009-09-23 12:51:37.008546 [DEBUG] switch_core_state_machine.c:568 > (sofia/internal/0xxxxxxxxx...@mydomain.de) State DESTROY going to sleep > > > > > > > > Anthony Minessale schrieb: > >> Here is what I get when I test it. >> you may want to look at your console for the blue Hangup lines and >> confirm it's your call to hangup >> >> >> <extension name="7016"> >> <condition field="destination_number" expression="^7016$"> >> <action application="set" data="sip_ignore_remote_cause=true"/> >> <action application="hangup" data="no_answer"/> >> </condition> >> </extension> >> >> send 644 bytes to udp/[72.128.89.126]:42988 at 14:34:29.043915: >> >> ------------------------------------------------------------------------ >> SIP/2.0 480 Temporarily Unavailable >> Via: SIP/2.0/UDP >> 10.0.1.8:50606;branch=z9hG4bK-d8754z-6077f64f00ed157e-1---d8754z-;rport=42988;received=72.128.89.126 >> From: "tony"<sip:t...@deathstar.freeswitch.org >> <mailto:sip%3at...@deathstar.freeswitch.org>>;tag=352a2a46 >> To: "7016" <sip:7...@deathstar.freeswitch.org >> <mailto:sip%3a7...@deathstar.freeswitch.org>>;tag=HUye00UQZKySQ >> Call-ID: N2Y1MWYwZjA2YzJlY2ZhY2VjYzRhNDZmMzczYWMwN2Q. >> CSeq: 1 INVITE >> User-Agent: The Guy In IRC IS WRONG >> Accept: application/sdp >> Allow: INVITE, ACK, BYE, CANCEL, OPTIONS, MESSAGE, UPDATE, INFO, >> REGISTER, REFER, NOTIFY >> Supported: timer, precondition, path, replaces >> Allow-Events: talk, refer >> Reason: Q.850;cause=19;text="NO_ANSWER" >> Content-Length: 0 >> >> >> <extension name="7016"> >> <condition field="destination_number" expression="^7016$"> >> <action application="set" data="sip_ignore_remote_cause=true"/> >> <action application="hangup" data="user_busy"/> >> </condition> >> </extension> >> >> >> send 630 bytes to udp/[72.128.89.126]:42988 at 14:35:31.286436: >> >> ------------------------------------------------------------------------ >> SIP/2.0 486 Busy Here >> Via: SIP/2.0/UDP >> 10.0.1.8:50606;branch=z9hG4bK-d8754z-223ae00e1829097e-1---d8754z-;rport=42988;received=72.128.89.126 >> From: "tony"<sip:t...@deathstar.freeswitch.org >> <mailto:sip%3at...@deathstar.freeswitch.org>>;tag=aa3b2b1d >> To: "7016" <sip:7...@deathstar.freeswitch.org >> <mailto:sip%3a7...@deathstar.freeswitch.org>>;tag=j4Q71UcUvvmcK >> Call-ID: NDcyNmQyYjY5YWQwOTI3MjZiZWFlZDQyNDIyZjZlMDA. >> CSeq: 1 INVITE >> User-Agent: The Guy In IRC IS WRONG >> Accept: application/sdp >> Allow: INVITE, ACK, BYE, CANCEL, OPTIONS, MESSAGE, UPDATE, INFO, >> REGISTER, REFER, NOTIFY >> Supported: timer, precondition, path, replaces >> Allow-Events: talk, refer >> Reason: Q.850;cause=17;text="USER_BUSY" >> Content-Length: 0 >> >> >> >> On Fri, Sep 18, 2009 at 2:53 AM, Peter P GMX <prometheus...@gmx.net >> <mailto:prometheus...@gmx.net>> wrote: >> >> Hello , >> >> I try to hangup aa call with a certain cause code. >> >> If the user dials a number which we currently do not serve we send >> <action application="set" data="sip_ignore_remote_cause=true"/> >> <action application="hangup" data="NO_ANSWER"/> >> which gives a >> "SIP/2.0 480 Temporarily Unavailable." Message , which is fine. >> >> For the target number being busy or having another state, we use this. >> <anti-action application="set" >> data="sip_ignore_remote_cause=true"/> >> <anti-action application="hangup" data="${hangup_cause}"/> >> which gives a >> "SIP/2.0 486 Busy Here."" Message , which is fine in case of Busy. >> >> However in both cases the SIP mssage has the following cause code: >> Reason: Q.850;cause=16;text="NORMAL_CLEARING". >> which can lead to problems when forwarding to a PSTN Gateway. >> >> How can we achieve, that the cause code is in sync with the deiivered >> message? >> >> We are on Trunk 14741M. >> >> Best regards >> Peter >> >> _______________________________________________ >> FreeSWITCH-users mailing list >> FreeSWITCH-users@lists.freeswitch.org >> <mailto:FreeSWITCH-users@lists.freeswitch.org> >> http://lists.freeswitch.org/mailman/listinfo/freeswitch-users >> UNSUBSCRIBE:http://lists.freeswitch.org/mailman/options/freeswitch-users >> http://www.freeswitch.org >> >> >> >> >> -- >> Anthony Minessale II >> >> FreeSWITCH http://www.freeswitch.org/ >> ClueCon http://www.cluecon.com/ >> Twitter: http://twitter.com/FreeSWITCH_wire >> >> AIM: anthm >> MSN:anthony_miness...@hotmail.com >> <mailto:msn%3aanthony_miness...@hotmail.com> >> GTALK/JABBER/PAYPAL:anthony.miness...@gmail.com >> <mailto:paypal%3aanthony.miness...@gmail.com> >> IRC: irc.freenode.net <http://irc.freenode.net> #freeswitch >> >> FreeSWITCH Developer Conference >> sip:8...@conference.freeswitch.org >> <mailto:sip%3a...@conference.freeswitch.org> >> iax:gu...@conference.freeswitch.org/888 >> <http://iax:gu...@conference.freeswitch.org/888> >> googletalk:conf+...@conference.freeswitch.org >> <mailto:googletalk%3aconf%2b...@conference.freeswitch.org> >> pstn:213-799-1400 >> ------------------------------------------------------------------------ >> >> _______________________________________________ >> FreeSWITCH-users mailing list >> FreeSWITCH-users@lists.freeswitch.org >> http://lists.freeswitch.org/mailman/listinfo/freeswitch-users >> UNSUBSCRIBE:http://lists.freeswitch.org/mailman/options/freeswitch-users >> http://www.freeswitch.org >> >> > > _______________________________________________ > FreeSWITCH-users mailing list > FreeSWITCH-users@lists.freeswitch.org > http://lists.freeswitch.org/mailman/listinfo/freeswitch-users > UNSUBSCRIBE:http://lists.freeswitch.org/mailman/options/freeswitch-users > http://www.freeswitch.org > > _______________________________________________ FreeSWITCH-users mailing list FreeSWITCH-users@lists.freeswitch.org http://lists.freeswitch.org/mailman/listinfo/freeswitch-users UNSUBSCRIBE:http://lists.freeswitch.org/mailman/options/freeswitch-users http://www.freeswitch.org