-
Posts
452 -
Joined
-
Last visited
Content Type
Profiles
Forums
Events
Posts posted by shopcomputer
-
-
I have never been able to make a snom 360 or 320 work on any cisco switch running spanning tree, and PoE
We primarily use HP switches, however I definetly have some Cisco switches out there, and never had to change any settings.
You may have an old Cisco switch, that is older than the current poe standards.
-
Definetly not a user name and password issue, as my web browser accepts that same login, it has the full username@domain, the Snom 820 accepted the same password too. I beleive I would get a 400 response not a 500 for a bad password.
Did anyone successfully autoprovision a Snom 870? which firmware version?
-
Ok. definitely this is a user name password issue. Try using username@domain if it is multi-domain system.
Definetly not a user name and password issue, as my web browser accepts that same login, it has the full username@domain, the Snom 820 accepted the same password too. I beleive I would get a 400 response not a 500 for a bad password.
-
FYI.. After copying the pnp.xml to html folder, you need to restart PBX service or this file needs to be uploaded through Admin->Settings->Configuration page.
Also, the log line "[0]24/12/2001 00:00:52: Webclient: Could not resolve host during provisioning srv.server.com:80", is a suspect.
Sorry, I forgot about that, I reloaded the pnp.xml, I get further however it seems to be getting an error 500, and it tries to re log in, from my desktop, the url's pull up fine, using same user name and password set in the client setting of the phone.
here is the snom 870 log
5]24/12/2001 00:00:27: Using GUI language English from: /snom/snomlang/gui_lang_EN.xml
[5]24/12/2001 00:00:32: Using WEB language English from: /snom/snomlang/web_lang_EN.xml
[5]24/12/2001 00:00:32: read_xml_settings: found dial-plan XML header
[5]24/12/2001 00:00:32: read_xml_settings: found one byte encoding: 0
[0]24/12/2001 00:00:41: phone::vlan_onoff: cannot open switch-api
[0]24/12/2001 00:00:41: phone::vlan_table_reset: cannot open switch-api
[5]24/12/2001 00:00:41: Opening TCP socket on port 843
[5]24/12/2001 00:00:46: Setting server was already set: http://server.server.com/provisioning/snom870.htm
[5]24/12/2001 00:00:46: Fetching URL: http://server.server.com/provisioning/snom870.htm
[5]24/12/2001 00:00:55: webclient::handle_challenge: http server is asking for credentials!
[5]24/12/2001 00:00:55: webclient::handle_challenge: resending request !
[5]24/12/2001 00:00:59: read_xml_settings: found setting-files XML header
[5]24/12/2001 00:00:59: read_xml_settings: found one byte encoding: 1
[5]24/12/2001 00:00:59: read_setting_file_list: added URL: http://55.77.142.3:80/provisioning/snom_3x...l?model=snom870
[5]24/12/2001 00:00:59: read_setting_file_list: added URL: https://55.77.142.3:443/provisioning/snom_3...l?model=snom870
[5]24/12/2001 00:00:59: read_setting_file_list: added URL: https://55.77.142.3:443/provisioning/snom_3...l?model=snom870
[5]24/12/2001 00:00:59: read_setting_file_list: added URL: https://55.77.142.3:443/provisioning/snom_3...l?model=snom870
[5]24/12/2001 00:00:59: read_setting_file_list: added URL: https://55.77.142.3:443/provisioning/snom_w...l?model=snom870
[5]24/12/2001 00:00:59: read_setting_file_list: added URL: https://55.77.142.3:443/provisioning/snom_g...l?model=snom870
[5]24/12/2001 00:00:59: read_setting_file_list: added URL: https://55.77.142.3:443/tftp/snom_870_custom.xml
[5]24/12/2001 00:00:59: Conf setup: found xml style settings
[5]24/12/2001 00:00:59: Fetching URL: http://server.server.com/provisioning/snom...00414410B3B.htm
[1]24/12/2001 00:00:59: Conf setup: code: 404, host: server.server.com:80, file: /provisioning/snom870-000414410B3B.htm
[5]24/12/2001 00:00:59: Fetching URL: http://55.77.142.3:80/provisioning/snom_3x...l?model=snom870
[5]24/12/2001 00:01:07: webclient::handle_challenge: http server is asking for credentials!
[5]24/12/2001 00:01:07: webclient::handle_challenge: resending request !
[5]24/12/2001 00:01:10: read_xml_settings: found phone-settings XML header
[5]24/12/2001 00:01:10: read_xml_settings: found one byte encoding: 1
[5]24/12/2001 00:01:10: Conf setup: found xml style settings
[5]24/12/2001 00:01:10: Fetching URL: https://55.77.142.3:443/provisioning/snom_3...l?model=snom870
[5]24/12/2001 00:01:19: webclient::handle_challenge: http server is asking for credentials!
[5]24/12/2001 00:01:19: webclient::handle_challenge: resending request !
[5]24/12/2001 00:01:49: Conf setup: return code 500; requeueing >https://55.77.142.3:443/provisioning/snom_3xx_phone.xml?model=snom870<;'>https://55.77.142.3:443/provisioning/snom_3xx_phone.xml?model=snom870<; attempt: 1, state: 38
[5]24/12/2001 00:01:52: Fetching URL: https://55.77.142.3:443/provisioning/snom_3...l?model=snom870
[5]24/12/2001 00:02:00: webclient::handle_challenge: http server is asking for credentials!
[5]24/12/2001 00:02:00: webclient::handle_challenge: resending request !
[5]24/12/2001 00:02:30: Conf setup: return code 500; requeueing >https://55.77.142.3:443/provisioning/snom_3xx_phone.xml?model=snom870<;'>https://55.77.142.3:443/provisioning/snom_3xx_phone.xml?model=snom870<; attempt: 2, state: 38
[5]24/12/2001 00:02:33: Fetching URL: https://55.77.142.3:443/provisioning/snom_3...l?model=snom870
[5]24/12/2001 00:02:42: webclient::handle_challenge: http server is asking for credentials!
[5]24/12/2001 00:02:42: webclient::handle_challenge: resending request !
[5]24/12/2001 00:03:12: Conf setup: return code 500; requeueing >https://55.77.142.3:443/provisioning/snom_3xx_phone.xml?model=snom870<;'>https://55.77.142.3:443/provisioning/snom_3xx_phone.xml?model=snom870<; attempt: 3, state: 38
[5]24/12/2001 00:03:15: Fetching URL: https://55.77.142.3:443/provisioning/snom_3...l?model=snom870
[5]24/12/2001 00:03:23: webclient::handle_challenge: http server is asking for credentials!
[5]24/12/2001 00:03:23: webclient::handle_challenge: resending request !
[5]24/12/2001 00:03:54: Conf setup: return code 500; requeueing >https://55.77.142.3:443/provisioning/snom_3xx_phone.xml?model=snom870<;'>https://55.77.142.3:443/provisioning/snom_3xx_phone.xml?model=snom870<; attempt: 4, state: 38
[5]24/12/2001 00:03:57: Fetching URL: https://55.77.142.3:443/provisioning/snom_3...l?model=snom870
[5]24/12/2001 00:04:05: webclient::handle_challenge: http server is asking for credentials!
[5]24/12/2001 00:04:05: webclient::handle_challenge: resending request !
[5]24/12/2001 00:04:35: Conf setup: return code 500; requeueing >https://55.77.142.3:443/provisioning/snom_3xx_phone.xml?model=snom870<;'>https://55.77.142.3:443/provisioning/snom_3xx_phone.xml?model=snom870<; attempt: 5, state: 38
[5]24/12/2001 00:04:38: Fetching URL: https://55.77.142.3:443/provisioning/snom_3...l?model=snom870
[5]24/12/2001 00:04:47: webclient::handle_challenge: http server is asking for credentials!
[5]24/12/2001 00:04:47: webclient::handle_challenge: resending request !
[5]24/12/2001 00:05:17: Conf setup: return code 500; requeueing >https://55.77.142.3:443/provisioning/snom_3xx_phone.xml?model=snom870<;'>https://55.77.142.3:443/provisioning/snom_3xx_phone.xml?model=snom870<; attempt: 6, state: 38
[5]24/12/2001 00:05:20: Fetching URL: https://55.77.142.3:443/provisioning/snom_3...l?model=snom870
[5]24/12/2001 00:05:28: webclient::handle_challenge: http server is asking for credentials!
[5]24/12/2001 00:05:28: webclient::handle_challenge: resending request !
[5]24/12/2001 00:05:58: Conf setup: return code 500; requeueing >https://55.77.142.3:443/provisioning/snom_3xx_phone.xml?model=snom870<;'>https://55.77.142.3:443/provisioning/snom_3xx_phone.xml?model=snom870<; attempt: 7, state: 38
[5]24/12/2001 00:06:01: Fetching URL: https://55.77.142.3:443/provisioning/snom_3...l?model=snom870
[5]24/12/2001 00:06:10: webclient::handle_challenge: http server is asking for credentials!
[5]24/12/2001 00:06:10: webclient::handle_challenge: resending request !
[5]24/12/2001 00:06:40: Conf setup: return code 500; requeueing >https://55.77.142.3:443/provisioning/snom_3xx_phone.xml?model=snom870<;'>https://55.77.142.3:443/provisioning/snom_3xx_phone.xml?model=snom870<; attempt: 8, state: 38
[5]24/12/2001 00:06:43: Fetching URL: https://55.77.142.3:443/provisioning/snom_3...l?model=snom870
[5]24/12/2001 00:06:51: webclient::handle_challenge: http server is asking for credentials!
[5]24/12/2001 00:06:51: webclient::handle_challenge: resending request !
[5]24/12/2001 00:07:22: Conf setup: return code 500; requeueing >https://55.77.142.3:443/provisioning/snom_3xx_phone.xml?model=snom870<;'>https://55.77.142.3:443/provisioning/snom_3xx_phone.xml?model=snom870<; attempt: 9, state: 38
[5]24/12/2001 00:07:25: Fetching URL: https://55.77.142.3:443/provisioning/snom_3...l?model=snom870
[5]24/12/2001 00:07:33: webclient::handle_challenge: http server is asking for credentials!
[5]24/12/2001 00:07:33: webclient::handle_challenge: resending request !
[5]24/12/2001 00:08:03: Conf setup: return code 500; requeueing >https://55.77.142.3:443/provisioning/snom_3xx_phone.xml?model=snom870<;'>https://55.77.142.3:443/provisioning/snom_3xx_phone.xml?model=snom870<; attempt: 10, state: 38
[5]24/12/2001 00:08:06: Fetching URL: https://55.77.142.3:443/provisioning/snom_3...l?model=snom870
[5]24/12/2001 00:08:15: webclient::handle_challenge: http server is asking for credentials!
[5]24/12/2001 00:08:15: webclient::handle_challenge: resending request !
[5]24/12/2001 00:08:45: Conf setup: return code 500; requeueing >https://55.77.142.3:443/provisioning/snom_3xx_phone.xml?model=snom870<;'>https://55.77.142.3:443/provisioning/snom_3xx_phone.xml?model=snom870<; attempt: 11, state: 38
[5]24/12/2001 00:08:48: Fetching URL: https://55.77.142.3:443/provisioning/snom_3...l?model=snom870
[5]24/12/2001 00:09:18: Conf setup: return code 500; requeueing >https://55.77.142.3:443/provisioning/snom_3xx_phone.xml?model=snom870<;'>https://55.77.142.3:443/provisioning/snom_3xx_phone.xml?model=snom870<; attempt: 12, state: 38
[5]24/12/2001 00:09:21: Fetching URL: https://55.77.142.3:443/provisioning/snom_3...l?model=snom870
[5]24/12/2001 00:09:52: Conf setup: return code 500; requeueing >https://55.77.142.3:443/provisioning/snom_3xx_phone.xml?model=snom870<;'>https://55.77.142.3:443/provisioning/snom_3xx_phone.xml?model=snom870<; attempt: 13, state: 38
[5]24/12/2001 00:09:55: Fetching URL: https://55.77.142.3:443/provisioning/snom_3...l?model=snom870
[5]24/12/2001 00:10:03: webclient::handle_challenge: http server is asking for credentials!
[5]24/12/2001 00:10:03: webclient::handle_challenge: resending request !
[5]24/12/2001 00:10:33: Conf setup: return code 500; requeueing >https://55.77.142.3:443/provisioning/snom_3xx_phone.xml?model=snom870<;'>https://55.77.142.3:443/provisioning/snom_3xx_phone.xml?model=snom870<; attempt: 14, state: 38
[5]24/12/2001 00:10:36: Fetching URL: https://55.77.142.3:443/provisioning/snom_3...l?model=snom870
[5]24/12/2001 00:10:45: webclient::handle_challenge: http server is asking for credentials!
[5]24/12/2001 00:10:45: webclient::handle_challenge: resending request !
[5]24/12/2001 00:11:15: Conf setup: return code 500; requeueing >https://55.77.142.3:443/provisioning/snom_3xx_phone.xml?model=snom870<;'>https://55.77.142.3:443/provisioning/snom_3xx_phone.xml?model=snom870<; attempt: 15, state: 38
[5]24/12/2001 00:11:18: Fetching URL: https://55.77.142.3:443/provisioning/snom_3...l?model=snom870
[5]24/12/2001 00:11:26: webclient::handle_challenge: http server is asking for credentials!
[5]24/12/2001 00:11:26: webclient::handle_challenge: resending request !
[5]24/12/2001 00:11:56: Conf setup: return code 500; requeueing >https://55.77.142.3:443/provisioning/snom_3xx_phone.xml?model=snom870<;'>https://55.77.142.3:443/provisioning/snom_3xx_phone.xml?model=snom870<; attempt: 16, state: 38
[5]24/12/2001 00:11:59: Fetching URL: https://55.77.142.3:443/provisioning/snom_3...l?model=snom870
[5]24/12/2001 00:12:08: webclient::handle_challenge: http server is asking for credentials!
[5]24/12/2001 00:12:08: webclient::handle_challenge: resending request !
[5]24/12/2001 00:12:38: Conf setup: return code 500; requeueing >https://55.77.142.3:443/provisioning/snom_3xx_phone.xml?model=snom870<;'>https://55.77.142.3:443/provisioning/snom_3xx_phone.xml?model=snom870<; attempt: 17, state: 38
[5]24/12/2001 00:12:41: Fetching URL: https://55.77.142.3:443/provisioning/snom_3...l?model=snom870
[5]24/12/2001 00:12:49: webclient::handle_challenge: http server is asking for credentials!
[5]24/12/2001 00:12:49: webclient::handle_challenge: resending request !
[5]24/12/2001 00:13:19: Conf setup: return code 500; requeueing >https://55.77.142.3:443/provisioning/snom_3xx_phone.xml?model=snom870<;'>https://55.77.142.3:443/provisioning/snom_3xx_phone.xml?model=snom870<; attempt: 18, state: 38
[5]24/12/2001 00:13:22: Fetching URL: https://55.77.142.3:443/provisioning/snom_3...l?model=snom870
[5]24/12/2001 00:13:31: webclient::handle_challenge: http server is asking for credentials!
[5]24/12/2001 00:13:31: webclient::handle_challenge: resending request !
[5]24/12/2001 00:14:01: Conf setup: return code 500; requeueing >https://55.77.142.3:443/provisioning/snom_3xx_phone.xml?model=snom870<;'>https://55.77.142.3:443/provisioning/snom_3xx_phone.xml?model=snom870<; attempt: 19, state: 38
[5]24/12/2001 00:14:04: Fetching URL: https://55.77.142.3:443/provisioning/snom_3...l?model=snom870
[5]24/12/2001 00:14:12: webclient::handle_challenge: http server is asking for credentials!
[5]24/12/2001 00:14:12: webclient::handle_challenge: resending request !
[5]24/12/2001 00:14:43: Conf setup: return code 500; requeueing >https://55.77.142.3:443/provisioning/snom_3xx_phone.xml?model=snom870<;'>https://55.77.142.3:443/provisioning/snom_3xx_phone.xml?model=snom870<; attempt: 20, state: 38
[5]24/12/2001 00:14:46: Fetching URL: https://55.77.142.3:443/provisioning/snom_3...l?model=snom870
[5]24/12/2001 00:14:54: webclient::handle_challenge: http server is asking for credentials!
[5]24/12/2001 00:14:54: webclient::handle_challenge: resending request !
[5]24/12/2001 00:15:24: Conf setup: return code 500; giving up on >https://55.77.142.3:443/provisioning/snom_3xx_phone.xml?model=snom870<
[5]24/12/2001 00:15:24: read_xml_settings: found phone-book XML header
[5]24/12/2001 00:15:24: read_xml_settings: found one byte encoding: 0
[5]24/12/2001 00:15:27: Using GUI language English from: /snom/snomlang/gui_lang_EN.xml
[5]24/12/2001 00:15:32: Using WEB language English from: /snom/snomlang/web_lang_EN.xml
[5]24/12/2001 00:15:32: Opening TCP socket on port 80
[5]24/12/2001 00:15:32: Opening TCP socket on port 443
-
It should work. Just make sure that you need to remove these files when you upgrade the version to something that includes the PnP files for snom 870. (All version older than today do support this).
Does not work for me, I do have snom_3xx_fs and snom_3xx_fw in the genrated/extension folder, my 820 phones have 8 files in their extension folder.
I get a 404 if I try browsing to http://srv.server.com/provisioning/snom870.htm where as if I try http://srv.server.com/provisioning/snom820.htm I get logon and see the xml
snom log
5]24/12/2001 00:00:31: Using GUI language English from: /snom/snomlang/gui_lang_EN.xml
[5]24/12/2001 00:00:36: Using WEB language English from: /snom/snomlang/web_lang_EN.xml
[5]24/12/2001 00:00:36: read_xml_settings: found dial-plan XML header
[5]24/12/2001 00:00:36: read_xml_settings: found one byte encoding: 0
[0]24/12/2001 00:00:46: phone::vlan_onoff: cannot open switch-api
[0]24/12/2001 00:00:46: phone::vlan_table_reset: cannot open switch-api
[5]24/12/2001 00:00:46: Opening TCP socket on port 843
[5]24/12/2001 00:00:51: Setting server was already set: http://srv.server.com/provisioning/snom870.htm
[5]24/12/2001 00:00:51: Fetching URL: http://srv.server.com/provisioning/snom870.htm
[0]24/12/2001 00:00:52: Webclient: Could not resolve host during provisioning srv.server.com:80
[5]24/12/2001 00:00:52: Conf setup: return code 400; requeueing >http://srv.server.com:80/provisioning/snom870.htm<; attempt: 1, state: 38
[5]24/12/2001 00:00:55: Fetching URL: http://srv.server.com:80/provisioning/snom870.htm
[1]24/12/2001 00:00:55: Conf setup: code: 404, host: srv.server.com:80, file: /provisioning/snom870.htm
[5]24/12/2001 00:00:55: Fetching URL: http://srv.server.com/provisioning/snom870-000414410B3B.htm
[1]24/12/2001 00:00:55: Conf setup: code: 404, host: srv.server.com:80, file: /provisioning/snom870-000413410B3B.htm
[5]24/12/2001 00:00:55: Fetching URL: http://127.0.0.1/dummy.htm
[1]24/12/2001 00:00:55: Conf setup: code: 500, host: 127.0.0.1:80, file: /dummy.htm
[5]24/12/2001 00:00:55: Fetching FW URL: http://srv.server.com/snom870/snom870-firmware.htm
[5]24/12/2001 00:00:55: Fetching URL: http://srv.server.com/snom870/snom870-firmware.htm
[2]23/12/2001 19:00:55: start_dst(984276000) end_dst(1004839200) offset_dst(3600) offset_utc(-18000)
[2]23/12/2001 19:00:55: start DST: 03/11/2001 02:00:00 (984276000)
[2]23/12/2001 19:00:55: end DST: 11/04/2001 02:00:00 (1004839200)
[5]23/12/2001 19:00:55: read_xml_settings: found phone-book XML header
[5]23/12/2001 19:00:55: read_xml_settings: found one byte encoding: 0
[5]23/12/2001 19:00:58: Using GUI language English from: /snom/snomlang/gui_lang_EN.xml
[5]23/12/2001 19:01:03: Using WEB language English from: /snom/snomlang/web_lang_EN.xml
[5]23/12/2001 19:01:03: Opening TCP socket on port 80
[5]23/12/2001 19:01:03: Opening TCP socket on port 443
[2]3/12/2009 19:32:32: start_dst(1236477600) end_dst(1257040800) offset_dst(3600) offset_utc(-18000)
[2]3/12/2009 19:32:32: start DST: 03/08/2009 02:00:00 (1236477600)
[2]3/12/2009 19:32:32: end DST: 11/01/2009 02:00:00 (1257040800)
-
How can I agree more... I think you need to open a trouble ticket on snom and report the current clock as "buggy".
I think it is doable, although I can't find the setting at the moment, I do remember seeing it in digital format, maybe it was only in version 6.
I am sure you can find a youtube video of how to do it.
-
We will come out with a version 3.5. I think there we can include the 870 config file. I attach the files that you can throw into the html directory. Don't forget to remove them when you upgrade later.
I am running 4.0.0.3217 (Win32) can use the same files for the Snom 870?
-
What you can do is create and address book entry and set the telephone number to the park code. Kind of workabound...
Can I have it monitor the park orbit extension, and somehow indicate a blf, when park orbit is in use?
-
I have a client with many Snom 360 phones, running PBXnSIP for several years.
They are set to use extension 60, 61, 62 and 63 for call parking
I have 4 park orbit buttons setup in the PBX for them, work great.
One user just got a Polycom IP 550, is there any way I can manually create a button on the phone as a park buttons, to use those extensions for parking and pickup?
Anybody there?
-
ageet--i had the problem the audio didn't come out the correct speaker...
(could be my hardwarE)
matt
I guess it depends on the hardware, it was the only one I was able to get working properly on the non toch screen windows mobile devices, such as my moto q.
-
Moishe,
Thanks, I did use the MC50 as a softphone using SJLab sip softphone. The mc50 worked nice in my recollection and sjlab wm softphone (while not glitzy) did work nice too. But if mc50 has a softphone they wrote i would REALLY like to know about it. I wasn't sure that a warehouse person would want to be tapping a screen for a phone though....just my thot...;-)
I did a video review of mc50 and sjlab phone (but youtube doesn't seem to be working today for it:)
matt
CA50 and MC50 are not the same model.
The buttons don't work with the softphone?
BTW how do you like that softphone? I have been using http://www.ageet.com/us/products-agephone-mobile.htm
-
Hey, I have a motorola mc70 sitting on my desk. (data collector). That doesn't come with a sip phone does it?
does the mc75?
thanks for all the good input.
matt
As far as I remember from training there are 2 versions one sip and the other h.323. Unless I am confusing with the CA50, as I do see that with a sip and h.323 version, all that says on the mc 70 datasheet is VOIP ready.
-
moishe,
Do you have a rugged wifi phone you like?
tx
matt
If you are looking for real rugged warehouse class device go with Motorola MC70 or MC75.
Alot of warehouse guys like engenius phones, I have not been able to get the SIP version, so I sometimes use fxs gateways for them.
You can also look at at Unidata and Polycom specralink, although not fully rugged, they are not cheap quality.
-
i actually saw the M9 and it is much better then the M3, but i still don't feel its for a warehouse environment
I warehouse enviroment we usually end up using Wifi cordless, they usually have a wifi inrastructure, and there are more handset options available.
-
I have a client with many Snom 360 phones, running PBXnSIP for several years.
They are set to use extension 60, 61, 62 and 63 for call parking
I have 4 park orbit buttons setup in the PBX for them, work great.
One user just got a Polycom IP 550, is there any way I can manually create a button on the phone as a park buttons, to use those extensions for parking and pickup?
-
Well I WAS getting error 408, timeout when I would have the outbound proxy set to proxy.nyc.broadvoice.com, and if I would change the outbound proxy to the other recommendation of proxy-nyc, I would get error 500, address issues, but now since I came into work this morning, My trunk doesn't give me an error message, it says: 200 OK (refresh interval 15 seconds), which that is completely new. So I am attempting to register it, and if it does indeed register, I will post what settings worked here for me. It is weird though because I really haven't changed anything, it just all of a sudden decides it wants to work...
200 OK means it successfully registered.
-
Thanks for the info. We do have the sip password, which we have correctly entered, and as for BYOD, I asked Broadvoice what that was, and they said it was just info. on the account, so I assume our account must be set for BYOD. It still is not registering... Broadvoice is no help either... they basically tell me since we are using a device that does not have a configuration with them, there is nothing they can tell us... I don't know what else to do. I do appreciate your help!
What is the PBX logs showing?
-
Greetings to whomever might be able to help,
We just bought Broadvoice, and are trying to connect it to our PBXNSIP system, however, we keep getting the error message: 408 Request Timeout (Registration failed, retry after 60 seconds)
Our account number is our phone number I believe...
The outbound pox that we are using was recommended on this board earlier:
proxy.nyc.broadvoice.com:5060
Is the domain listed in registering this as a trunk supposed to be the sip.broadvoice.com that they recommend when purchasing their stuff...
Also, we said yes to avoid RFC4122 (UUID), so I know it isn't that....
If anyone has struggled with this and found the answer, please let us know. I would appreciate it. Thanks!!
--Jeff
We tried Broadvoice a while back, it did register, make sure your account is set for BYOD, and you get a sip password from them.
-
115
you are very low on the amount of rtp ports, at a minimum you need 2 per call and 1 per phone, increase your rtp ports to at least 1000. there is no benefit of limiting it, why not leave the default range.
-
Hello,
I have a customer who wants to see the caller id caller_name AND the caller_number.
We use snom 360 phones and I can't see a very reasonable way to even get it! ;-)
(they need to write it down to get it to someone else...no computers are invovled)
#1-i can't seem to see a way to get it when on the call...
#2-after the call it is quite a few keystrokes...press the snom "calls" button > select "recieved calls" > press "check" > press "more info" button > press "number" and now the number is encoded in "sip:blah blalh" so you need to scroll (laboriorsly) back and forth! ;-)
Am I really missing something simple?
i'm sure i must be...
THANKS!
matt
Log in to the phone, prefrences, the 3rd option, number display style.
I will email you a screenshot.
-
yes , i also tried SIP without TLS. According the SIP log from the iSoftPhone Authentication is required.
Message sent: (to dest=15.137.40.40:5060)
REGISTER sip:15.137.40.40 SIP/2.0
Via: SIP/2.0/UDP 15.137.40.20:5060;rport;branch=z9hG4bK2121148679
From: <sip:55@15.137.40.40>;tag=1980515830
To: <sip:55@15.137.40.40>
Call-ID: 2048568031
CSeq: 1 REGISTER
Contact: <sip:55@15.137.40.20:5060;line=6ea58eb8426814e>
Max-Forwards: 70
User-Agent: iSoftPhone 2.6060
Expires: 1800
Supported: 100rel
Supported: path
Content-Length: 0
Received message:
SIP/2.0 401 Authentication Required
Via: SIP/2.0/UDP 15.137.40.20:5060;rport=5060;branch=z9hG4bK2121148679
From: <sip:55@15.137.40.40>;tag=1980515830
To: <sip:55@15.137.40.40>;tag=9115ce87a5
Call-ID: 2048568031
CSeq: 1 REGISTER
User-Agent: pbxnsip-PBX/3.4.0.3201
WWW-Authenticate: Digest realm="15.137.40.40",nonce="032e18d1169b67c4854bf26aefcf1714",domain="sip:15.137.40.40",algorithm=MD5
Content-Length: 0
The log is showing, you are using a wrong domain name.
-
Hi
changing the port number to 5060 did not work.
Did you change the protocol from tls to udp?
-
i changed the configuration as you described, however the iSoftPhone is not possible to register. After i checked the SIP log from the iSoftPhone it seems that it is a problm with the certificate. See following log information:
eXosip: Couldn't read CA list
New binding with 15.137.40.40
eXosip: Couldn't read CA list
Failed to verify remote certificate
Message sent:
REGISTER sip:15.137.40.40 SIP/2.0
Via: SIP/2.0/TLS 15.137.40.20:5061;rport;branch=z9hG4bK1009892605
From: <sip:55@15.137.40.40>;tag=1555775356
To: <sip:55@15.137.40.40>
Call-ID: 575753453
CSeq: 1 REGISTER
Contact: <sip:55@15.137.40.20:5061;transport=TLS;line=1cd5977bcaeb059>
Max-Forwards: 70
User-Agent: iSoftPhone 2.6060
Expires: 1800
Supported: 100rel
Supported: path
Content-Length: 0
(to dest=15.137.40.40:5061)
cb_transport_error (id=1)
cb_nict_kill_transaction (id=1)
Any idea what to do next?
Use udp port 5060
-
not really sure no. what is the rule of thumb on rtp ports?
The most concurrent calls I have had is 16.
How many phone do you have?
Can't log into Web GUI as user
in Web Interface
Posted
If you have more than 1 domain, not using the localhost domain, then you need to include the domain name, when logging in.