partysip-dev
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: AW: [Partysip-dev] 481 after 183, CANCEL


From: Aymeric Moizard
Subject: Re: AW: [Partysip-dev] 481 after 183, CANCEL
Date: Fri, 26 Sep 2003 11:01:13 +0200 (CEST)

pspm_sfp_cancel_match_invite is the method that match CANCEL
with INVITE in partysip.

Aymeric

On Thu, 25 Sep 2003, Walter Schober wrote:

> Hi Aymeric!
>
> This was already on. Double checked this. And since I have the same
> problem now with my X-Ten Client on XP, this might be not Cisco related.
> Which check for no tag is this?
>
> Can you give me a hint, which part of the signalling causes this 481?
> E.g. why this reply is generated? How do you match INVITE-CANCEL?
>
> Thanks!
> Walter
>
> -----Urspr√ľngliche Nachricht-----
> Von: Aymeric Moizard [mailto:address@hidden
> Gesendet: Donnerstag, 25. September 2003 18:34
> An: Walter Schober
> Cc: 'This is the partysip mailing list'
> Betreff: Re: [Partysip-dev] 481 after 183, CANCEL
>
>
>
> If you look at the partysip configuration, it says:
>
> # With Cisco ATA (version v2.15 ata18x)
> # More generally, if you can't CANCEL calls, try to uncomment this:
>
> #disable_check_for_to_tag_in_cancel = on
>
> Try to enable this!
> Aymeric
>
> On Thu, 25 Sep 2003, Walter Schober wrote:
>
> > Hi there!
> >
> > Another thing that makes me wondering:
> > Setup: (A) SIPPS/X-Ten - ProxyA - PartySIP - Cisco 1700 (B)
> >
> > A invites B, B answers with 183 Session in progress (but is RINGING,
> > Grrr.)
> > A cancels B, PartySIP answers with 481 Call Leg down not exist.
> >
> > Any idea, why?
> >
> > Below the INVITE, 183, CANCEL, 481
> >
> > Walter
> >
> > ----------------------------------------------------------------------
> > --
> > --
> >
> > INVITE sip:address@hidden SIP/2.0
> > Via: SIP/2.0/UDP
> > 192.168.3.2:5060;branch=z9hG4bKf749f8bde9fb401ba6c4ba33e4b7b8f25.0
> > Via: SIP/2.0/UDP 192.168.3.34:5060;branch=z9hG4bKx6OJcm9nOd8lsSs
> > Via: SIP/2.0/UDP
> > 192.168.3.209;branch=z9hG4bKnp269796522-411b5598192.168.3.209
> > Record-Route:
> > <sip:192.168.3.2:5060;lr;psp=f4242eaacf0b1348e1e49697805f77c4>
> > Record-Route: <sip:192.168.3.34:5060;lr>
> > From: petzi09 <sip:address@hidden>;tag=1014c496
> > To: <sip:address@hidden>
> > Call-ID: address@hidden
> > CSeq: 1 INVITE
> > Contact: <sip:address@hidden>
> > max-forwards: 69
> > expires: 180
> > user-agent: Ahead SIPPS IP Phone Version 2.0.42.13
> > Content-Type: application/sdp
> > Accept: application/sdp
> > Content-Length:   245
> >
> > SIP/2.0 183 Session Progress
> > Via: SIP/2.0/UDP
> > 192.168.3.2:5060;branch=z9hG4bKf749f8bde9fb401ba6c4ba33e4b7b8f25.0,SIP
> > /2
> > .0/UDP
> > 192.168.3.34:5060;branch=z9hG4bKx6OJcm9nOd8lsSs,SIP/2.0/UDP
> > 192.168.3.209;branch=z9hG4bKnp269796522-411b5598192.168.3.209
> > From: petzi09 <sip:address@hidden>;tag=1014c496
> > To: <sip:address@hidden>
> > Date: Mon, 01 Mar 1993 04:35:08 GMT
> > Call-ID: address@hidden
> > Server: Cisco VoIP Gateway/ IOS 12.x/ SIP enabled
> > CSeq: 1 INVITE
> > Content-Type: application/sdp
> > Session: Media
> > Content-Length: 134
> >
> > CANCEL sip:address@hidden:5060 SIP/2.0
> > Via: SIP/2.0/UDP 192.168.3.34:5060;branch=z9hG4bKNr2L_jXdCBFnvs!
> > To: sip:address@hidden
> > From: petzi09 <sip:address@hidden>;tag=1014c496
> > Call-ID: address@hidden
> > CSeq: 1 CANCEL
> > Max-Forwards: 70
> > Contact: sip:address@hidden
> > Content-Type: application/sdp
> > Expires: 180
> > Record-Route:  <sip:192.168.3.34:5060;lr>
> > User-Agent: Ahead SIPPS IP Phone Version 2.0.42.13
> > Accept: application/sdp
> >
> > |WARNING| <sfp.c: 753> module sfp: No valid INVITE found; answer to
> > request with 481.!
> > | INFO2 | <psp_osip.c: 70> osip module: wake up!
> > | INFO1 | <udp.c: 816>
> > SIP/2.0 481 Call Leg/Transaction Does Not Exist
> > Via: SIP/2.0/UDP 192.168.3.34:5060;branch=z9hG4bKNr2L_jXdCBFnvs!
> > From: petzi09 <sip:address@hidden>;tag=1014c496
> > To: <sip:address@hidden>
> > Call-ID: address@hidden
> > CSeq: 1 CANCEL
> > Server: partysip/0.6.0
> > Content-Length: 0
> >
> >
> >
>
>




reply via email to

[Prev in Thread] Current Thread [Next in Thread]