| Summary: | ASTERISK-18577: National prefix inserted even when caller ID not available | ||
| Reporter: | Kris Shaw (shawkris) | Labels: | |
| Date Opened: | 2011-09-19 12:37:41 | Date Closed: | 2011-09-22 16:34:40 |
| Priority: | Trivial | Regression? | Yes |
| Status: | Closed/Complete | Components: | Channels/chan_dahdi |
| Versions: | 1.8.6.0 | Frequency of Occurrence | Constant |
| Related Issues: | |||
| Environment: | DAHDI 2.5.0.1, Asterisk 1.8.6, LibPRI 1.4.12 | Attachments: | ( 0) jira_asterisk_18577_v1.8.patch |
| Description: | Issue 0013207/PRI-42 has re-occured. The national prefix is inserted even when no callerID is available. It looks like the extra code for 1.4/1.6 was not added to sig_pri.c/apply_plan_to_number. -- Accepting call from '0' to '1222' on channel 0/1, span 1 instead of -- Accepting call from '' to '1222' on channel 0/1, span 1 | ||
| Comments: | By: Leif Madsen (lmadsen) 2011-09-19 15:26:26.185-0500 You'll need to provide additional debug information to move this issue forward. I think starting with some ISDN/PRI debug information is going to be a good start. By: Richard Mudgett (rmudgett) 2011-09-19 15:45:31.996-0500 [^jira_asterisk_18577_v1.8.patch] should take care of this for all incoming numbers except the called number. Applying the prefix string to the called number to normalize it would affect dialplans so it could only be done to trunk. By: Kris Shaw (shawkris) 2011-09-19 16:04:21.178-0500 The patch applied cleanly to 1.8.6 so I'm testing that. For our environment, this patch should return the dialplan behavior back to what it was with 1.4.35. By: Leif Madsen (lmadsen) 2011-09-21 09:35:17.161-0500 Assigning to the reporter so they can provide feedback when they have tested if this patch solves the issue. By: Kris Shaw (shawkris) 2011-09-21 12:06:56.357-0500 No re-occurrence of '0' incoming numbers today. I am unable to test the application of prefixes to redirecting numbers as these are not sent by the PSTN. By: Leif Madsen (lmadsen) 2011-09-22 07:50:56.297-0500 Assigned to Richard to move this issue forward. Reporter states patch appears to resolve the issue. | ||