Summary: | ASTERISK-01411: [patch] Incoming SIP calls from SIP provider get wack channel names | ||
Reporter: | timecop (timecop) | Labels: | |
Date Opened: | 2004-04-14 19:32:52 | Date Closed: | 2004-09-25 02:51:26 |
Priority: | Minor | Regression? | No |
Status: | Closed/Complete | Components: | Core/General |
Versions: | Frequency of Occurrence | ||
Related Issues: | |||
Environment: | Attachments: | ( 0) sip.diff | |
Description: | Due to somewhat faulty logic for selecting incoming SIP channel name, incoming calls from a SIP provider (such as FWD) are created such as: SIP/1234-7a69 where 1234 is the FWD # asterisk is registered to. In case of multiple incoming calls from FWD, show channels looks something like: SIP/1234-acde SIP/1234-123d SIP/1234-341d And you cannot tell which REMOTE FWD number is actually calling. The ${CALLERID} (or whatever) variable is set correctly, but the channel name is wrong at that point and cannot be changed. Preliminary patch to fix this (needs testing) is attached. Please disregard the increasing of retransmit timeout in the patch, it is for a different problem. After applying, incoming FWD SIP calls are named correctly: SIP/23456-7a69 (call from 23456@FWD) SIP/210220-1234 (call from 23456@FWD) | ||
Comments: | By: Brian West (bkw918) 2004-04-15 22:42:51 Fix has been put in CVS this wasn't the exact fix but something to also fix the null peer side SIP/-asdf |