| Summary: | ASTERISK-03895: on multihomed PC Asterisk bad response blocks calls | ||
| Reporter: | manero (manero) | Labels: | |
| Date Opened: | 2005-04-08 08:11:50 | Date Closed: | 2011-06-07 14:10:34 |
| Priority: | Minor | Regression? | No |
| Status: | Closed/Complete | Components: | Core/General |
| Versions: | Frequency of Occurrence | ||
| Related Issues: | |||
| Environment: | Attachments: | ( 0) debug | |
| Description: | Configuration: Multihomed PC with 2 IP on one interface eth0: 192.168.1.127 and 62.168.4.1 with no routing between these two networks There is no way to initiate call for clients on 192.168.1.x due to SIP responses with IP 62.168.4.1 in headers/messages. SIP is listening only on 192.168.1.127. ****** ADDITIONAL INFORMATION ****** Example of call 204@192.168.1.20 -> 403@192.168.1.177 through Asterisk 192.168.1.127 (see atached file) | ||
| Comments: | By: manero (manero) 2005-04-08 08:31:37 By definition in Bug Placing Guidelines the severity is Major but I cannot find the way how to change it. Missing functionality in web interface. By: Brian West (bkw918) 2005-04-08 09:35:56 No this is not major... nor a block. /b By: Brian West (bkw918) 2005-04-08 09:39:02 the reason this isn't major or a block is 1. its atleast a duplicted more than once. 2. A patch exsists on this bug for this problem http://bugs.digium.com/bug_view_page.php?bug_id=0002358 /b By: Russell Bryant (russell) 2005-04-08 14:50:26 If this is a duplicate, is there any reason to keep this open? By: Brian West (bkw918) 2005-04-08 14:59:52 Nope! | ||