Got a little confusion here. FreeSWITCH log: http://pastebin.freeswitch.org/21226 SIP trace: http://pastebin.freeswitch.org/21227 Both were taken once after each other but other than the timing, everything else remains the same. This is a vanilla install for FreeSWITCH Version 1.5.5b+git~20130724T035836Z~3ae87091e1 (git 3ae8709 2013-07-24 03:58:36Z). Just dialing a non existent number (98871002) from a registered user 1001. The hangup cause returned by the switch shows # mod_sofia.c:463 Channel sofia/internal/1001@10.211.55.3:50601 hanging up, cause: NORMAL_CLEARING However the SIP capture shows SIP/2.0 480 Temporarily Unavailable. This 480 is also showing by the switch mod_sofia.c:597 Responding to INVITE with: 480. I know the mapping is done by FreeSWITCH. In this case why 480, returned Normal Temporary Failure while the switch shows NORMAL_CLEARING? Is this because Q.850 returned is 16 and FreeSWITCH mapping for 16 is NORMAL_CLEARING? Or is there something I am missing. -- Thanks, Muhammad Naseer Bhatti
16 is normal clearing - they are the q850 names for the same thing. Why that's being done for 480 is another question - seeing the full call context and any Reason headers might shed might on that 480 maps to 41 not 16 iirc, but would be overridden by a Reason header or if something else was going on on the call such as calling the hangup after the bridge On Wednesday, July 24, 2013, Muhammad Naseer Bhatti wrote:
Got a little confusion here. FreeSWITCH log: http://pastebin.freeswitch.org/21226 SIP trace: http://pastebin.freeswitch.org/21227
Both were taken once after each other but other than the timing, everything else remains the same.
This is a vanilla install for FreeSWITCH Version 1.5.5b+git~20130724T035836Z~3ae87091e1 (git 3ae8709 2013-07-24 03:58:36Z). Just dialing a non existent number (98871002) from a registered user 1001. The hangup cause returned by the switch shows mod_sofia.c:463 Channel sofia/internal/1001@10.211.55.3:50601 hanging up, cause: NORMAL_CLEARING
However the SIP capture shows SIP/2.0 480 Temporarily Unavailable. This 480 is also showing by the switch mod_sofia.c:597 Responding to INVITE with: 480. I know the mapping is done by FreeSWITCH. In this case why 480, returned Normal Temporary Failure while the switch shows NORMAL_CLEARING? Is this because Q.850 returned is 16 and FreeSWITCH mapping for 16 is NORMAL_CLEARING?
Or is there something I am missing.
-- Thanks, Muhammad Naseer Bhatti
Missed you'd included the logs ;) As suspected, the 480 contains 16 so that's where normal clearing comes from 480 temporary failure is the SIP cause 16 Normal Clearing is the ISDN Q850 one Internally FS will use ISDN causes and map protocol specific ones between them (which isn't 1:1), Reason lets the endpoint override that mapping because its already providing the exact one On Wednesday, July 24, 2013, Steven Ayre wrote:
16 is normal clearing - they are the q850 names for the same thing.
Why that's being done for 480 is another question - seeing the full call context and any Reason headers might shed might on that
480 maps to 41 not 16 iirc, but would be overridden by a Reason header or if something else was going on on the call such as calling the hangup after the bridge
On Wednesday, July 24, 2013, Muhammad Naseer Bhatti wrote:
Got a little confusion here. FreeSWITCH log: http://pastebin.freeswitch.org/21226 SIP trace: http://pastebin.freeswitch.org/21227
Both were taken once after each other but other than the timing, everything else remains the same.
This is a vanilla install for FreeSWITCH Version 1.5.5b+git~20130724T035836Z~3ae87091e1 (git 3ae8709 2013-07-24 03:58:36Z). Just dialing a non existent number (98871002) from a registered user 1001. The hangup cause returned by the switch shows mod_sofia.c:463 Channel sofia/internal/1001@10.211.55.3:50601 hanging up, cause: NORMAL_CLEARING
However the SIP capture shows SIP/2.0 480 Temporarily Unavailable. This 480 is also showing by the switch mod_sofia.c:597 Responding to INVITE with: 480. I know the mapping is done by FreeSWITCH. In this case why 480, returned Normal Temporary Failure while the switch shows NORMAL_CLEARING? Is this because Q.850 returned is 16 and FreeSWITCH mapping for 16 is NORMAL_CLEARING?
Or is there something I am missing.
-- Thanks, Muhammad Naseer Bhatti
I think 480 is because as mentioned in the wiki "Unspecified causes codes (no value in the "SIP Equiv." column in the table) are translated to SIP "480 Temporarily Unavailable" by FreeSwitch." But why in this case both Q.850 and SIP Equiv cause not matching? -- Thanks, Muhammad Naseer Bhatti Steven Ayre wrote:
Missed you'd included the logs ;)
As suspected, the 480 contains 16 so that's where normal clearing comes from
480 temporary failure is the SIP cause 16 Normal Clearing is the ISDN Q850 one
Internally FS will use ISDN causes and map protocol specific ones between them (which isn't 1:1), Reason lets the endpoint override that mapping because its already providing the exact one
On Wednesday, July 24, 2013, Steven Ayre wrote:
16 is normal clearing - they are the q850 names for the same thing.
Why that's being done for 480 is another question - seeing the full call context and any Reason headers might shed might on that
480 maps to 41 not 16 iirc, but would be overridden by a Reason header or if something else was going on on the call such as calling the hangup after the bridge
On Wednesday, July 24, 2013, Muhammad Naseer Bhatti wrote:
Got a little confusion here. FreeSWITCH log: http://pastebin.freeswitch.org/21226 SIP trace: http://pastebin.freeswitch.org/21227
Both were taken once after each other but other than the timing, everything else remains the same.
This is a vanilla install for FreeSWITCH Version 1.5.5b+git~20130724T035836Z~3ae87091e1 (git 3ae8709 2013-07-24 03:58:36Z). Just dialing a non existent number (98871002) from a registered user 1001. The hangup cause returned by the switch shows # mod_sofia.c:463 Channel sofia/internal/1001@10.211.55.3:50601 hanging up, cause: NORMAL_CLEARING
However the SIP capture shows SIP/2.0 480 Temporarily Unavailable. This 480 is also showing by the switch mod_sofia.c:597 Responding to INVITE with: 480. I know the mapping is done by FreeSWITCH. In this case why 480, returned Normal Temporary Failure while the switch shows NORMAL_CLEARING? Is this because Q.850 returned is 16 and FreeSWITCH mapping for 16 is NORMAL_CLEARING?
Or is there something I am missing.
-- Thanks, Muhammad Naseer Bhatti
_________________________________________________________________________ Professional FreeSWITCH Consulting Services: consulting@freeswitch.org http://www.freeswitchsolutions.com
FreeSWITCH-powered IP PBX: The CudaTel Communication Server http://www.cudatel.com
Official FreeSWITCH Sites http://www.freeswitch.org http://wiki.freeswitch.org http://www.cluecon.com
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
Its because you continued in the dialplan after the attempted bridge and hungup with normal clearing by reaching the final app in the dialplan you would actually have to explicitly execute <action application="hangup" data="hangup_cause"/> or set continue_on_fail=false before calling bridge. On Wed, Jul 24, 2013 at 1:19 PM, Muhammad Naseer Bhatti <nbhatti@gmail.com>wrote:
I think 480 is because as mentioned in the wiki "Unspecified causes codes (no value in the "SIP Equiv." column in the table) are translated to SIP "480 Temporarily Unavailable" by FreeSwitch." But why in this case both Q.850 and SIP Equiv cause not matching?
-- Thanks, Muhammad Naseer Bhatti
Steven Ayre wrote:
Missed you'd included the logs ;)
As suspected, the 480 contains 16 so that's where normal clearing comes from
480 temporary failure is the SIP cause 16 Normal Clearing is the ISDN Q850 one
Internally FS will use ISDN causes and map protocol specific ones between them (which isn't 1:1), Reason lets the endpoint override that mapping because its already providing the exact one
On Wednesday, July 24, 2013, Steven Ayre wrote:
16 is normal clearing - they are the q850 names for the same thing.
Why that's being done for 480 is another question - seeing the full call context and any Reason headers might shed might on that
480 maps to 41 not 16 iirc, but would be overridden by a Reason header or if something else was going on on the call such as calling the hangup after the bridge
On Wednesday, July 24, 2013, Muhammad Naseer Bhatti wrote:
Got a little confusion here. FreeSWITCH log: http://pastebin.freeswitch.org/21226 SIP trace: http://pastebin.freeswitch.org/21227
Both were taken once after each other but other than the timing, everything else remains the same.
This is a vanilla install for FreeSWITCH Version 1.5.5b+git~20130724T035836Z~3ae87091e1 (git 3ae8709 2013-07-24 03:58:36Z). Just dialing a non existent number (98871002) from a registered user 1001. The hangup cause returned by the switch shows mod_sofia.c:463 Channel sofia/internal/1001@10.211.55.3:50601 hanging up, cause: NORMAL_CLEARING
However the SIP capture shows SIP/2.0 480 Temporarily Unavailable. This 480 is also showing by the switch mod_sofia.c:597 Responding to INVITE with: 480. I know the mapping is done by FreeSWITCH. In this case why 480, returned Normal Temporary Failure while the switch shows NORMAL_CLEARING? Is this because Q.850 returned is 16 and FreeSWITCH mapping for 16 is NORMAL_CLEARING?
Or is there something I am missing.
-- Thanks, Muhammad Naseer Bhatti
_________________________________________________________________________
Professional FreeSWITCH Consulting Services:consulting@freeswitch.orghttp://www.freeswitchsolutions.com
FreeSWITCH-powered IP PBX: The CudaTel Communication Serverhttp://www.cudatel.com
Official FreeSWITCH Siteshttp://www.freeswitch.orghttp://wiki.freeswitch.orghttp://www.cluecon.com
FreeSWITCH-users mailing listFreeSWITCH-users@lists.freeswitch.orghttp://lists.freeswitch.org/mailman/listinfo/freeswitch-users UNSUBSCRIBE:http://lists.freeswitch.org/mailman/options/freeswitch-usershttp://www.frees...
_________________________________________________________________________ Professional FreeSWITCH Consulting Services: consulting@freeswitch.org http://www.freeswitchsolutions.com
FreeSWITCH-powered IP PBX: The CudaTel Communication Server http://www.cudatel.com
Official FreeSWITCH Sites http://www.freeswitch.org http://wiki.freeswitch.org http://www.cluecon.com
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 GTALK/JABBER/PAYPAL:anthony.minessale@gmail.com IRC: irc.freenode.net #freeswitch FreeSWITCH Developer Conference sip:888@conference.freeswitch.org googletalk:conf+888@conference.freeswitch.org pstn:+19193869900
This is just a default install without even changing any passwords. And user 1001 (default users) just trying to call a non existent extension. No scripting or anything involved. The only thing changed was the SIP ports to 50601 and that's all. -- Thanks, Muhammad Naseer Bhatti Steven Ayre wrote:
16 is normal clearing - they are the q850 names for the same thing.
Why that's being done for 480 is another question - seeing the full call context and any Reason headers might shed might on that
480 maps to 41 not 16 iirc, but would be overridden by a Reason header or if something else was going on on the call such as calling the hangup after the bridge
On Wednesday, July 24, 2013, Muhammad Naseer Bhatti wrote:
Got a little confusion here. FreeSWITCH log: http://pastebin.freeswitch.org/21226 SIP trace: http://pastebin.freeswitch.org/21227
Both were taken once after each other but other than the timing, everything else remains the same.
This is a vanilla install for FreeSWITCH Version 1.5.5b+git~20130724T035836Z~3ae87091e1 (git 3ae8709 2013-07-24 03:58:36Z). Just dialing a non existent number (98871002) from a registered user 1001. The hangup cause returned by the switch shows # mod_sofia.c:463 Channel sofia/internal/1001@10.211.55.3:50601 hanging up, cause: NORMAL_CLEARING
However the SIP capture shows SIP/2.0 480 Temporarily Unavailable. This 480 is also showing by the switch mod_sofia.c:597 Responding to INVITE with: 480. I know the mapping is done by FreeSWITCH. In this case why 480, returned Normal Temporary Failure while the switch shows NORMAL_CLEARING? Is this because Q.850 returned is 16 and FreeSWITCH mapping for 16 is NORMAL_CLEARING?
Or is there something I am missing.
-- Thanks, Muhammad Naseer Bhatti
_________________________________________________________________________ Professional FreeSWITCH Consulting Services: consulting@freeswitch.org http://www.freeswitchsolutions.com
FreeSWITCH-powered IP PBX: The CudaTel Communication Server http://www.cudatel.com
Official FreeSWITCH Sites http://www.freeswitch.org http://wiki.freeswitch.org http://www.cluecon.com
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
participants (3)
-
Anthony Minessale
-
Muhammad Naseer Bhatti
-
Steven Ayre