Re: [asterisk-users] Allow Header
Hi, asterisk version is 1.4.13 rich... On Tue, Nov 10, 2009 at 7:01 AM, Tilghman Lesher tles...@digium.com wrote: On Monday 09 November 2009 15:38:54 Coco Richard wrote: i'm not sure to understand. Asterisk does support SIP INFO, so why doesn't Asterisk add the INFO Method in the 200OK Response? You must be using Asterisk 1.2. This is the only version that I could find that does not put the INFO tag into the Allow header. Asterisk 1.4 and all versions greater supply the INFO tag as standard. Given that 1.2 is in security-only fix mode now, this is not going to be changed in SVN or in any subsequent 1.2 release (if any). You're welcome to change the ALLOWED_METHODS define in the top of chan_sip.c and recompile, however. -- Tilghman Lesher Digium, Inc. | Senior Software Developer twitter: Corydon76 | IRC: Corydon76-dig (Freenode) Check us out at: www.digium.com www.asterisk.org ___ -- Bandwidth and Colocation Provided by http://www.api-digital.com -- asterisk-users mailing list To UNSUBSCRIBE or update options visit: http://lists.digium.com/mailman/listinfo/asterisk-users ___ -- Bandwidth and Colocation Provided by http://www.api-digital.com -- asterisk-users mailing list To UNSUBSCRIBE or update options visit: http://lists.digium.com/mailman/listinfo/asterisk-users
Re: [asterisk-users] Allow Header
I took a look in chan_sip.c an for 1.4.13 ALLOWED_METHODS doesn't add INFO. So I will upgrade to 1.6... thank you for the replies... rich... On Tue, Nov 10, 2009 at 9:21 AM, Coco Richard richard.kingc...@gmail.com wrote: Hi, asterisk version is 1.4.13 rich... On Tue, Nov 10, 2009 at 7:01 AM, Tilghman Lesher tles...@digium.com wrote: On Monday 09 November 2009 15:38:54 Coco Richard wrote: i'm not sure to understand. Asterisk does support SIP INFO, so why doesn't Asterisk add the INFO Method in the 200OK Response? You must be using Asterisk 1.2. This is the only version that I could find that does not put the INFO tag into the Allow header. Asterisk 1.4 and all versions greater supply the INFO tag as standard. Given that 1.2 is in security-only fix mode now, this is not going to be changed in SVN or in any subsequent 1.2 release (if any). You're welcome to change the ALLOWED_METHODS define in the top of chan_sip.c and recompile, however. -- Tilghman Lesher Digium, Inc. | Senior Software Developer twitter: Corydon76 | IRC: Corydon76-dig (Freenode) Check us out at: www.digium.com www.asterisk.org ___ -- Bandwidth and Colocation Provided by http://www.api-digital.com -- asterisk-users mailing list To UNSUBSCRIBE or update options visit: http://lists.digium.com/mailman/listinfo/asterisk-users ___ -- Bandwidth and Colocation Provided by http://www.api-digital.com -- asterisk-users mailing list To UNSUBSCRIBE or update options visit: http://lists.digium.com/mailman/listinfo/asterisk-users
[asterisk-users] Allow Header
Hi all, In the INVITE from my SIP provider to Asterisk i can see that the Allow Header includes an INFO Method, but Asterisk replies a 200 OK with an Allow Header without INFO Method. But in the RFC3261 (20.5) you can read: All methods, including ACK and CANCEL, understood by the UA MUST be included in the list of methods in the Allow header field, when present. My SIP provider seems to refuse to send SIP INFO DTMF and releases the call, because in 200 OK from * there is no INFO Method in the Allow Header. Is that correct. thx richard ___ -- Bandwidth and Colocation Provided by http://www.api-digital.com -- asterisk-users mailing list To UNSUBSCRIBE or update options visit: http://lists.digium.com/mailman/listinfo/asterisk-users
Re: [asterisk-users] Allow Header
Yes, it's correct. Asterisk needs to advertise its support of that method in order for the other UA to be willing to send messages with that request method to it. Coco Richard wrote: Hi all, In the INVITE from my SIP provider to Asterisk i can see that the Allow Header includes an INFO Method, but Asterisk replies a 200 OK with an Allow Header without INFO Method. But in the RFC3261 (20.5) you can read: All methods, including ACK and CANCEL, understood by the UA MUST be included in the list of methods in the Allow header field, when present. My SIP provider seems to refuse to send SIP INFO DTMF and releases the call, because in 200 OK from * there is no INFO Method in the Allow Header. Is that correct. thx richard ___ -- Bandwidth and Colocation Provided by http://www.api-digital.com -- asterisk-users mailing list To UNSUBSCRIBE or update options visit: http://lists.digium.com/mailman/listinfo/asterisk-users -- Alex Balashov - Principal Evariste Systems Web : http://www.evaristesys.com/ Tel : (+1) (678) 954-0670 Direct : (+1) (678) 954-0671 ___ -- Bandwidth and Colocation Provided by http://www.api-digital.com -- asterisk-users mailing list To UNSUBSCRIBE or update options visit: http://lists.digium.com/mailman/listinfo/asterisk-users
Re: [asterisk-users] Allow Header
Hi Alex, i'm not sure to understand. Asterisk does support SIP INFO, so why doesn't Asterisk add the INFO Method in the 200OK Response? richard On Mon, Nov 9, 2009 at 6:38 PM, Alex Balashov abalas...@evaristesys.com wrote: Yes, it's correct. Asterisk needs to advertise its support of that method in order for the other UA to be willing to send messages with that request method to it. Coco Richard wrote: Hi all, In the INVITE from my SIP provider to Asterisk i can see that the Allow Header includes an INFO Method, but Asterisk replies a 200 OK with an Allow Header without INFO Method. But in the RFC3261 (20.5) you can read: All methods, including ACK and CANCEL, understood by the UA MUST be included in the list of methods in the Allow header field, when present. My SIP provider seems to refuse to send SIP INFO DTMF and releases the call, because in 200 OK from * there is no INFO Method in the Allow Header. Is that correct. thx richard ___ -- Bandwidth and Colocation Provided by http://www.api-digital.com -- asterisk-users mailing list To UNSUBSCRIBE or update options visit: http://lists.digium.com/mailman/listinfo/asterisk-users -- Alex Balashov - Principal Evariste Systems Web : http://www.evaristesys.com/ Tel : (+1) (678) 954-0670 Direct : (+1) (678) 954-0671 ___ -- Bandwidth and Colocation Provided by http://www.api-digital.com -- asterisk-users mailing list To UNSUBSCRIBE or update options visit: http://lists.digium.com/mailman/listinfo/asterisk-users ___ -- Bandwidth and Colocation Provided by http://www.api-digital.com -- asterisk-users mailing list To UNSUBSCRIBE or update options visit: http://lists.digium.com/mailman/listinfo/asterisk-users
Re: [asterisk-users] Allow Header
On Monday 09 November 2009 15:38:54 Coco Richard wrote: i'm not sure to understand. Asterisk does support SIP INFO, so why doesn't Asterisk add the INFO Method in the 200OK Response? You must be using Asterisk 1.2. This is the only version that I could find that does not put the INFO tag into the Allow header. Asterisk 1.4 and all versions greater supply the INFO tag as standard. Given that 1.2 is in security-only fix mode now, this is not going to be changed in SVN or in any subsequent 1.2 release (if any). You're welcome to change the ALLOWED_METHODS define in the top of chan_sip.c and recompile, however. -- Tilghman Lesher Digium, Inc. | Senior Software Developer twitter: Corydon76 | IRC: Corydon76-dig (Freenode) Check us out at: www.digium.com www.asterisk.org ___ -- Bandwidth and Colocation Provided by http://www.api-digital.com -- asterisk-users mailing list To UNSUBSCRIBE or update options visit: http://lists.digium.com/mailman/listinfo/asterisk-users
