Open Source Training Seminar FreePBX Paid Support

Ticket #1855 (closed Bugs: wontfix)

Opened 1 year ago

Last modified 1 year ago

calls coming in on pri with <blank> (null) calling number are not 'tagged' with ring group or followme prefix

Reported by: bongfrog Assigned to:
Priority: major Milestone: 2.3
Component: Ring Groups Version: 2.3-branch
Keywords: callerid pri ringgroup Cc:
Confirmation: SVN Revision (if applicable):
Backend Engine: All Backend Engine Version:

Description

calls coming in on pri (Qwest) (NI2) with <blank> or (null) calling number are not 'tagged' with ring group or followme prefix. CDR is correct, I placed NOOP and the callerid NAME is set after the dialparties.agi. Sip traces show the call is from "unknown" <sip:unknown@192.168.111.220>

this is recreatable using both ringgroups and followmes

Change History

03/19/07 15:28:37 changed by bongfrog

found issue to be Caller*ID presentation on a call set to prohibited caller id (set from the pri) from being set on out bound sip call legs hence the unknown.

solution

in macro-dial : exten => s,10,SetCallerPres?(allowed) exten => s,11,Set(CALLERID(all)=${CALLERID(name)}<${CALLERID(number)}>) exten => s,12,Dial(${ds})

there is undoubtly a better way / place to do this.

06/20/07 11:48:57 changed by p_lindheimer

  • version changed from 2.2.1 to 2.3-branch.

07/27/07 15:13:12 changed by p_lindheimer

  • status changed from new to closed.
  • resolution set to wontfix.

no setup able to reproduce this. If this is still and issue and you have a system that we can access to diagnose and determine a proper solution, then reopen the bug and let us know how we can get in contact with you (you can pm me on the forum also). Then we will be glad to see what we can do. Closing as wontfix until we have the means to address it.

Donate



Support
Download
Develop
Forums
News
Documentation
Paid Support
About

Paid Ads