ViciboxServer installation - Call unable to tranfer to agent

[edolesky]

I have installed the Vicibox-Server Distro. I am using IAX trunking for testing purposes and I can place calls.

When I log in as an Agent, my softphone (zoiper) rings. I can initiate the call from the agent console and it goes out over the network. The call rings and is answered but does not get transferred to the agent. The message in the CLI is Channel 'IAX2/jnctncarrier-10398' unable to transfer [See below]

== Manager 'sendcron' logged on from 127.0.0.1
-- Executing MeetMe("Local/8600051@default-e79a,2", "8600051|F") in new stack
> Channel Local/8600051@default-e79a,1 was answered.
-- Executing AGI("Local/8600051@default-e79a,1", "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("Local/8600051@default-e79a,1", "IAX2/jnctncarrier/12155551212") in new stack
-- Called jnctncarrier/12155551212
-- Call accepted by 66.227.100.30 (format ulaw)
-- Format for call is ulaw
-- IAX2/jnctncarrier-10398 is making progress passing it to Local/8600051@default-e79a,1
== Manager 'sendcron' logged off from 127.0.0.1
-- IAX2/jnctncarrier-10398 answered Local/8600051@default-e79a,1
-- Channel 'IAX2/jnctncarrier-10398' unable to transfer
[vicibox1*CLI>


Additionally, when I logout from the agent screen, it does not disconnect my softphone. If I then hangup on my softphone, The following message is displayed in the CLI -> WARNING[4708]: chan_iax2.c:1895 attempt_transmit: Max retries exceeded to host 142.192.176.133 on IAX2/cc300-8363 (type = 6, subclass = 2, ts=1840008, seqno=20)

Seems to me that even though Vici Dials my softphone it does not know where to transfer the call and also cannot find it to hangup on the softphone. I can't quite figure out where in the configs this is controlled.

Any help is appreciated

[mflorell]

I think it might be trying to do a native bridge. Have you tried adding a 'to' flag to your Dial line?

[edolesky]

I tried the TO command , It did not make a difference.

I thought I would simplify my testing. I decided to just login as an agent, answer the extension when it rings and then wait for a few moments and logout. I wanted to see if the softphone would automatically be disconnected. It was not. It stayed connected to Vici.....

I found 3 entries in the vicidial-manger table.

man_id |uniqueid | entry_date | status |response | server_ip | channel |action | callerid |cmd_line_b |cmd_line_c |cmd_line_d | cmd_line_e | cmd_line_f
-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
107 |1247509421.0 |2009-07-13 14:23:41 |UPDATED | N | 142.192.176.168 |IAX2/cc300-5095 |Originate | S0907131423418600051 | Channel: IAX2/cc300 |Context: default |Exten: 8600051 | Priority: 1 | Callerid: "S0907131423418600051" <0000000000>
108 | |2009-07-13 14:24:29 |SENT | N | 142.192.176.168 | |Hangup | ULGH34591247509469 | Channel: IAX2/cc300-5095 | | | |
109 | |2009-07-13 14:24:29 |SENT | N | 142.192.176.168 | |Originate | ULGH34581247509469 | Channel: Local/55558600051@default|Context: default |Exten: 8300 | Priority: 1 | Callerid: ULGH34581247509469

Any clues here?

[mflorell]

What does a ping look like between the machine with Zoiper on it and your Vicidial Server?

[edolesky]

Connectivity seems fine. Here are my outputs.

Zoiper to ViciDial

Pinging 142.192.176.168 with 32 bytes of data:
Reply from 142.192.176.168: bytes=32 time<1ms TTL=64
Reply from 142.192.176.168: bytes=32 time<1ms TTL=64
Reply from 142.192.176.168: bytes=32 time<1ms TTL=64
Reply from 142.192.176.168: bytes=32 time<1ms TTL=64
Ping statistics for 142.192.176.168:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 0ms, Maximum = 0ms, Average = 0ms

tracert 142.192.176.168
Tracing route to 142.192.176.168 over a maximum of 30 hops
1 <1 ms <1 ms <1 ms 142.192.176.168
Trace complete.

Vici to Zoiper

root@vicibox1:~# ping 142.192.176.133
PING 142.192.176.133 (142.192.176.133) 56(84) bytes of data.
64 bytes from 142.192.176.133: icmp_seq=1 ttl=128 time=0.262 ms
64 bytes from 142.192.176.133: icmp_seq=2 ttl=128 time=0.379 ms
64 bytes from 142.192.176.133: icmp_seq=3 ttl=128 time=0.380 ms

--- 142.192.176.133 ping statistics ---
3 packets transmitted, 3 received, 0% packet loss, time 1999ms
rtt min/avg/max/mdev = 0.262/0.340/0.380/0.057 ms

root@vicibox1:~# traceroute 142.192.176.133
traceroute to 142.192.176.133 (142.192.176.133), 30 hops max, 40 byte packets
1 eoleskynotebook.trc.local (142.192.176.133) 0.260 ms 0.270 ms 0.321 ms

[mflorell]

Not sure what to suggest at this point, we use Zoiper and ViciDial a lot on local networks without these issues.

Is there any kind of firewall on either of these machines?

What kind of network switches are you using?

[edolesky]

No firewalls are involved with this traffic and HP Switches.
Do you believe it to be a connectivity issue.

Zoiper connects to VICI fine. I can place a manual call and both parites can talk just fine.

Can explain to me how VICI attempts to hangup zoiper when an agent presses logout? Perhaps that would get me pointed in the right direction.

[mflorell]

Upon logout ViciDial will tell Asterisk to kickall from the meetme room.