Jump to content

Friedom-Tech

Members
  • Posts

    282
  • Joined

  • Last visited

Everything posted by Friedom-Tech

  1. I am running Version: 3.4.0.3202 (Win32) and i still have this issue. basically when the client calls in and it authenticates his cell with extension what is happening is it is using the same caller ID that is setup on his extension instead of using the dial plan that the calling card account has set! please advise asap.
  2. Hi, i am trying to setup a new trunk with a new carrier Broadview over a T1 but for some reason they are not accepting the calls i send them, they say the issue is that I am sending the same URI in the from and to header (see trace attached). I have changed changing most of the settings in the trunk itself with no results. please advise asap.
  3. Hi, I have a client with multiple conferences going on every day. Seeing how you can have multiple conferences scheduled for the same time on the same room they would like to be able to view (as admin user) every conference call that has been scheduled by all the users. Please advise asap if this is possible.
  4. Hi, I have a newer version of 4.0 now and it seems to support the image change in the WAC too. Thank you for that. Regarding the question marks I would say for my current purposes removal would be fine however in the future I would like to see an option to possibly redirect them. (I'm sure other resellers would welcome this feature). The important part to me is being able to sell a fully white labeled product without having to worry that there are traces of links/images that will point to pbxnsip. Also the pac for iphone is a beautiful option to offer clients but is there a way for clients to download/add to phone without it being branded by pbxnsip? possibly by adding a white labeled pac to apple store or alternate option to install it from? Please let me know.
  5. Hi, big fan of 4.0 but along with it comes issue...in the past to white label the pbx was simple...unlock appearance tab, change logo etc and your good. now i run into multiple issues. 1) Logo shows up multiplied over the top bar of the pbx screen. 2) The Question Marks on each page are configured to go to support suite. 3) WAC still shows pbxnsip logo? Can we not have one page where we can customize and white label the entire product? Please advise asap, this is holding me up from upgrading my clients.
  6. i downloaded the file: 1) Edited week of EDT start 2) Placed into HTML folder 3) Restarted pbx server. 4) Restarted my polycom 550 and it didnt change anything??
  7. How would i find the XML that is associated with this extension number? it does not show in the generated folder and in the extension folder it just has random numbers. I also failed to let you know that there is no phone registered to this extension...we are using this extension as an night emergency line that asks every caller for their name before passing the call through to the cell of the one oncall.
  8. This is an ongoing problem. do you think if i delete the extension and recreate it, that could help? please advise.
  9. It does reflect the 14th because it shows <dst_start_week_of_month>2</dst_start_week_of_month> which is the second week of the month. where do i find this file and how can i modify it so that i will push out to all phones on reboot?
  10. Hi, i have a bunch of customers using Polycom phones and every time there is a DST change I get complaints for around a week that the time on their phones is wrong because the time is changing based on the old dates for time change. is there any easy way for me to update the DST date changes in all phones without having to manually log in to each and every one? (around 2-300)??? please advise.
  11. Hi, Problem is that in your logfile i dont even see it going out at all? would you like me to test with wireshark running??
  12. Hi, i have system running latest version of 3.4.0.3201 (Win32) and emails alerts work great for all extensions...sending voicemails etc. however i have one extension that is set to send email for every call and for missed call alerts...now this extension DOES send emails for voicemails however does not send for missed calls or call details for every call! this is an extension that it is IMPERATIVE we get the alerts or we have no way of tracking who called that extensions (the only way we know a call went through to that extension is because we are getting end of day emails showing the call) FYI i have set the log to log only email with level 9 and it does not show that it is even trying to send out the message. any help would be appreciated asap.
  13. No this is a real problem i was onsite but the client today and he is terribly upset...i quote "it shows a lack of professionalism on the vendors part when they sell an add on that doesn't work and then give no support for it" i had no response. PLEASE can we get a fix....
  14. Hi, It is not an IP conflict because the voip network is on its own lan with no connections to anything but the phones which pull dhcp from the phone server. I will send you access to the system now.
  15. Hi, there is no interface with two ip addresses...we have two interfaces...one for LAN and one for WAN...everything is static ip... please advise where i can send PM with log info for the system so you can take a look for yourself. also we changed IP config a few weeks back and only began having issues now?? the issue you are seeing with 10.0.3.16 is nothing to worry about because that is just a trunked system in another location that is also down right now...
  16. Hi, I changed log level to 9 Logfile Clear or Reload the log. [6] 2010/01/23 21:05:11: Could not determine destination address on 69980 [6] 2010/01/23 21:05:11: Could not determine destination address on 69978 [6] 2010/01/23 21:05:11: Could not determine destination address on 69975 [6] 2010/01/23 21:05:11: Could not determine destination address on 69972 [6] 2010/01/23 21:05:11: Could not determine destination address on 69970 [6] 2010/01/23 21:05:11: Could not determine destination address on 69967 [6] 2010/01/23 21:05:11: Could not determine destination address on 69960 [6] 2010/01/23 21:05:11: Could not determine destination address on 69957 [6] 2010/01/23 21:05:11: Could not determine destination address on 69954 [6] 2010/01/23 21:05:11: Could not determine destination address on 69951 [6] 2010/01/23 21:05:11: Could not determine destination address on 69949 [6] 2010/01/23 21:05:11: Could not determine destination address on 69946 [6] 2010/01/23 21:05:11: Could not determine destination address on 69944 [6] 2010/01/23 21:05:11: Could not determine destination address on 69943 [6] 2010/01/23 21:05:11: Could not determine destination address on 69941 [6] 2010/01/23 21:05:11: Could not determine destination address on 69939 [6] 2010/01/23 21:05:11: Could not determine destination address on 69937 [6] 2010/01/23 21:05:11: Could not determine destination address on 69935 [6] 2010/01/23 21:05:11: Could not determine destination address on 69933 [6] 2010/01/23 21:05:11: Could not determine destination address on 69929 [6] 2010/01/23 21:05:11: Could not determine destination address on 69927 [6] 2010/01/23 21:05:11: Could not determine destination address on 69924 [6] 2010/01/23 21:05:11: Could not determine destination address on 69922 [6] 2010/01/23 21:05:11: Could not determine destination address on 69921 [6] 2010/01/23 21:05:11: Could not determine destination address on 69919 [6] 2010/01/23 21:05:11: Could not determine destination address on 69917 [6] 2010/01/23 21:05:11: Could not determine destination address on 69915 [6] 2010/01/23 21:05:11: Could not determine destination address on 69912 [6] 2010/01/23 21:05:11: Could not determine destination address on 69910 [6] 2010/01/23 21:05:11: Could not determine destination address on 69908 [6] 2010/01/23 21:05:11: Could not determine destination address on 69905 [6] 2010/01/23 21:05:11: Could not determine destination address on 69903 [6] 2010/01/23 21:05:11: Could not determine destination address on 69900 [6] 2010/01/23 21:05:11: Could not determine destination address on 69898 [6] 2010/01/23 21:05:11: Could not determine destination address on 69897 [6] 2010/01/23 21:05:11: Could not determine destination address on 69894 [6] 2010/01/23 21:05:11: Could not determine destination address on 69892 [6] 2010/01/23 21:05:11: Could not determine destination address on 69890 [6] 2010/01/23 21:05:11: Could not determine destination address on 69887 [6] 2010/01/23 21:05:11: Could not determine destination address on 69884 [6] 2010/01/23 21:05:11: Could not determine destination address on 69882 [6] 2010/01/23 21:05:11: Could not determine destination address on 69880 [6] 2010/01/23 21:05:11: Could not determine destination address on 69878 [6] 2010/01/23 21:05:11: Could not determine destination address on 69876 [6] 2010/01/23 21:05:11: Could not determine destination address on 69874 [6] 2010/01/23 21:05:11: Could not determine destination address on 69871 [6] 2010/01/23 21:05:11: Could not determine destination address on 69869 [6] 2010/01/23 21:05:11: Could not determine destination address on 69867 [6] 2010/01/23 21:05:11: Could not determine destination address on 69865 [6] 2010/01/23 21:05:11: Could not determine destination address on 69861 [6] 2010/01/23 21:05:11: Could not determine destination address on 69859 [6] 2010/01/23 21:05:11: Could not determine destination address on 69857 [6] 2010/01/23 21:05:11: Could not determine destination address on 69855 [6] 2010/01/23 21:05:11: Could not determine destination address on 69854 [6] 2010/01/23 21:05:11: Could not determine destination address on 69852 [6] 2010/01/23 21:05:11: Could not determine destination address on 69850 [6] 2010/01/23 21:05:11: Could not determine destination address on 69848 [6] 2010/01/23 21:05:11: Could not determine destination address on 69846 [6] 2010/01/23 21:05:11: Could not determine destination address on 69843 [6] 2010/01/23 21:05:11: Could not determine destination address on 69841 [6] 2010/01/23 21:05:11: Could not determine destination address on 69839 [6] 2010/01/23 21:05:11: Could not determine destination address on 69836 [6] 2010/01/23 21:05:11: Could not determine destination address on 69834 [6] 2010/01/23 21:05:11: Could not determine destination address on 69832 [6] 2010/01/23 21:05:11: Could not determine destination address on 69830 [6] 2010/01/23 21:05:11: Could not determine destination address on 69828 [6] 2010/01/23 21:05:11: Could not determine destination address on 69827 [6] 2010/01/23 21:05:11: Could not determine destination address on 69824 [6] 2010/01/23 21:05:11: Could not determine destination address on 69823 [6] 2010/01/23 21:05:11: Could not determine destination address on 69822 [6] 2010/01/23 21:05:11: Could not determine destination address on 69820 [6] 2010/01/23 21:05:11: Could not determine destination address on 69819 [6] 2010/01/23 21:05:11: Could not determine destination address on 69818 [6] 2010/01/23 21:05:11: Could not determine destination address on 69817 [6] 2010/01/23 21:05:11: Could not determine destination address on 69816 [6] 2010/01/23 21:05:11: Could not determine destination address on 69815 [6] 2010/01/23 21:05:11: Could not determine destination address on 69814 [6] 2010/01/23 21:05:11: Could not determine destination address on 69813 [6] 2010/01/23 21:05:11: Could not determine destination address on 69812 [6] 2010/01/23 21:05:11: Could not determine destination address on 69811 [6] 2010/01/23 21:05:11: Could not determine destination address on 69810 [6] 2010/01/23 21:05:11: Could not determine destination address on 69809 [6] 2010/01/23 21:05:11: Could not determine destination address on 69806 [6] 2010/01/23 21:05:11: Could not determine destination address on 69804 [6] 2010/01/23 21:05:11: Could not determine destination address on 69803 [6] 2010/01/23 21:05:11: Could not determine destination address on 69802 [6] 2010/01/23 21:05:11: Could not determine destination address on 69800 [6] 2010/01/23 21:05:11: Could not determine destination address on 69799 [6] 2010/01/23 21:05:11: Could not determine destination address on 69798 [6] 2010/01/23 21:05:11: Could not determine destination address on 69797 [6] 2010/01/23 21:05:11: Could not determine destination address on 69795 [6] 2010/01/23 21:05:11: Could not determine destination address on 69793 [6] 2010/01/23 21:05:11: Could not determine destination address on 69792 [6] 2010/01/23 21:05:11: Could not determine destination address on 69791 [6] 2010/01/23 21:05:11: Could not determine destination address on 69789 [6] 2010/01/23 21:05:11: Could not determine destination address on 69788 [6] 2010/01/23 21:05:11: Could not determine destination address on 69786 [6] 2010/01/23 21:05:11: Could not determine destination address on 69782 [9] 2010/01/23 21:05:11: Resolve 70177: url sip:10.0.3.16 [9] 2010/01/23 21:05:11: Resolve 70177: udp 10.0.3.16 5060 problem is that there is too much in file...let me know if i should write the file to text. FYI it seems to be intermittent...it goes up and down at will...i can call in and get auto attendant and then 15 seconds later call and be unable to get through!
  17. FYI my logfile is full of these [6] 2010/01/23 20:35:51: Could not determine destination address on 40624 [6] 2010/01/23 20:35:51: Could not determine destination address on 40622 [6] 2010/01/23 20:35:51: Could not determine destination address on 40620 [6] 2010/01/23 20:35:51: Could not determine destination address on 40619 [6] 2010/01/23 20:35:51: Could not determine destination address on 40618 [6] 2010/01/23 20:35:51: Could not determine destination address on 40617 [6] 2010/01/23 20:35:51: Could not determine destination address on 40615 [5] 2010/01/23 20:35:52: Connection refused on udp:10.0.3.16:5060 [6] 2010/01/23 20:35:52: Could not determine destination address on 40681 [6] 2010/01/23 20:35:52: Could not determine destination address on 40679 [6] 2010/01/23 20:35:52: Could not determine destination address on 40677 [6] 2010/01/23 20:35:52: Could not determine destination address on 40676 [6] 2010/01/23 20:35:52: Could not determine destination address on 40675 [6] 2010/01/23 20:35:52: Could not determine destination address on 40672 [6] 2010/01/23 20:35:52: Could not determine destination address on 40671 [6] 2010/01/23 20:35:52: Could not determine destination address on 40670 [6] 2010/01/23 20:35:52: Could not determine destination address on 40669 [6] 2010/01/23 20:35:52: Could not determine destination address on 40668 [6] 2010/01/23 20:35:52: Could not determine destination address on 40667 [6] 2010/01/23 20:35:52: Could not determine destination address on 40666 [6] 2010/01/23 20:35:52: Could not determine destination address on 40665 [6] 2010/01/23 20:35:52: Could not determine destination address on 40664 [6] 2010/01/23 20:35:52: Could not determine destination address on 40663 [6] 2010/01/23 20:35:52: Could not determine destination address on 40662 [6] 2010/01/23 20:35:52: Could not determine destination address on 40660 [6] 2010/01/23 20:35:52: Could not determine destination address on 40659 [6] 2010/01/23 20:35:52: Could not determine destination address on 40657 [6] 2010/01/23 20:35:52: Could not determine destination address on 40656 [6] 2010/01/23 20:35:52: Could not determine destination address on 40654 [6] 2010/01/23 20:35:52: Could not determine destination address on 40653 [6] 2010/01/23 20:35:52: Could not determine destination address on 40652 [6] 2010/01/23 20:35:52: Could not determine destination address on 40650 [6] 2010/01/23 20:35:52: Could not determine destination address on 40648 [6] 2010/01/23 20:35:52: Could not determine destination address on 40646 [6] 2010/01/23 20:35:52: Could not determine destination address on 40644 [6] 2010/01/23 20:35:52: Could not determine destination address on 40643 [6] 2010/01/23 20:35:52: Could not determine destination address on 40642 [6] 2010/01/23 20:35:52: Could not determine destination address on 40640 [6] 2010/01/23 20:35:52: Could not determine destination address on 40638 [6] 2010/01/23 20:35:52: Could not determine destination address on 40636 [6] 2010/01/23 20:35:52: Could not determine destination address on 40634 [6] 2010/01/23 20:35:52: Could not determine destination address on 40633 [6] 2010/01/23 20:35:52: Could not determine destination address on 40632 [6] 2010/01/23 20:35:52: Could not determine destination address on 40630 [6] 2010/01/23 20:35:52: Could not determine destination address on 40627 [6] 2010/01/23 20:35:52: Could not determine destination address on 40625 [6] 2010/01/23 20:35:52: Could not determine destination address on 40624 [6] 2010/01/23 20:35:52: Could not determine destination address on 40622 [6] 2010/01/23 20:35:52: Could not determine destination address on 40620 [6] 2010/01/23 20:35:52: Could not determine destination address on 40619 [6] 2010/01/23 20:35:52: Could not determine destination address on 40618 [6] 2010/01/23 20:35:52: Could not determine destination address on 40617 [6] 2010/01/23 20:35:52: Could not determine destination address on 40615 [5] 2010/01/23 20:35:52: Connection refused on udp:10.0.3.16:5060 [6] 2010/01/23 20:35:52: Could not determine destination address on 40684 [6] 2010/01/23 20:35:52: Could not determine destination address on 40681 [6] 2010/01/23 20:35:52: Could not determine destination address on 40679 [6] 2010/01/23 20:35:52: Could not determine destination address on 40677 [6] 2010/01/23 20:35:52: Could not determine destination address on 40676 [6] 2010/01/23 20:35:52: Could not determine destination address on 40675 [6] 2010/01/23 20:35:52: Could not determine destination address on 40672 [6] 2010/01/23 20:35:52: Could not determine destination address on 40671 [6] 2010/01/23 20:35:52: Could not determine destination address on 40670 [6] 2010/01/23 20:35:52: Could not determine destination address on 40669 [6] 2010/01/23 20:35:52: Could not determine destination address on 40668 [6] 2010/01/23 20:35:52: Could not determine destination address on 40667 [6] 2010/01/23 20:35:52: Could not determine destination address on 40666 [6] 2010/01/23 20:35:52: Could not determine destination address on 40665 [6] 2010/01/23 20:35:52: Could not determine destination address on 40664 [6] 2010/01/23 20:35:52: Could not determine destination address on 40663 [6] 2010/01/23 20:35:52: Could not determine destination address on 40662 [6] 2010/01/23 20:35:52: Could not determine destination address on 40660 [6] 2010/01/23 20:35:52: Could not determine destination address on 40659 [6] 2010/01/23 20:35:52: Could not determine destination address on 40657 [6] 2010/01/23 20:35:52: Could not determine destination address on 40656 [6] 2010/01/23 20:35:52: Could not determine destination address on 40654 [6] 2010/01/23 20:35:52: Could not determine destination address on 40653 [6] 2010/01/23 20:35:52: Could not determine destination address on 40652 [6] 2010/01/23 20:35:52: Could not determine destination address on 40650 [6] 2010/01/23 20:35:52: Could not determine destination address on 40648 [6] 2010/01/23 20:35:52: Could not determine destination address on 40646 [6] 2010/01/23 20:35:52: Could not determine destination address on 40644 [6] 2010/01/23 20:35:52: Could not determine destination address on 40643 [6] 2010/01/23 20:35:52: Could not determine destination address on 40642 [6] 2010/01/23 20:35:52: Could not determine destination address on 40640 [6] 2010/01/23 20:35:52: Could not determine destination address on 40638 [6] 2010/01/23 20:35:52: Could not determine destination address on 40636 [6] 2010/01/23 20:35:52: Could not determine destination address on 40634 [6] 2010/01/23 20:35:52: Could not determine destination address on 40633 [6] 2010/01/23 20:35:52: Could not determine destination address on 40632 [6] 2010/01/23 20:35:52: Could not determine destination address on 40630 [6] 2010/01/23 20:35:52: Could not determine destination address on 40627 [6] 2010/01/23 20:35:52: Could not determine destination address on 40625 [6] 2010/01/23 20:35:52: Could not determine destination address on 40624 [6] 2010/01/23 20:35:52: Could not determine destination address on 40622 [6] 2010/01/23 20:35:52: Could not determine destination address on 40620 [6] 2010/01/23 20:35:52: Could not determine destination address on 40619 [6] 2010/01/23 20:35:52: Could not determine destination address on 40618 [6] 2010/01/23 20:35:52: Could not determine destination address on 40617 [6] 2010/01/23 20:35:52: Could not determine destination address on 40615
  18. Hi, I am having a weird issue. My system shows as online with all working correctly but i cannot make or receive any calls...when i call in i see the call hitting the system but i get "you are calling a non working number" If i reboot the service all works fine but then after a few minutes its goes down again... I have two trunks...an onnet with the ISP and a Callcentric and neither are working (the callcentric trunk shows as registered but still does not accept calls) please can someone help me with this asap.
  19. Hi, i have the following scenario where recordings were missing. version 3.4.3201 1) Call comes in and there is no record of the call (incidentally the user TRIED to transfer to someone else but person did not pick up) 2) Call comes in to extension 6003 the user transfers the call to extension 6025...the only recording we can find is 6003 calling 6025 to let him know he has mr smith on the line but once he transfers the call through to 6025 the recording stops....i have ALL CALLS set to record...why is it not recording/
  20. Hi, i have the following scenario where recordings were missing. version 3.4.3201 1) Call comes in and there is no record of the call (incidentally the user TRIED to transfer to someone else but person did not pick up) 2) Call comes in to extension 6003 the user transfers the call to extension 6025...the only recording we can find is 6003 calling 6025 to let him know he has mr smith on the line but once he transfers the call through to 6025 the recording stops....i have ALL CALLS set to record...why is it not recording/
  21. there is a lot of traffic back and forth so difficult to discern that...also this is an intermittent issue...not happening every time on every phone...
×
×
  • Create New...