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:tony@deathstar.freeswitch.org<sip%3Atony@deathstar.freeswitch.org>
;tag=352a2a46 To: "7016" <sip:7016@deathstar.freeswitch.org<sip%3A7016@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:tony@deathstar.freeswitch.org<sip%3Atony@deathstar.freeswitch.org>
;tag=aa3b2b1d To: "7016" <sip:7016@deathstar.freeswitch.org<sip%3A7016@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 <Prometheus001@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 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_minessale@hotmail.com <MSN%3Aanthony_minessale@hotmail.com> GTALK/JABBER/PAYPAL:anthony.minessale@gmail.com<PAYPAL%3Aanthony.minessale@gmail.com> IRC: irc.freenode.net #freeswitch FreeSWITCH Developer Conference sip:888@conference.freeswitch.org <sip%3A888@conference.freeswitch.org> iax:guest@conference.freeswitch.org/888 googletalk:conf+888@conference.freeswitch.org<googletalk%3Aconf%2B888@conference.freeswitch.org> pstn:213-799-1400