I have a trace of one leg only I can try to capture both legs.
But a 200 OK with a Reason header is a valid SIP message (below 200 OK forwarded by FreeSWITCH) ?


Frame 5: 957 bytes on wire (7656 bits), 957 bytes captured (7656 bits)
Ethernet II, Src: Hewlett-_f3:e9:2c (3c:d9:2b:f3:e9:2c), Dst: JuniperN_f6:ce:27 (78:19:f7:f6:ce:27)
Internet Protocol Version 4, Src: FreeSWITCH_IP (FreeSWITCH_IP), Dst: CUSTOMER_IP (CUSTOMER_IP)
User Datagram Protocol, Src Port: sip (5060), Dst Port: sip (5060)
Session Initiation Protocol (200)
    Status-Line: SIP/2.0 200 OK
    Message Header
        Via: SIP/2.0/UDP CUSTOMER_IP:5060;branch=z9hG4bK00E0F510095D15ED848E0A88725A
        Max-Forwards: 63
        From: <sip:cg@FreeSWITCH_IP>;tag=00E0F510095D15ED848E7A60E97C
        To: <sip:cd@FreeSWITCH_IP>;tag=5881vaN1reajB
        Call-ID: ae8f80003582-5417017f-60871148-3ad46cc0-745bf31@127.0.0.1
        CSeq: 14398 INVITE
        Contact: <sip:cd@FreeSWITCH_IP:5060;transport=udp>
        User-Agent: FS_1.2
        Allow: INVITE, ACK, BYE, CANCEL, OPTIONS, MESSAGE, INFO, REGISTER, REFER, NOTIFY
        Supported: timer, path, replaces
        Allow-Events: talk, hold, conference, refer
        Reason: Q.850;cause=16;text="NORMAL_CLEARING"
        Content-Type: application/sdp
        Content-Disposition: session
        Content-Length: 217
    Message Body


On Wed, Sep 17, 2014 at 10:09 PM, Steven Ayre <steveayre@gmail.com> wrote:
Can you post the sip trace for the call (all legs)

On 17 September 2014 19:54, Stephen Wilde <wstephen80@gmail.com> wrote:
Anyone can help me on that?

Stephen

On Tue, Sep 16, 2014 at 9:58 PM, Stephen Wilde <wstephen80@gmail.com> wrote:
I have a strange issue: some calls are dropped with a 200 OK containing the "Reason" header.
Is this valid?
The message flow is:

CUSTOMER ----     FS

INVITE ->

        <- 100 Trying
        <- 180 Ringing
        <- 200 OK (containing the Reason Header)
ACK ->

after some seconds...

BYE ->
BYE ->
BYE ->
BYE ->
BYE ->

The 200 OK sent by FreeSwitch contain a "Reason Header":

Reason: Q.850;cause=16;text="NORMAL_CLEARING"

And the call seems dropped and not connected in FreeSWITCH.
For the customer side the call seems connected with 200 OK (the customer ignore the Reason).
After some seconds, the customer try to disconnect the call with BYE but these messages are ignored by Freeswitch because the call was been already dropped.

It's valid the Reason inside the 200 OK? It's possible that this 200 OK has been forwarded by Freeswitch from the outbound leg.
Any advice for that?

Stephen









_________________________________________________________________________
Professional FreeSWITCH Consulting Services:
consulting@freeswitch.org
http://www.freeswitchsolutions.com

Official FreeSWITCH Sites
http://www.freeswitch.org
http://confluence.freeswitch.org
http://www.cluecon.com

FreeSWITCH-powered IP PBX: The CudaTel Communication Server
http://www.cudatel.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


_________________________________________________________________________
Professional FreeSWITCH Consulting Services:
consulting@freeswitch.org
http://www.freeswitchsolutions.com

Official FreeSWITCH Sites
http://www.freeswitch.org
http://confluence.freeswitch.org
http://www.cluecon.com

FreeSWITCH-powered IP PBX: The CudaTel Communication Server
http://www.cudatel.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