Thank you for the reply. I have tried unchecking the box for default asserted identity. I have tried checking the box. I did both of these things prior to sending a message to this list...and forgot to add that to my list of things that I have tried (frustration makes me forget to write things down).
The work around does not produce the desired result. If you need anything from me to help you such as a trace, log files, or whatever, please let me know. ------------------------------------------------------------------------ Heather L. Sanders Linux Systems Administrator Saginaw Valley State University 7400 Bay Road 374 Wickes Hall University Center, MI 48710 Office: (989) 964-2156 Mobile: (989) 326-3300 Email: [email protected] On 08/13/2010 08:47 AM, Tony Graziano wrote: > Undo what you have done and refer to this workaround... > > http://track.sipfoundry.org/browse/XX-8647 > > On Fri, Aug 13, 2010 at 8:42 AM, Heather L. Sanders <[email protected] > <mailto:[email protected]>> wrote: > > Dear sipX users: > > Three days ago, I upgraded my system to 4.2.1-018930 build34, and > since > then, I have not been able to get my caller ID settings to work > correctly. We use an ITSP provider, who provides us with phone > numbers > that are different that what we want displayed to the outside > world, so > I change the caller ID settings to display the correct number when > outgoing calls are made. > > However, since the upgrade, outgoing calls will only display the > default > number that I have configured in the PAI for the ITSP provider. I > have > taken the following steps to try to resolve the problem on my own: > > * Changed caller ID to be blocked, which has had no effect - the > number in the PAI still comes through. > * Configured individual caller ID settings - no effect, same > result. > * Removed and recreated the gateway for the ITSP provider. > * Called the provider and verified that nothing had changed at > their > end. > * Ran a packet trace on the call, and confirmed that the "From" > header was in fact incorrect....It displayed the phone number > configured in the PAI. > > I have attached a sipx-trace file from my pbx, which details calls > attempted to my mobile number. You will see where the caller id > information is incorrect, as the numbers should all be > '989964xxxx' numbers. > > I am open to suggestions on anything to try. This was working > perfectly > prior to the upgrade... > > -- > ------------------------------------------------------------------------ > Heather L. Sanders > Linux Systems Administrator > Saginaw Valley State University > 7400 Bay Road > 374 Wickes Hall > University Center, MI 48710 > Office: (989) 964-2156 > Mobile: (989) 326-3300 > Email: [email protected] <mailto:[email protected]> > > _______________________________________________ > sipx-users mailing list > [email protected] <mailto:[email protected]> > List Archive: http://list.sipfoundry.org/archive/sipx-users/ > > > > > -- > ====================== > Tony Graziano, Manager > Telephone: 434.984.8430 > sip: [email protected] > <mailto:[email protected]> > Fax: 434.984.8431 > > Email: [email protected] <mailto:[email protected]> > > LAN/Telephony/Security and Control Systems Helpdesk: > Telephone: 434.984.8426 > sip: [email protected] > <mailto:[email protected]> > Fax: 434.984.8427 > > Helpdesk Contract Customers: > http://www.myitdepartment.net/gethelp/ > > Why do mathematicians always confuse Halloween and Christmas? > Because 31 Oct = 25 Dec. >
_______________________________________________ sipx-users mailing list [email protected] List Archive: http://list.sipfoundry.org/archive/sipx-users/
