ap_6200
-
Posts
139 -
Joined
-
Last visited
Content Type
Profiles
Forums
Events
Posts posted by ap_6200
-
-
Customers like using Press 1 for this, Press 2 for that, and 3 this something else. They also like having extension like 101, 201, 301v etc...
what must be done in the auto attendent to allow this so that when the person calling presses the first digit in a valid extension it doesn't automatically send that caller to the quick access dial in the AA?
Some sort of delay is necessary to prevent the automatic redirect to an extension.
Supposedly using the # sign after the Direct Dial extension alleviates this - but I've had problems - especially when the direct dial extension goes to another AA.
-
In 2.1.x daily CDR's were introduced...
There is a limitation of the last 1000 calls in a 24 hour period.
In 2.1.6 I am strongly urging the following adjustments:
** - Increase the limitation on the domain from 1000 to at least 2000 - preferrably 3000.
** - Add a feature to get Daily CDR's per extension - I'm not a fan of every call CDR - especially in this volume of calls.
I am on the verge of losing a high volume customer if this cannot be implemented quickly.
Please help!
Thank you.
-
Could you be more specifik please? I didn't get any hits when googling Fro Fax.
I'm quite certain that Fro Fax was a typo... He meant to type - "For Fax........."
The key here was stating that both the PSTN gateway and the FXS gateway needs to support T.38 fax protocol.
-
Are you sure? If should read out the two new messages (in "historical" order), then the 10 saved messages ("in historical order"). If you have a lot of messages, then the historical might be an issue because you have to go through all of the messages before you get to the latest, but IHMO that is okay because as a policy.
Yes, I'm sure. If it worked like you described above - that would be fine.
-
Duplicate Ticket - but I want to make sure my voice is heard.
Is there a known issue with this and is it being fixed?
The proof is in the pudding for me... same exact setup - using 2.0.3.1715 - it works.
Using 2.1.5.2357 - doesn't work.
[8] 20080204154855: No codec available for sending
[8] 20080204154855: Last message repeated 45 times
[9] 20080204154855: Resolve 9916807: udp 10.15.237.246 1240
[8] 20080204154855: No codec available for sending
[8] 20080204154855: Last message repeated 6 times
[9] 20080204154855: Resolve 9916808: udp 15.10.174.19 5060
[8] 20080204154855: No codec available for sending
[8] 20080204154855: Last message repeated 12 times
[9] 20080204154855: Resolve 9916809: udp 15.10.174.19 5060
[8] 20080204154855: No codec available for sending
[8] 20080204154856: Last message repeated 58 times
[9] 20080204154856: Resolve 9916810: udp 10.15.237.138 10283
[8] 20080204154856: No codec available for sending
[8] 20080204154856: Last message repeated 32 times
[9] 20080204154856: Resolve 9916811: udp 10.15.237.234 49161
[8] 20080204154856: No codec available for sending
[8] 20080204154856: Last message repeated 61 times
[8] 20080204154856: SNMP: Received unknown object identifier 06082b06010201010300
[8] 20080204154856: No codec available for sending
[8] 20080204154856: Last message repeated 14 times
[9] 20080204154856: Resolve 9916812: udp 10.15.236.70 4217
[8] 20080204154856: No codec available for sending
[8] 20080204154857: Last message repeated 49 times
[9] 20080204154857: Resolve 9916813: udp 15.10.174.19 5060
[8] 20080204154857: No codec available for sending
[8] 20080204154857: Last message repeated 12 times
[9] 20080204154857: Resolve 9916814: udp 10.15.236.162 16626
[8] 20080204154857: No codec available for sending
[8] 20080204154857: Last message repeated 9 times
[9] 20080204154857: Resolve 9916815: udp 15.10.174.19 5060
[8] 20080204154857: No codec available for sending
[8] 20080204154857: Last message repeated 42 times
[9] 20080204154857: Resolve 9916816: udp 15.10.174.19 5060
[8] 20080204154857: No codec available for sending
[8] 20080204154857: Last message repeated 17 times
[9] 20080204154857: Resolve 9916817: udp 10.15.237.138 10229
[9] 20080204154857: Resolve 9916818: udp 10.15.237.138 10244
[8] 20080204154857: No codec available for sending
[8] 20080204154857: Last message repeated 6 times
[9] 20080204154857: Resolve 9916819: udp 15.10.174.19 5060
[8] 20080204154857: No codec available for sending
[8] 20080204154857: Last message repeated 21 times
[9] 20080204154857: Resolve 9916820: udp 10.15.237.138 10238
[8] 20080204154857: No codec available for sending
-
Was this version posted for beta testing?
I'm also getting reports of DTMF issues on certain automated systems:
I tested with 2.0.3.1715 and it works fine.. But with the latest release of 2.1.5 I get the following errors:
[8] 20080204154855: No codec available for sending
[8] 20080204154855: Last message repeated 45 times
[9] 20080204154855: Resolve 9916807: udp 10.15.237.246 1240
[8] 20080204154855: No codec available for sending
[8] 20080204154855: Last message repeated 6 times
[9] 20080204154855: Resolve 9916808: udp 15.10.174.19 5060
[8] 20080204154855: No codec available for sending
[8] 20080204154855: Last message repeated 12 times
[9] 20080204154855: Resolve 9916809: udp 15.10.174.19 5060
[8] 20080204154855: No codec available for sending
[8] 20080204154856: Last message repeated 58 times
[9] 20080204154856: Resolve 9916810: udp 10.15.237.138 10283
[8] 20080204154856: No codec available for sending
[8] 20080204154856: Last message repeated 32 times
[9] 20080204154856: Resolve 9916811: udp 10.15.237.234 49161
[8] 20080204154856: No codec available for sending
[8] 20080204154856: Last message repeated 61 times
[8] 20080204154856: SNMP: Received unknown object identifier 06082b06010201010300
[8] 20080204154856: No codec available for sending
[8] 20080204154856: Last message repeated 14 times
[9] 20080204154856: Resolve 9916812: udp 10.15.236.70 4217
[8] 20080204154856: No codec available for sending
[8] 20080204154857: Last message repeated 49 times
[9] 20080204154857: Resolve 9916813: udp 15.10.174.19 5060
[8] 20080204154857: No codec available for sending
[8] 20080204154857: Last message repeated 12 times
[9] 20080204154857: Resolve 9916814: udp 10.15.236.162 16626
[8] 20080204154857: No codec available for sending
[8] 20080204154857: Last message repeated 9 times
[9] 20080204154857: Resolve 9916815: udp 15.10.174.19 5060
[8] 20080204154857: No codec available for sending
[8] 20080204154857: Last message repeated 42 times
[9] 20080204154857: Resolve 9916816: udp 15.10.174.19 5060
[8] 20080204154857: No codec available for sending
[8] 20080204154857: Last message repeated 17 times
[9] 20080204154857: Resolve 9916817: udp 10.15.237.138 10229
[9] 20080204154857: Resolve 9916818: udp 10.15.237.138 10244
[8] 20080204154857: No codec available for sending
[8] 20080204154857: Last message repeated 6 times
[9] 20080204154857: Resolve 9916819: udp 15.10.174.19 5060
[8] 20080204154857: No codec available for sending
[8] 20080204154857: Last message repeated 21 times
[9] 20080204154857: Resolve 9916820: udp 10.15.237.138 10238
[8] 20080204154857: No codec available for sending
Please advise quickly.
Thanks!
-
Version: 2.1.6.2433 (Win32) and also when we used the previous version. 2.1.5.????
Was this version posted for beta testing?
-
Well, ultimately that will be in the release notes. Out of my head currently:
- Agent queue fixes: The LIFO algorithm added all agents without delay at the same time
- Agent queue is not able to send daily emails with agent statistics
- all accounts can now have descriptive names
- dongle support for Linux (well maybe we have to drop debian 3.1 support because of that)
Is there an easy way to reverse the order that the voice messages are played?
Currently, if the user has 10 saved voice messages, he has to listen to all 10 before getting to his 2 new messages.
Thanks
- Agent queue fixes: The LIFO algorithm added all agents without delay at the same time
-
Oh you mean someone has a personal DID and that someone should be able to tell if the DID has been dialled or the call came in through the AA? Hmm, at the moment I don't see a useful way of doing this...
That is correct... Initially I was thinking that you could do something equivalent to identifying if the call came from the Agent Queue by setting this field:
From-Header: Calling-Party Group name Group name (Calling Party)
I have a pseudo work around in place by assigning the user a different extension and labled it PL for Private Line and routed his direct DID to the new extension... But I'd rather not create 2 accounts for each user.
-
We added the option to send an email with the CDR after every call. I am using it already and it makes sense to me. It is my Outlook's job to sort the emails correctly into the right folder and I never have to worry about writing numbers down.
Hmmm.. With heavy call volume - this would seem cumbersome to receive say 200 emails a day, as opposed to 1.
Can we customize this?
-
I know that it was added for the exchange server 2007 um integration so we could tell who to bill for the call on that trunk in the CDR. I thougth that if you look at the CDR it would show the AA was called first then transferred to the extension. What are you trying to do?
I'm trying to find a way for a customer to differentiate calls dialed directly to him - as opposed to calls coming from the AA
-
I have a main auto attendant with a prompt 4# to go to a sub auto attendant with a directory listing.
About 2 seconds after the sub listing starts playing the greeting, it gets interupted with a message please enter your entension number.
If I dial the extension number of the sub auto attendant directly, without first going to the main auto attendant it works fine.
All other menu's that do not have a # work fine.
The time out on the main autoattendant is set to 60 seconds.
I've experienced this same problem with the latest release of pbxnsip... I hadn't posted it yet.
-
Can anyone point me to the reference manual on this?
I can't find it in the wiki - (using 2.1.5)
Also - is there any way to be able to distinguish to a user when a call is dialed directly to their extension from the trunk - or if it came through the auto-attendant?
Thanks
-
In addition to this - I have a feature request that I believe is very beneficial to the customers.
I would like to request a CDR on a per account basis. Currently it's the entire domain, but parsing through those can be somewhat cumbersome.
I propose a CDR for each extension, and I don't believe it should be that hard to implement, as the USER call lists are already in the system.
Please let me know about both of these requests - as it is for a major client.
Thank you,
One More Request Please - Can we have the ability to have a domain admin-type account, with access to change account settings, AA settings, etc.. But just NOT have the ability to ADD/CREATE additional extensions,service flags, etc..
PLEASE let me know about all of my Feature Requests as soon as you can.
Thank you
-
Why does it scare you?
In addition to this - I have a feature request that I believe is very beneficial to the customers.
I would like to request a CDR on a per account basis. Currently it's the entire domain, but parsing through those can be somewhat cumbersome.
I propose a CDR for each extension, and I don't believe it should be that hard to implement, as the USER call lists are already in the system.
Please let me know about both of these requests - as it is for a major client.
Thank you,
-
Having more than 1000 entries scares me...
Why does it scare you?
-
Probably not a bug, but a limitation of the system... Daily CDR's appear to only grab the last 1000 calls (in a 24 hour period)
Can we get this adjusted to all calls within the time period?
-
This issue is resolved - it was a problem on the domain settings for account.
(Maybe I should've triple-checked)
Thanks!
My issue was a simple one - ,com and .com are very different. ;-)
-
I'm on the latest 2.1.5
This issue is resolved - it was a problem on the domain settings for account.
(Maybe I should've triple-checked)
Thanks!
-
Maybe it makes sense to get an Wireshark trace and see what exactly goes back and forth. What version are you running?
I'm on the latest 2.1.5
-
I have gone through and doublechecked all of the domain settings - but I'm still seeing a high percentage of "Last Email could not be sent"
I have removed IP's and domain names to protect the innocent:
This is log level 8 - by the way.
[8] 2008/01/22 15:46:54: SMTP: Connect to 1.2.3.4:25
[8] 2008/01/22 15:46:54: SMTP: Received 220 mail-02.name-services.com Microsoft ESMTP MAIL Service, Version: 6.0.3790.3959 ready at Tue, 22 Jan 2008 13:50:39 -0800
[8] 2008/01/22 15:46:54: SMTP: Received 250-mail-02.name-services.com Hello [5.4.3.2]
250-AUTH=LOGIN
250-AUTH LOGIN
250-TURN
250-SIZE 10485760
250-ETRN
250-PIPELINING
250-DSN
250-ENHANCEDSTATUSCODES
250-8bitmime
250-BINARYMIME
250-CHUNKING
250-VRFY
250 OK
[8] 2008/01/22 15:46:54: SMTP: Received 334 VXNlcm5hbWU6
[8] 2008/01/22 15:46:55: SMTP: Received 334 UGFzc3dvcmQ6
[8] 2008/01/22 15:46:55: SMTP: Received 235 2.7.0 Authentication successful
[8] 2008/01/22 15:46:55: SMTP: Received 501 5.5.4 Invalid Address
[5] 2008/01/22 15:46:55: SMTP Server returned 501
Is there any other indication on what the "Invalid Address" is?
On successful emails, the next thing I should see is:
[8] 2008/01/22 15:45:20: SMTP: Received 235 2.7.0 Authentication successful
[8] 2008/01/22 15:45:20: SMTP: Received 250 2.1.0 test@messaging.com....Sender OK
[8] 2008/01/22 15:45:20: SMTP: Received 250 2.1.5 joe@smith.com
So is it a problem with the sender??
-
Low Priority Feature Request for 2.1.5.x or 2.1.6.x
Auto Attendant "Names" are a very nice addition.
If you could also put the Agent Groups "Name" on the Extensions listing - that would be a good thing for customers with multiple Agent Groups.
Thanks,
-
Has anyone else experienced any 2.1.5 issues?
Please post your comments and/or concerns.
Thanks!
-
We upgraded to 2.1.5 and moved some domains off of this particular FS to load balance across the server farm.
This will give me a clear indication on Monday or Tuesday if indeed I have reached the upper echelon of active calls without affecting voice quality.
By no means am I happy with this solution, because I should be able to do more than what i'm able to do - but the limitations are there, and nobody from PBXnSIP has been able to offer me any other suggestions. I have 6 FS's for my customer base, all built identically.. The only one I'm having trouble with - is the one I described earlier.
I am not seeing any negative indication from the server itself - it is only the Media CPU Usage graphed in PBXnSIP.
Using 1 2 and 3 for direct dial and using 3 digit extension
in Auto Attendant Setup
Posted
It should say 1# and 2# - not the destination field. The # makes the pbx wait 3 seconds.