Page 1 of 1

VicidialNow 1.2 CE SIP Trunks issue

PostPosted: Tue Jun 16, 2009 6:27 pm
by ykhan
When I try to dial out using a SIP softphone, I get the following CLI output and call fails:

Code: Select all
    -- Executing AGI("SIP/cc100-097c4b40", "agi://127.0.0.1:4577/call_log") in new stack
    -- AGI Script agi://127.0.0.1:4577/call_log completed, returning 0
    -- Executing Dial("SIP/cc100-097c4b40", "/15554443333||To") in new stack
Jun 16 11:56:18 WARNING[22039]: channel.c:2621 ast_request: No channel type registered for ''
Jun 16 11:56:18 NOTICE[22039]: app_dial.c:1076 dial_exec_full: Unable to create channel of type '' (cause 66 - Channel not implemented)
  == Everyone is busy/congested at this time (1:0/0/1)
    -- Executing Hangup("SIP/cc100-097c4b40", "") in new stack
  == Spawn extension (default, 915554443333, 3) exited non-zero on 'SIP/cc100-097c4b40'
    -- Executing DeadAGI("SIP/cc100-097c4b40", "agi://127.0.0.1:4577/call_log--HVcauses--PRI-----NODEBUG-----66-----CHANUNAVAIL----------") in new stack
    -- AGI Script agi://127.0.0.1:4577/call_log--HVcauses--PRI-----NODEBUG-----66-----CHANUNAVAIL---------- completed, returning 0


CONFIGURATION IN VICIDIAL
Code: Select all
register => username:pwd@hostname:5060

[test-outbound] (exact format/casing required)
type=friend
host=hostname
context=default (ext-did or from-trunk for A@H)
username=username
fromuser=username
trustrpid=yes
sendrpid=yes
secret=pwd
allow=all
canreinvite=no

exten => _91.,1,AGI(agi://127.0.0.1:4577/call_log)
exten => _91.,2,Dial(SIP/${EXTEN:1}@test-outbound,,tTor)
exten => _91.,3,Hangup

PostPosted: Tue Jun 16, 2009 8:11 pm
by mflorell
try deleting the 91NXXNXXXXXX from extensions.conf reload in Asterisk and see what happens.

PostPosted: Wed Jun 17, 2009 6:52 am
by ykhan
That worked. Also commented out the toll free lines.

I did not see the DID config that I did in Vicidial screens in either the extensions.conf or in extensions-vicidial.conf. I can't get my inbound DID to work.

PostPosted: Wed Jun 17, 2009 12:10 pm
by mflorell
DIDs are handled in the AGI, not through the dialplan.

PostPosted: Wed Jun 17, 2009 12:16 pm
by ykhan
Ok, I have resolved it. I had to manually add another context in the sip.conf file for the inbound as provided by my sip provider. The context in that configuration needs to be set to trunkinbound and then the calls come through ok.

SIP Trunk issue

PostPosted: Thu Jun 18, 2009 1:21 am
by zeroche_rodriguez
Goodday sir,

Hope you can help us in solving this.
What seem to be the problem in my settings. Im using vicidialNOW 1.2
We have configure the Carrier.

[TRUNK SIP]
type=friend
host=xxx.xxx.xxx.xxx
canreinvite=no
disallow=all
allow=g729
dtmfmode=rfc2833
qualify=yes


DIAL PLAN ENTRY

exten => _91NXXNXXXXXX,1,AGI(agi://127.0.0.1:4577/call_log)
exten => _91NXXNXXXXXX,2,Dial(${SIPTRUNK1}/1972${EXTEN:1},55,o)
exten => _91NXXNXXXXXX,3,Hangup


Errors Encountered
Executing Dial("Local/8600051@default-61c2,1", "SIP/NOVATEL/1972180087253
87|55|o") in new stack
-- Called NOVATEL/197218008725387
Jun 18 10:14:31 WARNING[5200]: channel.c:2781 ast_channel_make_compatible: No pa
th to translate from SIP/NOVATEL-08418a60(256) to Local/8600051@default-61c2,1(6
4)
Jun 18 10:14:31 WARNING[5200]: chan_sip.c:2608 sip_write: Asked to transmit fram
e type 64, while native formats is 256 (read/write = 256/256)
Jun 18 10:14:31 WARNING[5200]: chan_sip.c:2608 sip_write: Asked to transmit fram
e type 64, while native formats is 256 (read/write = 256/256)
Jun 18 10:14:31 WARNING[5200]: chan_sip.c:2608 sip_write: Asked to transmit fram
e type 64, while native formats is 256 (read/write = 256/256)
Jun 18 10:14:31 WARNING[5200]: chan_sip.c:2608 sip_write: Asked to transmit fram
e type 64, while native formats is 256 (read/write = 256/256)
Jun 18 10:14:31 WARNING[5200]: chan_sip.c:2608 sip_write: Asked to transmit fram
e type 64, while native formats is 256 (read/write = 256/256)
Jun 18 10:14:31 WARNING[5200]: chan_sip.c:2608 sip_write: Asked to transmit fram
e type 64, while native formats is 256 (read/write = 256/256)
Jun 18 10:14:31 WARNING[5200]: chan_sip.c:2608 sip_write: Asked to transmit fram
e type 64, while native formats is 256 (read/write = 256/256)
Jun 18 10:14:31 WARNING[5200]: chan_sip.c:2608 sip_write: Asked to transmit fram
e type 64, while native formats is 256 (read/write = 256/256)
Jun 18 10:14:31 WARNING[5200]: chan_sip.c:2608 sip_write: Asked to transmit fram
e type 64, while native formats is 256 (read/write = 256/256)
Jun 18 10:14:31 WARNING[5200]: chan_sip.c:2608 sip_write: Asked to transmit fram
e type 64, while native formats is 256 (read/write = 256/256)
Jun 18 10:14:32 WARNING[5200]: chan_sip.c:2608 sip_write: Asked to transmit fram
e type 64, while native formats is 256 (read/write = 256/256)
Jun 18 10:14:32 WARNING[5200]: chan_sip.c:2608 sip_write: Asked to transmit fram
e type 64, while native formats is 256 (read/write = 256/256)
Jun 18 10:14:32 WARNING[5200]: chan_sip.c:2608 sip_write: Asked to transmit fram
e type 64, while native formats is 256 (read/write = 256/256)
Jun 18 10:14:32 WARNING[5200]: chan_sip.c:2608 sip_write: Asked to transmit fram
e type 64, while native formats is 256 (read/write = 256/256)
Jun 18 10:14:32 WARNING[5200]: chan_sip.c:2608 sip_write: Asked to transmit fram
e type 64, while native formats is 256 (read/write = 256/256)
Jun 18 10:14:32 WARNING[5200]: chan_sip.c:2608 sip_write: Asked to transmit fram
e type 64, while native formats is 256 (read/write = 256/256)
Jun 18 10:14:32 WARNING[5200]: chan_sip.c:2608 sip_write: Asked to transmit fram
e type 64, while native formats is 256 (read/write = 256/256)
Jun 18 10:14:32 WARNING[5200]: chan_sip.c:2608 sip_write: Asked to transmit fram
e type 64, while native formats is 256 (read/write = 256/256)
Jun 18 10:14:32 WARNING[5200]: chan_sip.c:2608 sip_write: Asked to transmit fram
e type 64, while native formats is 256 (read/write = 256/256)
Jun 18 10:14:32 WARNING[5200]: chan_sip.c:2608 sip_write: Asked to transmit fram
e type 64, while native formats is 256 (read/write = 256/256)
Jun 18 10:14:32 WARNING[5200]: chan_sip.c:2608 sip_write: Asked to transmit fram
e type 64, while native formats is 256 (read/write = 256/256)
Jun 18 10:14:32 WARNING[5200]: chan_sip.c:2608 sip_write: Asked to transmit fram
e type 64, while native formats is 256 (read/write = 256/256)
Jun 18 10:14:32 WARNING[5200]: chan_sip.c:2608 sip_write: Asked to transmit fram
e type 64, while native formats is 256 (read/write = 256/256)
Jun 18 10:14:32 WARNING[5200]: chan_sip.c:2608 sip_write: Asked to transmit fram
e type 64, while native formats is 256 (read/write = 256/256)
Jun 18 10:14:32 WARNING[5200]: chan_sip.c:2608 sip_write: Asked to transmit fram
e type 64, while native formats is 256 (read/write = 256/256)
Jun 18 10:14:32 WARNING[5200]: chan_sip.c:2608 sip_write: Asked to transmit fram
e type 64, while native formats is 256 (read/write = 256/256)
Jun 18 10:14:32 WARNING[5200]: chan_sip.c:2608 sip_write: Asked to transmit fram
e type 64, while native formats is 256 (read/write = 256/256)
== Parsing '/etc/asterisk/manager.conf': Found
== Manager 'sendcron' logged on from 127.0.0.1
-- Executing MeetMe("Local/58600051@default-256c,2", "8600051|Fmq") in new s
tack
> Channel Local/58600051@default-256c,1 was answered.
-- Executing Answer("Local/58600051@default-256c,1", "") in new stack
-- Executing Monitor("Local/58600051@default-256c,1", "wav|20090618-221431_8
008725387_INFOCITY_asun") in new stack
Jun 18 10:14:32 WARNING[5200]: chan_sip.c:2608 sip_write: Asked to transmit fram
e type 64, while native formats is 256 (read/write = 256/256)
-- Executing Wait("Local/58600051@default-256c,1", "3600") in new stack
Jun 18 10:14:32 WARNING[5200]: chan_sip.c:2608 sip_write: Asked to transmit fram
e type 64, while native formats is 256 (read/write = 256/256)
Jun 18 10:14:32 WARNING[5200]: chan_sip.c:2608 sip_write: Asked to transmit fram
e type 64, while native formats is 256 (read/write = 256/256)
Jun 18 10:14:32 WARNING[5200]: chan_sip.c:2608 sip_write: Asked to transmit fram
e type 64, while native formats is 256 (read/write = 256/256)
Jun 18 10:14:32 WARNING[5200]: chan_sip.c:2608 sip_write: Asked to transmit fram
e type 64, while native formats is 256 (read/write = 256/256)
Jun 18 10:14:32 WARNING[5200]: chan_sip.c:2608 sip_write: Asked to transmit fram
e type 64, while native formats is 256 (read/write = 256/256)
Jun 18 10:14:32 WARNING[5200]: chan_sip.c:2608 sip_write: Asked to transmit fram
e type 64, while native formats is 256 (read/write = 256/256)
Jun 18 10:14:32 WARNING[2803]: chan_sip.c:9890 handle_response_invite: Forbidden
- wrong password on authentication for INVITE to '"M0618101431000067502" <sip:0
000000000@202.57.46.210>;tag=as64fd356f'
-- SIP/NOVATEL-08418a60 is circuit-busy
== Everyone is busy/congested at this time (1:0/1/0)
-- Executing Hangup("Local/8600051@default-61c2,1", "") in new stack
== Spawn extension (default, 918008725387, 3) exited non-zero on 'Local/860005
1@default-61c2,1'
-- Executing DeadAGI("Local/8600051@default-61c2,1", "agi://127.0.0.1:4577/c
all_log--HVcauses--PRI-----NODEBUG-----21-----CONGESTION----------") in new stac
k
-- AGI Script agi://127.0.0.1:4577/call_log--HVcauses ... EBUG-----2
1-----CONGESTION---------- completed, returning 0
== Spawn extension (default, 8600051, 1) exited non-zero on 'Local/8600051@def
ault-61c2,2'
-- Executing DeadAGI("Local/8600051@default-61c2,2", "agi://127.0.0.1:4577/c
all_log--HVcauses--PRI-----NODEBUG-----0---------------") in new stack
-- AGI Script agi://127.0.0.1:4577/call_log--HVcauses ... EBUG-----0
--------------- completed, returning 0
== Manager 'sendcron' logged off from 127.0.0.1
== Manager 'sendcron' logged off from 127.0.0.1

PostPosted: Thu Jun 18, 2009 6:21 am
by mflorell
Did you buy a G729 license and install it on your system?

Have you tried ulaw instead?

VICIDIAL SIP Issue

PostPosted: Thu Jun 18, 2009 7:29 am
by zeroche_rodriguez
Sir,

Our provider authenticate the codec. We have try ulaw sir and we have a problem too. Thank you for the quick response.

PostPosted: Thu Jun 18, 2009 8:04 am
by ykhan
Are you using a softphone (Xlite)? Check your phones codecs, make sure you have ulaw selected. Try dialing directly from the phone. Try at least two numbers, one conference number like 8600051 and make sure you can hear the message. Also try a regular outbound number like the one in the CLI log.