Jump to content

iActive

Members
 View Profile  See their activity

  • Posts

    33

  • Joined

  • Last visited

 Content Type 

Posts posted by iActive

  2. extension alias problem

    in Extension Setup

    Posted

    I thought I just saw a wiki that actually explained how to alias an account to a DID but did so in an opposie manor than what I saw in the manual. Maybe I'm missing something?

     

     

    What if I wanted to route a DID and TFN to one account is this possible and how would it be done?

  3. extension alias problem

    in Extension Setup

    Posted

    Still does not answer the question.

     

    Why does an account not answer when it is setup like this 90 7891234567

    this is how the manual says to alias an account.

     

    However

    When we setup the account like this 90/7891234567

    this seems to work but it creates another account call 7891234567<90>

  6. extension alias problem

    in Extension Setup

    Posted

    Hello,

     

    We have a new setup and we are trying to attach a DID to a particular extension (90). The manual says that we can create an account and create an alias using the following format 90 7891234567. When we create an account 90 7891234567 save it then try to call the DID 7891234567 we get a message that the account or number could not be found.

     

    So if we change the account and set it as 90/7891234567 save the account. Now when we call 7891234567 the call completes without issue. However when creating a account alias to a DID using the / another account is created on the system which uses another user license.

     

    How can we create a DID alias to an account without having to use another license?

     

    Thanks,

    Greg

  8. Real Instructions for Setting up WAN PNP

    in Plug and Play

    Posted

    A large company out of California specified in the old days that the way to talk to the provisioning phones is tftp. Now we all have to live with that default decision. This is not what I would call NAT-friendly. There are plenty of other ways; but this is the default. You can also use HTTP, but then you need to manually tell that the phones and you need to specify the path from which the files need to be downloaded.

     

    If the server is behind NAT you will have a very hard time to get it working anyway. VoIP uses UDP for the media transport, and that is extremly NAT unfriendly. Practically speaking, you need a "routable" IP address--one that can be reached from all devices that indent to use the service. AKA known as "public" IP address (but it does not have to be public, e.g. in company VLAN, VPN and so on).

     

    If both the PBX and the phones are behind NAT things get (alomost) funny. "If you want to send me media, send it to 10.1.2.3"--"okay, and if you want to send me something send it to 192.168.1.2". Thank you!

     

    Fortunately, the last IPv4 address has just been assigned and hopefully soon the whole NAT madness will be over.

     

    okay so is there a solid step by step instruction available for setting up tftp? Do I need to create some files ahead of time? if so where do i put them? how should they look? what url do I use?

     

    has anyone been able to get it this to work in a similar setup? if so can you share what you did?

  10. Real Instructions for Setting up WAN PNP

    in Plug and Play

    Posted

    I've have been through so many manuals, wiki's, snome support site, pbxnsip support site, all of these different documents, etc. in regards to WAN PnP and we still have not been able to get it setup. Does anyone have true step by step instructions for setting up WAN based PnP for SnomOne using snom300 phones? Instructions that when followed result in a system that actually works?

  11. server IP and auto provision

    in Plug and Play

    Posted

    Did you try to load this file from the web browser? If that does not work, did you change anything in pnp.xml or did you change this file (either in the web interface or on the file system)? "It should work", I checked here.

     

    It does not load from the web browser. I did not change anything this is a fresh install.

  12. server IP and auto provision

    in Plug and Play

    Posted

    that's resolved

     

    now..

     

    When when the phone goes to <public ip>/provisioning/snom300.htm it produces this output

     

    <?xml version="1.0" encoding="utf-8" ?>

    - <setting-files>

    <file url="<public ip>/prov/snom_3xx_fw.xml?model=snom300" />

    <file url="<public ip>/prov/snom_3xx_phone.xml?model=snom300" />

    <file url="<public ip>/prov/snom_300_fkeys.xml?model=snom300" />

    <file url="<public ip>/prov/snom_web_lang.xml?model=snom300" />

    <file url="<public ip>/prov/snom_gui_lang.xml?model=snom300" />

    </setting-files>

     

    when the phone connects to <public ip>//prov/snom_3xx_fw.xml?model=snom300 it produces this output

    <?xml version="1.0" encoding="utf-8" ?>

    - <phone-settings>

    <firmware_status perm="RW"><public ip>/prov/snom_3xx_fs.xml?model=snom300</firmware_status>

    </phone-settings>

     

    and when the phone finally tries to go to <public ip>/prov/snom_3xx_fs.xml?model=snom300

     

    We get the following output

     

    File snom_3xx_fs.xml is empty

    Please ask your system administrator to check the log file.

  14. server IP and auto provision

    in Plug and Play

    Posted

    well this issues was that I needed to upgrade because my version did not have the web page control tab. Now that I've upgraded I see the tab and I've made the change to snom_300.xml document but now according the logs I need to change the 300fs and 300fw files and apparently I need to load some configuration file else the phone will not be provisioned. Any advice or if you could point me to the correct documentation I can learn for myself.

  16. server IP and auto provision

    in Plug and Play

    Posted

    I am setting up provisioning for over the WAN and I was wondering if there was any way to override the IP address that the PBX thinks it should use in the provisioning links.

     

    Example - our publix PBX is NAT'd behind a firewall. Instead of presenting Phone login requests with the public IP address of the PBX it is sending out the internal IP address and the external phones are not able to register.

     

    <?xml version="1.0" encoding="utf-8" ?>

    - <setting-files>

    <file url="http://192.168.204.50:80/prov/snom_3xx_fw.xml?model=snom300" />

    <file url="https://192.168.204.50:443/prov/snom_3xx_phone.xml?model=snom300" />

    <file url="https://192.168.204.50:443/prov/snom_3xx_fkeys.xml?model=snom300" />

    <file url="https://192.168.204.50:443/prov/snom_web_lang.xml?model=snom300" />

    <file url="https://192.168.204.50:443/prov/snom_gui_lang.xml?model=snom300" />

    <file url="https://192.168.204.50:443/tftp/snom_300_custom.xml" />

    </setting-files>

     

     

    Is there any way to change the IP address that is used here?

     

    Greg

  20. Various Issues with our new setup

    in General Setup

    Posted

    update to my dilemma

     

    call from a Snom821

     

    to a Snom 300 -> no audio can be heard

    to a external number just by picking up the handset-> no audio both ways

    to a external number by selecting a line before picking up the handset -> audio both ways

     

    page from a Snom821

     

    to a Snom 300 -> no audio either way

     

    intercom from a Snom 821

     

    to a Snom 300 -> no audio either way

     

     

     

    Intercom, paging, dialing from a Snom 300

     

    to a Snom 821 -> audio both ways always works.

×
×
  • Create New...