SIP/2.0 200 OK

To: <sip:8646783182@63.86.212.154>;tag=bc5a80577e3d5642

From: <sip:8644679887@63.86.212.157>;tag=322BCA98-25A3

Call-ID: F429FDCE-30B011D8-BA0EDB9C-52307829@63.86.212.157

CSeq: 101 INVITE

Via: SIP/2.0/UDP 63.86.212.154;branch=z9hG4bKb2f4.035.0

Via: SIP/2.0/UDP 63.86.212.157:5060

Record-Route: <sip:8646783182@63.86.212.154;ftag=322BCA98-25A3;lr>

Timestamp: 1071766157

Contact: John Walter <sip:8646783182@63.86.212.155:5060>

Server: Sipura/SPA2000-1.0.20

Content-Length: 150

Allow: ACK, BYE, CANCEL, INFO, INVITE, NOTIFY, OPTIONS, PRACK, REFER

Supported: 100rel

Content-Type: application/sdp

v=0

o=- 88599 88599 IN IP4 192.168.0.101

s=-

c=IN IP4 63.86.212.155

t=0 0

m=audio 16404 RTP/AVP 0

a=rtpmap:0 PCMU/8000

a=ptime:20

a=sendrecv

‡?F&#0;&#0;&#0;&#0;&#0;&#0;&#0;&#0;&#0;&#0;&#0;&#0;&#0;&#0;&#0;

ˆN&#0;E"8@&#0;?Vš&#0;eBEACK sip:8646783182@63.86.212.155:5060 SIP/2.0

Record-Route: <sip:8646783182@63.86.212.154;ftag=322BCA98-25A3;lr>

Via: SIP/2.0/UDP 63.86.212.154;branch=0

Via: SIP/2.0/UDP 63.86.212.157:5060

From: <sip:8644679887@63.86.212.157>;tag=322BCA98-25A3

To: <sip:8646783182@63.86.212.154>;tag=bc5a80577e3d5642

Date: Thu, 18 Dec 2003 16:49:17 GMT

Call-ID: F429FDCE-30B011D8-BA0EDB9C-52307829@63.86.212.157

Max-Forwards: 5

Content-Length: 0

CSeq: 101 ACK

&#0;e?Vš}BYE sip:8644679887@63.86.212.157:5060 SIP/2.0

Via: SIP/2.0/UDP 63.86.212.155:5060;branch=z9hG4bK-b76fe29f

From: <sip:8646783182@63.86.212.154>;tag=bc5a80577e3d5642

To: <sip:8644679887@63.86.212.157>;tag=322BCA98-25A3

Call-ID: F429FDCE-30B011D8-BA0EDB9C-52307829@63.86.212.157

CSeq: 101 BYE

Max-Forwards: 70

Route: <sip:8646783182@63.86.212.154;ftag=322BCA98-25A3;lr>

User-Agent: Sipura/SPA2000-1.0.20

Content-Length: 0

?&#0;&#0;&#0;&#0;&#0;&#0;&#0;&#0;&#0;&#0;&#0;&#0;&#0;&#0;&#0;

ˆN&#0;E":@&#0;%?Vš&#0;ekSIP/2.0 481 Call/Transaction Does Not Exist

Via: SIP/2.0/UDP 63.86.212.155:5060;branch=z9hG4bK-b76fe29f

From: <sip:8646783182@63.86.212.154>;tag=bc5a80577e3d5642

To: <sip:8644679887@63.86.212.157>;tag=322BCA98-25A3

Call-ID: F429FDCE-30B011D8-BA0EDB9C-52307829@63.86.212.157

CSeq: 101 BYE

Contact: <sip:8644679887@63.86.212.148>

Server: Sip EXpress router (0.8.12 (i386/linux))

Content-Length: 0

Warning: 392 63.86.212.148:5060 "Noisy feedback tells: pid=20033 req_src_ip=63.86.212.154 req_src_port=5060 in_uri=sip:8644679887@63.86.212.148:5060 out_uri=sip:8644679887@63.86.212.148:5060 via_cnt==0"


-----Original Message-----
From: Andres [mailto:andres@telesip.net]
Sent: Thursday, December 18, 2003 3:25 PM
To: Darren Sessions; serusers@lists.iptel.org
Subject: Re: [Serusers] BYE Message Problem


On Thursday 18 December 2003 15:11, Darren Sessions wrote:
> Sipura Firmware is 1.0.20
>
> We are already in talks with Sipura about this issue as we found a bug for
> them yesterday. It appears though based on the Etheral traces and ngrep
> that the Sipura is sending the BYE messages - but SER is not forwarding
> them along.
Can you post all the messages here(INVITE...to ...BYE)?  Otherwise it is hard
to guess where the problem might be.  I'm sure Jiri or Jan can spot the error
right away. 

>
> We are using Ser 8.12 on a Sun Ultra 60 - and as I said before, all other
> instances work flawlessly.
>
> Thanks,
>
>  - Darren
>
> -----Original Message-----
> From: Andres [mailto:andres@telesip.net]
> Sent: Thursday, December 18, 2003 2:58 PM
> To: Darren Sessions; serusers@lists.iptel.org
> Subject: Re: [Serusers] BYE Message Problem
>
> On Thursday 18 December 2003 14:50, Darren Sessions wrote:
> > We also have a problem with BYE's not being sent from an on-net call
> > (sipura to sipura).
>
> What firmware version are you using?  We have been testing the SPA2000 for
> about 3 weeks now and have not seen this issue.
>
> > -----Original Message-----
> > From: Darren Sessions
> > Sent: Thursday, December 18, 2003 2:32 PM
> > To: 'serusers@lists.iptel.org'
> > Subject: RE: Serusers Digest, Vol 8, Issue 16
> > Importance: High
> >
> >
> > Situation:
> >
> > Endpoint is called Party (Sipura SPA2000)
> >
> > Calling Party is routed through from a TDM call and VoIP'd by Cisco 3640
> > router then sent to SER.
> >
> > Endpoint receives call - everything works. When the Sipura hangs up the
> > call, it sends a BYE to ser - but ser does not send the BYE to the router
> > to disconnect the TDM channel.
> >
> > All other situations result in a completed call with channels released on
> > the router just fine.
> >
> > After further inspection - we noticed that when the Sipura hangs up and
> > send the BYE to SER, SER responds with this:
> >
> >
> > SIP/2.0 481 Call/Transaction Does Not Exist
> > Via: SIP/2.0/UDP 11.11.111.155:5060;branch=z9hG4bK-b76fe29f
> > From: <sip:8646783182@22.22.222.154>;tag=bc5a80577e3d5642
> > To: <sip:8644679887@33.33.333.157>;tag=322BCA98-25A3
> > Call-ID: F429FDCE-30B011D8-BA0EDB9C-52307829@33.33.333.157
> > CSeq: 101 BYE
> > Contact: <sip:8644679887@44.44.444.148>
> > Server: Sip EXpress router (0.8.12 (i386/linux))
> > Content-Length: 0
> > Warning: 392 44.44.444.148:5060 "Noisy feedback tells:  pid=20033
> > req_src_ip=22.22.222.154 req_src_port=5060
> > in_uri=sip:8644679887@44.44.444.148:5060
> > out_uri=sip:8644679887@44.44.444.148:5060 via_cnt==0"
> >
> >
> > Any ideas?
> >
> > Thanks,
> >
> >  - Darren
> >
> > _______________________________________________
> > Serusers mailing list
> > serusers@lists.iptel.org
> > http://lists.iptel.org/mailman/listinfo/serusers