[G729 w/ 5.0.4 under OS X - garbled]

Using the G729 codec w/ 5.0.4 under OS X produces garbled audio. Trucks to voip.ms and callcentric. No issues under 4.5 and no issue with other codecs in 5.0.4. Anyone else see this?

 

Version: 5.0.4 (MacOS)

Created on: Jan 24 2013 17:26:46

License Status: snom ONE forty xxxxxxxxxxxxx

[Version 5]

Any word on "Other operating systems will follow soon."

[License after upgrade to V5]

You don't have to pay for the vouchers. We expect that the vouchers are used to upgrade the existing snom ONE blue or yellow installation.

 

Never mind, I didn't see this on the website before "Just use your version 4 activation code as a voucher, and you get 50 % off the bundle price."

[License after upgrade to V5]

What are the values of the vouchers? I like to know that before I chose a bundle.

[Error code 57]

I'm no longer seeing the error 57 when using 4.5.0.1075 Delta Aurigids (MacOS). I still frequently see error 60 but it doesn't seem to be causing any troubles.

 

(I've had one blind transfer fail that I think should not have, I monitor that.)

[Error code 57]

I created 2 test installations of snomONE under OS X and 1 under Linux. Both OS X installs exhibited the behavior eventually (anywhere from 3 to 10 calls to the IVR after starting up). I couldn't make it happen with Linux.

 

Good, come right back with the destination

[8] 20120503160559: Call from an user 509

[8] 20120503160559: To user 500

[8] 20120503160559: Call state for call object 51: idle

[8] 20120503160559: Call state for call object 51: connected

[5] 20120503160559: set codec: codec pcmu/8000 is set to call-leg 50

[5] 20120503160559: Last message repeated 3 times

[8] 20120503160559: HTTP client: Connect to 10.89.20.90:80, pending requests 0

[8] 20120503160559: Received response code 200 with destination 512

 

 

Bad, comes right back with the error 57, also note the error 60, doesn't always happen right before a 57

[8] 20120503160614: Call from an user 509

[8] 20120503160614: To user 500

[8] 20120503160614: Call state for call object 52: idle

[8] 20120503160615: Call state for call object 52: connected

[4] 20120503160615: select returns error 60 (rtp)

[5] 20120503160615: set codec: codec pcmu/8000 is set to call-leg 51

[5] 20120503160615: Last message repeated 3 times

[8] 20120503160615: HTTP client: Connect to 10.89.20.90:80, pending requests 0

[5] 20120503160615: Could not send 535 bytes to 10.89.20.90, error code 57

[Error code 57]

As far as I call tell there is no delay.

 

I'm suspecting something went wrong with the update, now 2 users mentioned transfers disconecting calls. Going from 4.2 to 4.5 nothing other than the binary needs to be changed, right?

 

It (IVR/SOAP) works fine with pbxctrl-darwin9.0-2011-4.5.0.1016 but not with 1030 or 1050.

 

I got more reports of 4.5.0.1050 disconnecting transfers, I've reverted to 4.2.1.4025.

[Error code 57]

Error code seems to be related to "Socket is not connected".

 

PBX tries to connect to 10.2.3.4:8080 first before sending the data. Possibly, it is taking more time to connect to 10.2.3.4:8080.

Does the server on the 10.2.3.4:8080 accept connections without any delay?

 

As far as I call tell there is no delay.

 

I'm suspecting something went wrong with the update, now 2 users mentioned transfers disconecting calls. Going from 4.2 to 4.5 nothing other than the binary needs to be changed, right?

[Error code 57]

Not sure which OS you are on. But sometimes the firewalls, do not like it when the executable is changed. May be some issue with the outbound rules?

 

I'm on OS X with no software firewall.

 

I'm not seeing any TCP traffic on port 8080 on the snomONE machine or the web server (different machines). It seems to me that the PBX is timing out because it never made the http request.

 

It works occasionally, usually 3 times in a row but I can't reliably reproduce it. When it does work I see the TCP traffic as expected.

[Error code 57]

The timeout means PBX could not connect to the server on 10.2.3.4:8080.

 

Set the log level to 8 (Web Client) and you should see bit more information that can help us see what is going on.

 

1 more line:

 

[8] 2012/04/30 12:56:53: HTTP client: Connect to 10.2.3.4:8080, pending requests 0

[5] 2012/04/30 12:56:53: Could not send 555 bytes to 10.2.3.4, error code 57

[4] 2012/04/30 12:57:53: HTTP client: Timeout on 10.2.3.4:8080

[3] 2012/04/30 12:57:53: IVR Node: Received http code 0

 

 

Whitelist, Settings/Access and add an allow entry? Did that, same results. Also same results when trying a different URL on different server, which also worked with 4.2.

 

Messing around with the time out and different lengths of the message I just had it working but a few minutes later I can't recreate. This is what I have/want:

 

No wav file

DTMF Match List:!T!310!

Timeout: 0

[Error code 57]

I have an IVR node with a SOAP URL that works fine with 4.2.1.4025 but when I use 4.5.0.1050 I see this in the log.

 

[5] 2012/04/30 11:09:25: Could not send 555 bytes to 10.2.3.4, error code 57

and a minute later

[4] 2012/04/30 11:10:25: HTTP client: Timeout on 10.2.3.4:8080

 

 

On the webserver I only see the request several minutes later and if I call the IVR 3 times in a row on the webserver the 3 request all come at the same time. Ideas?

[IVR patern]

Something like !E!70! !T!70! will send the call to account 70 either on end of the message or on a timeout (Note: timeout depends on the "Timeout" field on the IVR account).

 

It would be nice if this (the E and T) made it into the documentation. It would have saved me a lot of time. With a DTMF match of !T!999! and a time out of 0, I can go to SOAP right away. I knew I was missing something. :roll eyes:

[Personal Virtual Assistant]

Doesn't seem to be working for me. When I call in from my cell I don't get the usual Auto Attendant (so far so good), just silence. Pressing 4 to get to the AA followed by an extension also doesn't work. Any ideas?

 

2011-4.2.1.4025 (Darwin)

[snom m9 and call transfering]

Hi Matt,

 

Thanks, I'm on 9.2.42-us-a. Oops, I missed that on the m9 forums, it's hard to keep up with a moving target.

[snom m9 and call transfering]

Trying to transfer a call from a snom m9 results in the call getting disconnected and in log I see:

REFER from device type "" is not supported in this product

 

What am I doing wrong?

[Where to change cdr_field_separator]

Got to reboot this evening, is there something special about the | (pipe) character? All SIP trucks would not register. Changing back to , (comma) and all was well again. Any suggested character?

[Where to change cdr_field_separator]

Got it, pbx.xml. I must have made a typo when greping.

[Where to change cdr_field_separator]

I need to change the cdr_field_separator, as some caller ID names have a comma in the in them (ie Last, First) but don't know where to change this.

[BLF button is picking up]

Thanks. Even after removing *87 I'm able to pick up a call by hitting the BLF.

 

The documentation says "This mode [bLF] is similar to the monitor extension mode; however, it does not support the picking up of calls." I'm not seeing a difference between the two modes. If set it up on the phone and not in snomOne it works as expected.

[BLF button is picking up]

This is a problem, am I the only one seeing this? What could possibly be wrong?

[Prevent outbound calls]

There is no difference for the PBX between using a registered SIP extension and a cell phone when placing outbound calls.

Thanks for the clarification, that helps.

[Prevent outbound calls]

How do I prevent outbound calls from cell phones ("To place an outbound call press 1")? I really like press 2's simplicity and I think I need press 3 functionality to remotely setting service flags.

[MWI never stops on 4.2.0.3981]

Thanks voipguy.

[BLF button is picking up]

Is anybody else seeing this?

[MWI never stops on 4.2.0.3981]

Update: listening to the new message with web interface clears it.