| Summary: | ASTERISK-00138: More problems when using a bindaddr in chan_sip on multi-homed hosts. | ||
| Reporter: | oliver (oliver) | Labels: | |
| Date Opened: | 2003-08-20 21:02:51 | 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: | chan_sip still uses the IP-address of the interface it's talking through instead of the one specified as bindaddr in many places. The "Via:" and "Contact:"-header + several places in the body of the INVITE, for example. It even starts the session with "We're at <wrong IP-address> port <port>" on the console. This causes all kinds of problems, where the remote end tries to send requests or replies to an IP-address chan_sip isn't listening to. I suggest using the bindaddr consistently everywhere in the protocol, if it's set. Also see Bug-ID "0000026". ****** ADDITIONAL INFORMATION ****** RH9 Asterisk CVS-08/21/03-01:56:50 | ||
| Comments: | By: oliver (oliver) 2003-08-21 06:10:11 Hey Mark, Your fix in CVS seems to have done it, thanks! You can close this ticket. By: Mark Spencer (markster) 2003-08-21 10:42:54 Fixed in CVS | ||