If you do a simple search of the attached file looking for "6102" you find it multiple times. And not one time does it have a 1 in front of it. At least not from what I could find. It's pretty basic, if sipXecs was putting that one is for any reason, you would find it in your capture from the logs.
Have you tried a packet capture on your last connection off the network to compare it to this capture. My bet is it looks the same, which would be an indication that the ITSP is inserting the one. -----Original Message----- From: [email protected] [mailto:[email protected]] On Behalf Of Roy Walker Sent: Tuesday, January 04, 2011 5:52 PM To: [email protected] Subject: Re: [sipx-users] Caller-id settings not working I was trying to show the relevant section of the log... I don't see how this COULD POSSIBLY be an issue with the ITSP (in this case Vitelity). I have turned off Caller ID settings on EVERYTHING but the user account. Which is set to 2148916102. I got 16102 on the receiving end... exactly what was sent to the ITSP. Attached is the segment of the sipxbridge.log from the moment before I call to a few seconds after the call is hung up. Roy _______________________________________________ sipx-users mailing list [email protected] List Archive: http://list.sipfoundry.org/archive/sipx-users/
