NO SOUND when I call and

Hello
I new with asterisk…

I have: Softphone: 3CX and Provider:Voiptalk

Ring multiple channels simultaneously: The call is handled on a “first come, first served” basis; the first extension to pick up answers the call, and all the other extensions stop ringing and become
available: exten => s,1,Dial(SIP/2000&SIP/2001&SIP/2303))

  1. I try to call a mobil number with 2 sip simultaneously, when the number i call is answered i don’t have any sound.

  2. When i use: “exten => s,1,Dial(SIP/2000&SIP/2001&SIP/2303)” to make simultaneously dial,I thought only one sip is charged(“first come, first served”),when first sip pick up the call, the secound sip is stop calling. But no, both are charged. It is any mistake in my configuration, or I need to use another command ?

For exemple i my case i config the asterisk:

Sip.conf config:

[general]
register => 811280113:pass1@voiptalk.org/811280113
register => 811280112:pass1@voiptalk.org/811280112

[811280113]
type=friend
username=811280113
secret=pass1
fromuser=811280113
host=voiptalk.org
dtmfmode=rfc2833
fromdomain=voiptalk.org
context=default
insecure=very
allow=gsm

[811280112]
type=friend
username=811280112
secret=pass1
fromuser=811280112
host=voiptalk.org
dtmfmode=rfc2833
fromdomain=voiptalk.org
context=default
insecure=very
allow=gsm

[3cx] ; config for softphone 3cx
type=friend
username=3cx
callerid="811280113"
callerid="811280112"
host=dynamic
nat=yes
canreinvite=no
disallow=all
allow=gsm
allow=ulaw
allow=alaw

Extensions.conf config:

[default]
exten => _00[1-9].,1,Dial(SIP/811280113/${EXTEN}&SIP/811280112/${EXTEN})

For exemple i try to call my mobil number 00447927234555 :

  1. I put in 3cx number 00447927234555@voiptalk.org and I call.

  2. I answer the call(my mobile) and when i speak i my mobile…I don’t hear nothing in pc/3cx (no sound from mobile), and both sip are charged.

Thank you

The charging issue will relate to the ITSP’s policies. The PSTN policy equates to starting charging when the far end generates the equivalent of 200 OK. You cannot control that, except in as much as the calls should get cancelled once one answers.

If insecure=very is working, you are using an obsolete version of Asterisk, so knowing the version number may be important. (Also note that most cases of insecure=port,invite (the new form) should be insecure=invite.) This will cause problems with incoming calls.

A detailed explanation of what is wrong will require the SIP and SDP for all the calls.

Finally, this is the wrong forum for support questions.

Ok thanks,

My Asterisk : Connected to Asterisk 1.8.5.0 currently running on localhost (pid = 2640)
Verbosity is at least 3

I changed “insecure=very”, I put: insecure=port,invite…isn’t working, after i changed i put: insecure=invite …isn’t working.

[811280112]
type=friend
username=811280112
secret=pass1
fromuser=811280112
host=voiptalk.org
dtmfmode=rfc2833
fromdomain=voiptalk.org
context=default
insecure=port,invite
allow=gsm

I tried after to call with one sip a mobil number/landline and i received this massage:

Executing [00448706161166@default:1] Dial(“SIP/3CX-0000007f”, “SIP/811280112/00448706161166”) in new stack
== Using SIP RTP CoS mark 5
– Called SIP/811280112/00448706161166
– SIP/811280112-00000080 is making progress passing it to SIP/3CX-0000007f
– SIP/811280112-00000080 answered SIP/3CX-0000007f
– Locally bridging SIP/3CX-0000007f and SIP/811280112-00000080
[Jun 21 17:31:31] WARNING[2816]: chan_sip.c:3351 __sip_xmit: sip_xmit of 0x96fcc10 (len 836) to (null) returned -1: Invalid argument
[Jun 21 17:31:31] WARNING[2816]: chan_sip.c:3622 retrans_pkt: Retransmission timeout reached on transmission 0cb0b8b3121d469b4923440d2db834dd@127.0.0.1:5060 for seqno 102 ( Critical Request)
– See wiki.asterisk.org/wiki/display/ … nsmissions
Packet timed out after 31999ms with no response
== Spawn extension (default, 00448706161166, 1) exited non-zero on ‘SIP/3CX-0000007f’

Thanks…

As noted, wrong settings of insecure tend to cause problems for incoming calls, not outgoing ones.

This suggests a bug, but you will need full SIP channel debugging before you can report it. (core set debug 5 chan_sip and sip set debug on)

At a minimum, you need sip history to work out what this is. It is quite likely to be a consequence of the above problem, but could be the result of trying to issue a re-invite to something that has broken re-invite handling (neither handles nor rejects them).