[Freeswitch-users] FreeSWITCH overrides/dose no accept hangup cause

[ivdreg ivdreg]

Hi All,

I have 2 FS boxes that communicates each other. First originates call to
second and on second FS perl scrips process a call. On some errors during
processing I hangup call with specific hangup cause and everything is OK.

For example:
SIP/2.0 503 Service Unavailable
Via: SIP/2.0/UDP 10.10.1.101;rport=5060;branch=z9hG4bK77698B1e1BZ3j
From: "11111111111" <sip:11111111111 at 10.10.1.101<sip%3A11111111111 at 10.10.1.101>
>;tag=X628H5HUDy86S
To: <sip:999999999999 at 10.10.1.110:7060>;tag=Ztg1r5S60rQFF
Call-ID: cca7076d-4b12-122e-44b6-7fd0651f7bfe
CSeq: 2802191 INVITE
User-Agent: FreeSWITCH-mod_sofia/1.0.6-svn-exported
Accept: application/sdp
Allow: INVITE, ACK, BYE, CANCEL, OPTIONS, MESSAGE, UPDATE, INFO, NOTIFY
Supported: timer, precondition, path, replaces
Allow-Events: talk, refer
*Reason: Q.850;cause=38;text="NETWORK_OUT_OF_ORDER"*
Content-Length: 0
Remote-Party-ID: "999999999999"
<sip:999999999999 at 10.10.1.110<sip%3A999999999999 at 10.10.1.110>
>;party=calling;privacy=off;screen=no

As you can see Q.850 cause is 38 - NETWORK OUT OF ORDER but on first FS
application info says:

variable_proto_specific_hangup_cause: [sip:503]
variable_sip_hangup_phrase: [Service Unavailable]
variable_originate_disposition: [NORMAL_TEMPORARY_FAILURE]

SIP Cause of both NORMAL_TEMPORARY_FAILURE and NETWORK_OUT_OF_ORDER is 503
and is the same but Q.850 cause is different.
Is it normal behavior for 1.0.6 ? Is it also possible first FS to respect
Q.850 cause ?

Thanks
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.freeswitch.org/pipermail/freeswitch-users/attachments/20101005/c6359158/attachment.html