Jump to content

maslym

Members
 View Profile  See their activity

  • Posts

    63

  • Joined

  • Last visited

 Content Type 

Posts posted by maslym

  3. Maximum Number of Calls

    in General Setup

    Posted

    Hmm. Maybe there is a mix up of calls and call legs. From the PBX perspective, it is the call leg which is expensive, the call itself is not very expensive but thats what the user perceives.

    What does the "Maximum Number of Calls" control, call legs or calls?

  4. Maximum Number of Calls

    in General Setup

    Posted

    I try to set up Maximum Number of Calls for the PBX domain in 4.3.0.5021 (Linux) and it seems in order to allow N calls, I have to enter N+1. If I set Maximum Number of Calls to 1, I cannot make any call including calling own mailbox. Any idea?

    Thank you.

  5. Ringback wave file

    in Web Interface

    Posted

    If we are talking about the extensions "mailbox" section "Ringback"

    you have to make sure when uploading a WAV file it must be 8 kHz Mono, 16 bit mono, preferably PCM format.

     

    I tested it under 2011-4.5.0.1016 Alpha Monocerotids (CentOS32)and 2011-4.3.0.5021 (Linux) and did not have to restart the service.

    All the wave files I used for test are in correct format. I even tried to delete the old ringtone wave file and upload a new one, but it still played the old deleted one. Once I restarted the service, it started to play the new wave file.

  6. Ringback wave file

    in Web Interface

    Posted

    Under admin webpage control you can see a sample file, if you don't want to restart the service, go to admin settings, configuration, towards the bottom you will see a reload configuarion section.

    I tried to save the default ringtones.xml and pnp.xml from HTML Templates and reloaded them under Reload Configuration Files section and it didn't make any difference. The system is still playing the old wave file.

     

    Thank you.

  8. Ringback wave file

    in Web Interface

    Posted

    Hi,

     

    I am using PBXnSIP 4.3.0.5021 (Linux). After I upload a new wave file as the extension's ringback tone, the system is still using the old wave file as the ringback tone. I have to restart the PBXnSIP application in order to make the new wave file work. It seems it's a bug in version 4.3.0.5021. Any idea?

     

    Thank you.

  12. Cross domain calling

    in Dial Plan Setup

    Posted

    That is strange. If the extension has a dial plan, we should not have seen that error message. Even if did not have a dialplan, then domain default dial plan should have kicked in.

     

    Anyways, can you PM the log (with log level 9 & SIP logging turned ON) for just 1 such call?

    Hi PBX support,

     

    I just PM the call log to you. Please check.

    Thank you.

  13. Cross domain calling

    in Dial Plan Setup

    Posted

    If the error is "No dial plan available", then check the account that is making the call to see if it really has a dial plan assigned.

    The account has the dial plan assigned and it could make outbound calls. It just couldn't call any DID in another domain on the same PBXnSIP server.

    Thank you.

  15. vitelity fax functionality--quick question

    in Fax Setup

    Posted

    Hello,

     

    We have a company that faxes price sheets to their clients weekly. Probably about 40 clients and each price sheet is 15 pages.

     

    vitelity seems nice but you can't seem to email/send a fax to a distribution group, you need to sent a seperate email to each fax number.

    Maybe I'm missing something?

     

    Anyone worked through this senario? Ideas welcome.

     

    Matt

     

    Check http://www.peopleline.net/pstelco/emailandfax.htm or call 604-639-2550.

  16. Cross domain calling

    in Dial Plan Setup

    Posted

    Hi pbxnsip support,

     

    Any update on this issue?

    I tried 4.0.1.3499 and still the call couldn't go through. And I got following error messages.

    [5] 2010/05/14 14:01:18: Received loopback request without tag

    [2] 2010/05/14 14:01:18: Call Reject: Could identify call domain

  18. End users can't change web GUI password

    in Web Interface

    Posted

    It doesn't work.

     

    Doesn't matter which computer I use or web browser, the end user can't change their web password.

     

    This is how I tested:

     

    1. Opened up web browser and went to domain that customer is in.

    2. Entered customer login name - 4166381234@test1.mydomain.com

    3. Entered password.

    4. Login Type is Automatic

    5. Went to settings, changed web password to test1234 did the repeat password.

    6. Clicked Save

    7. I logged out.

    8. Closed web browser - opened new web browser.

    9. Tried logging in with new password and it doesn't work - I can use the old password and that lets me login.

    10. Tried this from different computers/web browsers and still doesn't work.

     

    Is your test system setup as a multi domain? If yours is not could that make a difference as to why yours works and mine doesn't? I know it made a difference with one other bug report where your tech said it works for them but not me until I said make sure your testing in a multi domain system and not just localhost...soon as he changed it to multi domain he was able to duplicate the bug on his end.

     

    If you are testing on a multi domain system and it works for you do you have any suggestions for on how I can get this working?

     

    Can other PBXNSIP customers who are using ver 4.0.1.3442 test this to see if it's not just me that's having this problem.

     

    Thanks

     

    I tested it with latest 4.0.1.3442 on CentOS 5 and couldn't reproduce the problem you got. There are two domains set up on the server. I tested it on different extensions in both domains (one domain is localhost) and it worked okay.

  20. Cross domain calling

    in Dial Plan Setup

    Posted

    Is that a trunk that is either inbound or inbound/outbound? When you are using the outbound proxy and don't use the field "Explicitly list addresses for inbound traffic" then the transport layer does matter. The best would be if you put "127.0.0.1" into the "Explicitly list addresses for inbound traffic" setting of the trunk and make it "inbound".

     

    Of course, use 127.0.0.1 only of the packet is actually received over the loopback device. Maybe just add the IP address of the server there as well, e.g. "127.0.0.1 10.1.1.110" if "10.1.1.110" if the IP address of the PBX which is used for sending the request out. If you are using a SIP proxy, put the address of the SIP proxy there. Whereever the looped request is coming from"

    Here is the test setup.

    I set up two domains on one server running 4.0.1.3433 on CentOS 5.3. Each domain has a SIP Registration trunk and is registering to the SIP Proxy server. Since the server is behind the router, so the trunk is registering to the SIP proxy server through the outbound proxy. I tried to set up the trunk as Inbound only and put all the IP addresses related into the trunk such as 127.0.0.1, the private IP of the server, the public IP of the router, the IP of the SIP proxy server and the IP of the outbound proxy. Still the cross domain calling doesn't work.

    It was working before on version 2.x and stopped working since version 3.x.

  21. Cross domain calling

    in Dial Plan Setup

    Posted

    Well, that's your problem now: "Received incoming call without trunk information and user has not been found". That means you must have a trunk that accepts traffic from 127.0.0.1 (or ::1 in IPv6). In V4, you can explicitly put the 127.0.0.1 into the trunk now (at the bottom, "Explicitly list addresses for inbound traffic").

    Okay, I did that by putting 127.0.0.1 into the trunk and it didn't make any difference. I still got the same error messages in the logfile and the call still didn't go through.

  22. Cross domain calling

    in Dial Plan Setup

    Posted

    I quickly tested this loopback scenario again (using the latest and greatest 4.0.1.3424, let me know if you need a build/OS). The PBX blocks the loop request if the "detect loopback" is on, once it is turned off it is working as it should.

     

    I tried the latest 4.0.1.3433 on CentOS 5.3 and still got the same problem on cross domain calling. I tried to turn the "detect loopback" on and off and it didn't make any difference. I still got following error message as found in version 3.x.

    [5] 2010/03/08 16:09:52: Received loopback request without tag

    [5] 2010/03/08 16:09:52: Received incoming call without trunk information and user has not been found

    [5] 2010/03/08 16:09:57: Call 2ab08296@pbx#625927210: Last request not finished

    [5] 2010/03/08 16:09:57: BYE Response: Terminate 2ab08296@pbx

  23. MWI with only saved messages

    in Mailbox

    Posted

    Do you mean PBX is not sending the SIP NOTIFY messages when you save the message (by pressing 9 during or at the end of the message)?

    PBX is sending the SIP NOTIFY message if I press 9 to save the message.

    If I don't save the message by pressing 9 and simply hang up after hearing "This is the main menu of the mailbox", the message is also saved in the mailbox, but PBX is not sending the SIP NOTIFY message.

     

    Thanks,

     

    Yimin

×
×
  • Create New...