Jump to content

voipguy

Members
  • Posts

    293
  • Joined

  • Last visited

Everything posted by voipguy

  1. Read my prev post - SPA2102
  2. It's not simple and I only know of one company that is doing https - they are the ones that made the https firmware that runs in the AudioCodes ATA's.
  3. Do not use the PAP2T - this unit is not good for fax. The SPA2102 adapter is much better - run the latest firmware from Linksys ver 5.2.12 which was just released end of Jan/2011. The new firmware made the T.38 faxing much better. You can have the 2 ports on SPA2102 to handle 1 port for faxing and second port for credit card machine. The reason you need credit card machine on second port is because you have to set special settings on that port to get the visa machine to send data over voip. Https faxing is the best - I think the guys over at Nexsip have this running now.
  4. Maybe try the latest SNOM firmware ver 8.4.31 which was just released yesterday. http://provisioning.snom.com/download/fw/snom870-8.4.31-SIP-r.bin
  5. I can confirm this has been fixed in ver 4.2.1.4001 Thanks
  6. I can confirm the 5 second delay is now gone - fixed in ver 4.2.1.4000
  7. Per http://forum.pbxnsip.com/index.php?/topic/3124-does-soap-expose-all-pbxnsip-objects/page__pid__19081#entry19081 it doesn't exposes all of pbxnsip's objects.
  8. This is not a bug....if you listen to the message and then just hangup the phone the mwi will still blink....after you listen to the message you have to take an action - press 7 to delete or press 9 to save....if you press 9 to save you will see the mwi stop blinking.
  9. Can you confirm this will be fixed soon? Thanks
  10. I'm on .3981 and still have the 4 or 5 second delay.
  11. They load the directory data into the phone a different way now....I think it used to be XML which was fast but now it's LDAP (Lightweight Directory Access Protocol)which takes 4 or 5 seconds on my phone to load the data.
  12. Just found this bug today which I hope will be fixed soon. PBXNSIP 4.2.0.3981 Linux 32 bit running on centos 5 64bit We have an after hours mailbox 250 that is setup to email the voice message to 2 email addressess...1 goes to my Outlook email box and the other goes to my gmail email account which is setup on my iPhone. On my iPhone I use the built in email client to retrieve my gmail email/voice messages and I click on the attachment to listen to the wave file in my iphone and it plays the voicemail message over the iphone speaker. The above setup has worked for the past 2 years until today when I set the option under Accounts then under the Email tab you will see the option "After sending a message" it was set to "keep message as new message" but today I changed it to "delete the message". I still get the voicemail message sent to both email addresses and when I listen to the message on my Outlook desktop email 1 account it plays fine but on my iphone when you click on the wave file it opens and states "This movie format is not supported." so now it can't play the attached wave files....I then put the option "After sending a message" back to what it was "keep message as new message" and left a test message and now on my iPhone when I click on the attached wave file it plays no problem. You can duplicate this bug everytime you toggle that option/setting. It's not the iPhone, it's not gmail....it's when I set the "After sending a message" to "delete the message" then all messages sent to my iPhone can't play the wave file. All the messages sent to my Outlook desktop email 1 account play fine. I also have other mailboxes set to send messages to my iphone and I can play those wave files because I have the "After sending a message" it set to "keep message as new message". We want our after hours mailbox 250 to delete the message after it emails it but because of this bug we can't. It looks like when the setting "After sending a message" is set to "delete the message" it is not formatting the wave file properly and that's why the iphone can't play it?? soon as you turn it back to "keep message as new message" the iphone can then play the new messages/wave files that come in. Anyone that wants to test this of course would have to have an iPhone and an email account setup on your iPhone and have your voicemail messages sent there....doesn't matter if it's a gmail email account. Please confirm this is a bug. Thanks
  13. I turned on the logging and it's definitely not recording the 911 calls even when I set the users account to ON for "Record outgoing calls to emergency". My log.... [8] 2011/02/09 21:20:05: Last message repeated 6 times [8] 2011/02/09 21:20:05: Could not find a trunk (41 trunks) [7] 2011/02/09 21:20:05: Set packet length to 20 [6] 2011/02/09 21:20:05: Sending RTP for 3c2af091d007-rh3p3vyggbhk to 192.168.1.25:56612, codec not set yet [8] 2011/02/09 21:20:05: Call from an user 224 [8] 2011/02/09 21:20:05: To is <sip:911@mydomain.com;user=phone>, user 0, domain 2 [8] 2011/02/09 21:20:05: From user 224 [8] 2011/02/09 21:20:05: Set the To domain based on From user 224@mydomain.com [8] 2011/02/09 21:20:05: Call state for call object 5166: idle [7] 2011/02/09 21:20:05: set_codecs: for 3c2af091d007-rh3p3vyggbhk codecs "", codec_preference count 3 [5] 2011/02/09 21:20:05: Dialplan "mypbxnsiptrunk": Match 911@mydomain.com to <sip:the911number@myproxyip;user=phone> on trunk mypbxnsiptrunk [8] 2011/02/09 21:20:05: DNS: Add AAAA smtp.myisp.ca (ttl=60) [8] 2011/02/09 21:20:05: Play audio_moh/noise.wav [7] 2011/02/09 21:20:05: set_codecs: for 5e6e8de4@pbx codecs "18 0", codec_preference count 3 [8] 2011/02/09 21:20:05: Answer challenge with username mypbxnsiptrunk [7] 2011/02/09 21:20:05: Set packet length to 20 [6] 2011/02/09 21:20:05: Codec g729/8000 is chosen for call id 3c2af091d007-rh3p3vyggbhk [8] 2011/02/09 21:20:05: SMTP: Connect to ipaddress:25 [8] 2011/02/09 21:20:05: SMTP: Received 220 ip03.myisp.ca ESMTP [8] 2011/02/09 21:20:05: SMTP: Send EHLO localhost [8] 2011/02/09 21:20:05: SMTP: Received 250-ip03.myisp.ca 250-8BITMIME 250 SIZE 31457280 [8] 2011/02/09 21:20:05: SMTP: Send MAIL FROM:<pbx@mymaildomain> [8] 2011/02/09 21:20:05: SMTP: Received 250 sender <pbx@mymaildomain> ok [8] 2011/02/09 21:20:05: SMTP: Send RCPT TO:<me@mydomain.com> [8] 2011/02/09 21:20:05: SMTP: Received 250 recipient <me@mydomain.com> ok [8] 2011/02/09 21:20:05: SMTP: Send DATA [8] 2011/02/09 21:20:05: SMTP: Received 354 go ahead [8] 2011/02/09 21:20:05: SMTP: Send From:pbx@mymaildomain To:<me@mydomain.com> Subject: =?UTF-8?Q?mycompanyname:_224_is_calling_911!?= Date: Thu, 10 Feb 2011 01:20:05 -0000 MIME-Version: 1.0 Content-Type: text/plain Content-Length: 89 [...] [8] 2011/02/09 21:20:05: SMTP: Received 250 ok: Message 796407137 accepted [8] 2011/02/09 21:20:05: SMTP: Send QUIT [8] 2011/02/09 21:20:05: SMTP: Received 221 ip03.myisp.ca [8] 2011/02/09 21:20:05: Sucessfully sent email to <me@mydomain.com> [8] 2011/02/09 21:20:05: Packet authenticated by transport layer [6] 2011/02/09 21:20:05: Sending RTP for 5e6e8de4@pbx to ipaddress:4690, codec not set yet [7] 2011/02/09 21:20:05: Set packet length to 20 [6] 2011/02/09 21:20:05: Codec g729/8000 is chosen for call id 5e6e8de4@pbx [8] 2011/02/09 21:20:05: Call state for call object 5166: alerting [7] 2011/02/09 21:20:05: 3c2af091d007-rh3p3vyggbhk: RTP pass-through mode [7] 2011/02/09 21:20:05: 5e6e8de4@pbx: RTP pass-through mode [8] 2011/02/09 21:20:05: SRTP MAC mismatch: 4238c45d != 00000000 [7] 2011/02/09 21:20:05: Discard SRTCP packet from ipaddress:57830 with wrong MAC [6] 2011/02/09 21:20:05: Sending RTP for 3c2af091d007-rh3p3vyggbhk to ipaddress.45:57831, codec g729/8000 [8] 2011/02/09 21:20:06: Packet authenticated by transport layer [8] 2011/02/09 21:20:14: Last message repeated 7 times [7] 2011/02/09 21:20:14: Call 5e6e8de4@pbx: Clear last INVITE [7] 2011/02/09 21:20:14: Set packet length to 20 [7] 2011/02/09 21:20:14: Determine pass-through mode after receiving response [8] 2011/02/09 21:20:14: Call state for call object 5166: connected [8] 2011/02/09 21:20:15: Packet authenticated by transport layer [8] 2011/02/09 21:20:23: Last message repeated 4 times [8] 2011/02/09 21:20:23: Trunk 32 (507114) is associated with the following addresses: udp:myproxyip:5060 [8] 2011/02/09 21:20:26: Packet authenticated by transport layer [8] 2011/02/09 21:20:30: Last message repeated 3 times [7] 2011/02/09 21:20:30: 5e6e8de4@pbx: Media-aware pass-through mode [8] 2011/02/09 21:20:30: Hangup: Call 80 not found [8] 2011/02/09 21:20:30: Last message repeated 2 times [7] 2011/02/09 21:20:30: Call 5e6e8de4@pbx: Clear last request [5] 2011/02/09 21:20:30: BYE Response: Terminate 5e6e8de4@pbx [8] 2011/02/09 21:20:30: Packet authenticated by transport layer [8] 2011/02/09 21:20:31: Trunk 39 (507183) is associated with the following addresses: udp:myproxyip:5060 [8] 2011/02/09 21:20:31: Trunk 46 (506040) is associated with the following addresses: udp:myproxyip:5060 [8] 2011/02/09 21:20:31: Trunk 48 (502156) is associated with the following addresses: udp:myproxyip:5060 [8] 2011/02/09 21:20:31: Trunk 50 (507227) is associated with the following addresses: udp:myproxyip:5060 [8] 2011/02/09 21:20:31: Trunk 41 (507218) is associated with the following addresses: udp:myproxyip:5060 [8] 2011/02/09 21:20:31: Trunk 49 (507244) is associated with the following addresses: udp:myproxyip:5060 [8] 2011/02/09 21:20:31: Trunk 47 (506710) is associated with the following addresses: udp:myproxyip:5060 [8] 2011/02/09 21:20:32: Packet authenticated by transport layer I did about 5 tests and checked the recording directory and the call was not recorded. I think this is a bug.
  14. We have the recording in our license.....we record all our calls - few hundred a day.
  15. This one - "Or the message got cut off prematurely?" When it happens again I'll look for the file in my linux box and see the file size.
  16. This has also happened to me. Person calls and leaves me a 40 second message, PBXNSIP emails the message to me and it states (40 seconds)in the email but when I listen to the attached wave file it's only 10 or 15 seconds long...I then picked up my SNOM 370 phone to listen to the message and it stops after 10 or 15 seconds....so it's not a corrupt wave file it's the PBXNSIP software. I called the person back and asked if after 10 or 15 seconds did my system hangup on you and he said no he left the full message. This has happened in past versions but it just happened when I went to ver 4.2.0.3981 linux centos 32bit....only 1 time so far.
  17. Record outgoing calls to emergency numbers - I don't think this feature is working or I can't find where it stores the recording. PBXNSIP 4.2.0.3981 Linux centos 32 bit running on centos 5 64bit Under Domain Settings we have Record outgoing calls to emergency numbers set to Yes, we also have the setting Emergency numbers: 911. For the Account in question we have under the Redirection tab Record outgoing calls to emergency numbers set to default. For the PBXNSIP system under Settings we have Record Location: $r/$o/$a/$d-$t-$i-$n-$u.wav 911 was called and the system knows this because it sent us an email stating "Account *blanked out* is calling the emergency number 911 at 2011/02/08 15:49:59" but we can't find where the recording is stored or it's not working. Please let us know if this is a bug. Thanks
  18. can you post a link for Centos version? 4.2.0.3966
  19. You can do it with a * code... *84 you would have to do it from that phone...one downside is that it also resets the voicemail greeting and maybe the password - can't remember it's been awhile since I last did it.....I believe the *84 code "Clean up extension" is used in the "Hotel" version of the software but it's also in the default version.
  20. Yes, the setting is not in WAC but in your PBXNSIP settings under Settings/General/Appearance - Web Session Timeout: it's valu is in seconds so 10 hours would be 36,000 seconds.
  21. ....my live system running ver 4.2.0.3903 just locked up....went back to stable 4.1.0.4031.
  22. SNOM Directory button broke in ver 4.2.0.3903 Just noticed when you press the Directory button on my SNOM 370 it no longer lists my stored names and numbers. I did a reboot on my phone but got same results.
×
×
  • Create New...