| Summary: | ASTERISK-18259: Asterisk 1.8.5.0 not putting p-asserted into ringing or answered SIP messages | ||
| Reporter: | David Brillert (aragon) | Labels: | |
| Date Opened: | 2011-08-11 10:16:43 | Date Closed: | 2011-08-12 13:59:24 |
| Priority: | Minor | Regression? | |
| Status: | Closed/Complete | Components: | Channels/chan_sip/General |
| Versions: | 1.8.5.0 | Frequency of Occurrence | Constant |
| Related Issues: | |||
| Environment: | Polycom 3.x firmware | Attachments: | ( 0) deployment_server_p-asserted_failure_4115_to_4116.txt ( 1) lab_p-asserted_success_6010_to_6002.txt |
| Description: | I have a lab server configured with connected party p-asserted which works perfectly with connected party configuration. My deployment server uses identical software versions of Asterisk and Polycom firmware but never sends p-asserted in ringing or answered SIP messages. I have captured two SIP traces and sip.conf files from both systems: One from working system and one from system where SIP messages are not sent with p-asserted I cannot honestly tell if this is a bug in the deployment system... | ||
| Comments: | By: David Brillert (aragon) 2011-08-11 10:24:04.457-0500 BTW I ripped out a bunch of NOTIFY events from lab trace because it was making the lab trace harder to follow (lab uses lots of BLF)... By: David Brillert (aragon) 2011-08-12 13:59:07.100-0500 Ignore this problem, I have fixed the issue. It was a problem in the vendor’s Asterisk configuration. By: David Brillert (aragon) 2011-08-12 13:59:24.674-0500 Ignore this problem, I have fixed the issue. It was a problem in the vendor’s Asterisk configuration. | ||