| Summary: | ASTERISK-05124: [patch] Add "UNDEFINED" Call-ID support for OSP module | ||
| Reporter: | Di-Shi Sun (homesick) | Labels: | |
| Date Opened: | 2005-09-21 16:12:57 | Date Closed: | 2011-06-07 14:03:24 |
| Priority: | Major | Regression? | No |
| Status: | Closed/Complete | Components: | Channels/chan_sip/Interoperability |
| Versions: | Frequency of Occurrence | ||
| Related Issues: | |||
| Environment: | Attachments: | ( 0) undefined_callid.patch | |
| Description: | When Asterisk sends an OSP AuthReq to an OSP server, it is possible that it does not know and/or cannot create a Call-ID because it does not know the destination protocols. So, Asterisk should support "UNDEFINED" Call-ID. That means, Asterisk should sends "UNDEFINED" as Call-ID to the OSP server. Also, when it receives an OSP token with the "UNDEFINED" Call-ID, it should accept it. Since OSP Toolkit has supported this feature, Asterisk can directly support this feature by passing a zero as ospvNumberOfCallIds to OSPPTransactionRequestAuthorisation. ****** ADDITIONAL INFORMATION ****** Disclaimer signed by TransNexus, Inc. 1/27/05 | ||
| Comments: | By: Di-Shi Sun (homesick) 2005-09-22 12:19:43 Please postpone this ticket. Some more changes for this issue may be added soon. Thanks. By: Di-Shi Sun (homesick) 2005-09-23 11:10:30 Please erase or close this ticket. This issue is more complicated than we thought. We have not had a simple solution yet. Thanks. By: Michael Jerris (mikej) 2005-09-24 18:38:23 Suspended at OP request. | ||