search

paulhsu / csipsimple

Automatically exported from code.google.com/p/csipsimple
1 stars 1 forks source link

call between two csipsimple account #1992

Closed GoogleCodeExporter closed 9 years ago

GoogleCodeExporter commented 9 years ago 
Premise :
In my factory I have a telephone exchange(samsung officeserv 7100) with witch I 
use 4 samsung cellular phone (two galaxy S3, one galaxy Mini2 and one Galaxy 
Ace2) connected in the wifi network to talk away the office.(instead of the old 
dect cordless).

These are the problems that i found using csipsimple :
1.when I call with csipsimple a normal(phisical) phone I haven't any problem.
2.when a phone call me there aren't any problem.
3.when I call another cellular phone both with csipsimple I have the following 
cases:
A)The call is established and both account are in "on hold" and i can't resume 
the conversation.
B)The call isn't established and both account show "call terminated" and after 
go in the blue number screen(the screen for dial the number to call)

What version of the product are you using? On what operating system?
Csipsimple : 0.04-04 r1916
Android 2.3.6 on Galaxy mini2 and Galaxy Ace 2
Android 4.0.4 on galaxy S3

Please provide any additional information below:

The cellular phones work only in an internal network without internal NAT 
(there is a NAT on the firewall between internet and Lan
I tried the call with another SIP Client (Bria) and there wasn't problem;
the four cellular have the same codec actived.

This behavior is a bug ? or I didn't set properly some parameters ?

best regards 
Marco

Original issue reported on code.google.com by marco.lu...@gmail.com on 23 Sep 2012 at 9:07

GoogleCodeExporter commented 9 years ago 
Hi,

Probably something with configuration. I use same kind of topology at work.

Depending on how the sip server behaves regarding media (gateway or 
transparent), configuration may need to be different.

What could be helpful is to collect logs : 
http://code.google.com/p/csipsimple/wiki/HowToCollectLogs?wl=en
I think that I can find some clues on why it reach such state in logs.

Original comment by r3gis...@gmail.com on 23 Sep 2012 at 9:55