SearchSearch  Log in to check your private messagesLog in to check your private messages  recent posts Recent Posts
Post new topic   Reply to topic
View previous topic Printable version Log in to check your private messages View next topic
Author Message
PhiebsOffline



Joined: Apr 24, 2005
Posts: 4

Status: Offline
Posted: Apr 17, 2009 - 07:05 AM Reply with quote Back to top
Hello,

First off I am not a novice to either VOIP, DECT, SIP, phone systems, computer systems bla bla bla...

With that out of the way I have a very strange problem:

Few weeks ago I bought a set of S685's with 3 handsets. I have 2 older DECT handsets from a previous set-up all on the same base-station.

All was working 100% fine using VOIP and POTS, configured nicely and generally perfect.

There was a few storms last week and some close lightning strikes near the house, however no power failures or anything (this might or might not be related).

Went to dial out (using VOIP) and nothing happened, but when I contacted the 3rd party via my mobile, they said their phone rang but was no response (from me).

I figured that a reboot should do it, so I reset (power cycle) the base and all of the phones. Still nothing.

I know my way around the web UI pretty well so decided to do a factory reset. Still the same problem.

This is where is starts to get a little bit strange: just for laughs, I decided to try one of the old DECT handsets, and it worked flawlessly! I went back to the new Siemens handsets and none of them were working.

So in summary:

ALL phones are working for both in and out on POTS
Siemens phones are NOT working for VOIP (in OR out)
Old DECT phones ARE working for VOIP

So the only thing I can think of is that there is a part of the Siemens system which detects the "new" phones and attempts to use a higher quality voice channel, and for some reason it is not working.

Has anyone else had any issues like this/heard of this? Or is it simply time for me to contact Siemens/place I bought them for a replacement?

Many thanks in advance.
View user's profile Send private message
NisiOffline



Joined: Apr 19, 2009
Posts: 2

Status: Offline
Posted: Apr 19, 2009 - 09:40 AM Reply with quote Back to top
Hey Phiebs and all the others here,

My Name is Nisi and i have exact the same problem as phiebs! till a few days ago my gigaset A580IP worked how it should with Voip.. But since yesterday i only can call with the fix line.. if i try to call with voip to someone or for testing to my own mobile number it goes through so my mobile is ringing BUT i cant hear nothing and the other party also cant hear nothing.

PLease help us out guys, i'm a starter in the Voip society so realy need your help.

I tried everything, frome resseting base and handset to resetting voipacount. I tried updating but i already have the latest firmware... i have no idea what the next step is.

Thanx,

Nisi
View user's profile Send private message
NisiOffline



Joined: Apr 19, 2009
Posts: 2

Status: Offline
Posted: Apr 19, 2009 - 10:16 AM Reply with quote Back to top
Phiebs :
Hello,

First off I am not a novice to either VOIP, DECT, SIP, phone systems, computer systems bla bla bla...

With that out of the way I have a very strange problem:

Few weeks ago I bought a set of S685's with 3 handsets. I have 2 older DECT handsets from a previous set-up all on the same base-station.

All was working 100% fine using VOIP and POTS, configured nicely and generally perfect.

There was a few storms last week and some close lightning strikes near the house, however no power failures or anything (this might or might not be related).

Went to dial out (using VOIP) and nothing happened, but when I contacted the 3rd party via my mobile, they said their phone rang but was no response (from me).

I figured that a reboot should do it, so I reset (power cycle) the base and all of the phones. Still nothing.

I know my way around the web UI pretty well so decided to do a factory reset. Still the same problem.

This is where is starts to get a little bit strange: just for laughs, I decided to try one of the old DECT handsets, and it worked flawlessly! I went back to the new Siemens handsets and none of them were working.

So in summary:

ALL phones are working for both in and out on POTS
Siemens phones are NOT working for VOIP (in OR out)
Old DECT phones ARE working for VOIP

So the only thing I can think of is that there is a part of the Siemens system which detects the "new" phones and attempts to use a higher quality voice channel, and for some reason it is not working.

Has anyone else had any issues like this/heard of this? Or is it simply time for me to contact Siemens/place I bought them for a replacement?

Many thanks in advance.


Hey Phiebs,

I just managed to fix the problem..! i had the same problem as you did like i said before!

Solution ( for me )

Went to the web configurator of the gigaset base!

From there on log in with you pincode -> Settings -> Telephony -> Audio -> And play around with the codecs, i set mine on "optimized for low bandwidth" (becouse i'm using 5 devices with one bandwidh Razz )

These settings fixed it for me so try it out! Smile

Good Luck,

Nisi
View user's profile Send private message
dibsmftOffline
Site Admin


Joined: Oct 21, 2005
Posts: 3059
Location: St. John's, Newfoundland and Labrador, Canada
Status: Offline
Posted: Apr 19, 2009 - 11:52 AM Reply with quote Back to top
Nisi

Good for you!

Phiebs

Lets us know if the same procedure works for you.

Also, have you checked the compatibility list:

http://gigaset.com/shc/0,1935,hq_en_0_1 ... rN,00.html
View user's profile Send private message
janfondseOffline



Joined: May 11, 2006
Posts: 6

Status: Offline
Posted: Apr 19, 2009 - 03:33 PM Reply with quote Back to top
I have the same problem with a siemens a580ip duo set when calling through voipcheap.com. When I dial a number I don´t hear the phone ringing, although the phone on the other side does ring. Although I´m not sure I think this was introduced with the new firmware that siemens released. When I use my targa dip 450 phone (=siemens c450ip) everything works ok.

Looks like siemens needs to release a new firmware version quickly!

update: Nisi's post made me look into the codec selection a bit further. The problem seems to be g.722 codec. When you remove this codec from the selection everything works fine.

What's happening to Phieb's actually makes sense: the old dect handsets cannot use the g.722 codec. If you have a hd handset and have the g.722 codec listed first it will try to use the g.722 codec and that's where things get pearshaped. When using the old dect handset it will skip the g.722 codec from your list.
View user's profile Send private message
janfondseOffline



Joined: May 11, 2006
Posts: 6

Status: Offline
Posted: Apr 20, 2009 - 12:09 PM Reply with quote Back to top
@ Phiebs & Nisi:

Which provider do you use for you voip calls? I was wondering if we're using the same provider and that might be part of the cause as well.

I'm using voipcheap.com, a betamax clone like voipbuster, justvoip etc.


cheers,

Jan
View user's profile Send private message
sqlsieOffline



Joined: Apr 20, 2009
Posts: 1

Status: Offline
Posted: Apr 20, 2009 - 05:10 PM Reply with quote Back to top
All,

I have been pulling my hair out for days on this. I've got a s685ip and since upgrading the firmware (apr 09) lost all outgoing audio through my poivy (betamax) account. Poivy gave the usual response of check firewall etc.....

After resetting router and s685ip base unit i resorted to a proxy solution to poivy through voxalot with some success.

Came across your posts and removed the G277 codec from the profile. All is now back to normal Smile

Seems like Seimens should do a little more testing prior to a "forced" firmware upgrade.

With no ability to revert to the previous version and no bugs listed from Seimens Gigaset site it would appear to be a massive shortfall / mess up.

Thanks for the solution here - it has at least got to the bottom of the problem & i can now put a logical close to the issue even though i had a temporary work around.

Let's hope Seimens bring out a fix shortly - although i will be far more cautious to apply next time


Many Thanks

James
View user's profile Send private message
janfondseOffline



Joined: May 11, 2006
Posts: 6

Status: Offline
Posted: Apr 20, 2009 - 05:53 PM Reply with quote Back to top
well, I´m not really sure the problem is caused by the siemens firmware. I´ve checked my calling history with voipcheap.com and on the 10th i made some successfull calls. The firmwareupdate was done on 7 april. (i know becaused I saved the firmware to disk as well.)

On a different forum I read that it was possible to make calls through other providers though, like sipgate. So it could very well be that betamax has messed things up with g.722.

Btw, betamax has it's own forum. It's located at forum.voipbuster.com (i've posted my findings on it, but no reactions as yet.)

Cheers,

Jan
View user's profile Send private message
PhiebsOffline



Joined: Apr 24, 2005
Posts: 4

Status: Offline
Posted: Apr 22, 2009 - 07:00 AM Reply with quote Back to top
Wow, I am amazed that there are others with the same problem as me! I am indeed using voipstunt.com (part of voipbuster etc)... I am at work at the moment but will try out modifying the allowed codecs. I did have a play around with these before but must admit, I didn't really research it and was only fiddling.

This also happened to me about a week after the latest firmware update, is it possible that they have changed default codecs or something?

Quote:
What's happening to Phieb's actually makes sense: the old dect handsets cannot use the g.722 codec. If you have a hd handset and have the g.722 codec listed first it will try to use the g.722 codec and that's where things get pearshaped. When using the old dect handset it will skip the g.722 codec from your list.


This is a very very possible solution/cause... thank you Nisi and Janfondse for helping me figure out what is causing this strange behaviour!

I will post my results later on...
View user's profile Send private message
janfondseOffline



Joined: May 11, 2006
Posts: 6

Status: Offline
Posted: Apr 22, 2009 - 12:16 PM Reply with quote Back to top
update 22-04-2009:

betamax has fixed this issue and you no longer have to have the g.722 codec removed from your codec list
View user's profile Send private message
PhiebsOffline



Joined: Apr 24, 2005
Posts: 4

Status: Offline
Posted: Apr 22, 2009 - 01:34 PM Reply with quote Back to top
janfondse :
update 22-04-2009:

betamax has fixed this issue and you no longer have to have the g.722 codec removed from your codec list


Thats amazing news! Many thanks for all of your help guys. Will have a play around tonight when I get home and feedback the results onto here.
View user's profile Send private message
BlueMaxOffline



Joined: Jun 08, 2009
Posts: 12
Location: Goring
Status: Offline
Posted: Jun 24, 2009 - 06:52 PM Reply with quote Back to top
Quite a few Giagaset users here Smile
Rather expensive for a phone but nice piece of kit Smile

Mine is a Siemens Gigaset S685IP that I bought couple of weeks ago. VoIP service provider is localphone.com
Adding details in the handset did not work. But all was well after going to Siemens web configuration page that allowed me to add more details than possible in the handset.

Few days ago, I added two more providers including VoIP User. Status of all three is shown as 'registerd'

The page 'VoIP User Outbound Service for BlueMax' show
'You are online with a S685IP021840000000 device or phone at xx.xx.xx.xxx and you are not behind NAT'.

I disabled the other two providers in the web interface. But I cant make any calls. I noticed that details in the hand set has not changed. It stayed the same as for localphone.

Does anyone know what to do?
Thanks
View user's profile Send private message
BlueMaxOffline



Joined: Jun 08, 2009
Posts: 12
Location: Goring
Status: Offline
Posted: Jun 24, 2009 - 11:54 PM Reply with quote Back to top
Oh! forgot to say...
I have set up a VoIP User account in X-Lite and can make calls.
But not too practical with built in mic and speaker of my laptop.
View user's profile Send private message
BlueMaxOffline



Joined: Jun 08, 2009
Posts: 12
Location: Goring
Status: Offline
Posted: Jul 02, 2009 - 01:40 PM Reply with quote Back to top
Solved the problem Smile
In the Web Interface went to
Settings > Telephony > Connections > Number Assignment and under ' Connections for outgoing calls', selected 'VoIP User'.
View user's profile Send private message


View previous topic Printable version Log in to check your private messages View next topic

Post new topic   Reply to topic
Forum Rules and Guidelines | About VoIP User | Privacy Policy


All logos and trademarks in this site are property of their respective owner.
Comments and posts are property of the poster, all the rest (c) 2003-2008 VoIP User Limited.

VoIP User Limited is incorporated in England and Wales under Company Number 6694577.

No part of this site may be reproduced without our prior consent.