| Summary: | ASTERISK-13393: SIP Remote-Party-ID not fully parsed | ||
| Reporter: | Tim King (timking) | Labels: | |
| Date Opened: | 2009-01-19 06:22:51.000-0600 | Date Closed: | 2009-01-20 17:04:53.000-0600 |
| Priority: | Minor | Regression? | No |
| Status: | Closed/Complete | Components: | Channels/chan_sip/Interoperability |
| Versions: | Frequency of Occurrence | ||
| Related Issues: | |||
| Environment: | Attachments: | ||
| Description: | Asterisk implementation only parses SIP tag Remote-Part-ID for number and privacy tag and nothing else. ****** ADDITIONAL INFORMATION ****** Some SIP agents such as those gateways made by Patton can send a Remote-Party-ID of the form Remote-Party-ID: <sip:642040@192.168.5.3>;party=calling to identify the caller, and Remote-Party-ID: <sip:642040@192.168.5.3>;party=called to identify the number called SIP standard appears to say the "calling" should be sent but not compulsory. Either way there's a small compatibility issue. | ||
| Comments: | By: Mark Michelson (mmichelson) 2009-01-20 17:04:53.000-0600 The remote party ID support in Asterisk is a bit weak at this time, but the work being done on issue 8824 will solve this as well as many other remote party ID reloated issues. It has been a while since anyone has commented on that issue, but the development branch created for that issue is still very active and should hopefully be merged into Asterisk trunk sometime within the first quarter of this year. | ||