Summary: | ASTERISK-00155: Support native SIP transfer feature | ||
Reporter: | chriz (chriz) | Labels: | |
Date Opened: | 2003-08-23 12:43:59 | Date Closed: | 2004-09-25 02:40:13 |
Priority: | Major | Regression? | No |
Status: | Closed/Complete | Components: | Core/General |
Versions: | Frequency of Occurrence | ||
Related Issues: | |||
Environment: | Attachments: | ||
Description: | ... using the SIP "also:" field in the BYE message .... See field below for example. ****** ADDITIONAL INFORMATION ****** SEND >> 213.23.152.157:5060 BYE sip:500@213.23.152.157 SIP/2.0 Via: SIP/2.0/UDP 192.168.4.170:5060 From: chriz <sip:phone1@pbx.no-ip.org>;tag=164016830 To: <sip:500@pbx.no-ip.org>;tag=as2ee101fb Contact: <sip:phone1@192.168.4.170:5060> Call-ID: 9A943309-A9CA-47BD-BF78-F97760C9647D@192.168.4.170 CSeq: 27450 BYE Also: sip:600@pbx.no-ip.org User-Agent: X-Lite build 1059 Content-Length: 0 | ||
Comments: | By: Mark Spencer (markster) 2003-08-24 18:01:30 Is there any non-deprecated RFC that defines the BYE/Also method? By: chriz (chriz) 2003-08-24 18:17:25 It seems that the method is superceeded by rfc3515, is asterisk supporting this one ? BYE/also support would still be great for backward compatiblity. edited on: 08-24-03 18:04 By: Mark Spencer (markster) 2003-08-24 18:34:34 We support "REFER" method. In any case if there is no standard to reference i'm a bit leary to implement it. By: Mark Spencer (markster) 2003-08-25 10:06:48 Bye/Also support has been added although it logs a NOTICE that this is a deprecated feature of SIP. |