Trunk Setup not working in new Vodia Mini

[Dave Alvarado]

We were using some Planet VIP 480FD gateway for trunking with snom without any problems at all, in fact they still work today, but with the Vodia Mini the same configuration is not working, no inbound or outbound calls, any ideas?

[Vodia support]

What portion of the trunk is not working and could you post a SIP trace of the event?

[Dave Alvarado]

This messages are what we are getting regarding the trunk, also i tried to setup manually the phone IP addresses and register them to the pbx whiteout success, its not registering any phone, I have the license installed and everything.

The trunk Gateway is on 192.168.7.3

[9] 2000/01/01 02:33:39: Received JSON from 192.168.7.78

[8] 2000/01/01 02:33:44: Trunk 4: sending discover message for 192.168.7.3

[8] 2000/01/01 02:33:44: Trunk 4 (VIP480) is associated with the following addresses: udp:192.168.7.3:5060

[9] 2000/01/01 02:33:44: Received JSON from 192.168.7.78

[9] 2000/01/01 02:33:50: Last message repeated 2 times

[8] 2000/01/01 02:33:50: Trunk 4: sending discover message for 192.168.7.3

[8] 2000/01/01 02:33:50: Trunk 4 (VIP480) is associated with the following addresses: udp:192.168.7.3:5060

[9] 2000/01/01 02:33:50: Received JSON from 192.168.7.78

[9] 2000/01/01 02:34:24: Last message repeated 4 times

[6] 2000/01/01 02:34:24: Websocket

GET / HTTP/1.1
Upgrade: websocket
Connection: Upgrade
Host: 192.168.7.2
Origin: http://192.168.7.2
Cookie: acct_table#pageNavPos=1; ui_reg_gen=block; session=avevavva5texdvyy9plw
Pragma: no-cache
Cache-Control: no-cache
Sec-WebSocket-Key: 7FMdYOloph63gH1n/5Ft6Q==
Sec-WebSocket-Version: 13
Sec-WebSocket-Extensions: x-webkit-deflate-frame
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_7_5) AppleWebKit/537.75.14 (KHTML, like Gecko) Version/6.1.3 Safari/537.75.14

[5] 20:40:55.900 PACK: SIP Rx udp:192.168.7.10:32768: REGISTER sip:192.168.7.2 SIP/2.0
Via: SIP/2.0/UDP 192.168.7.10:32768;branch=z9hG4bK-436iray5wp2a;rport
From: <sip:100@192.168.7.2>;tag=m73a4zdrq5
To: <sip:100@192.168.7.2>
Call-ID: 386d43eb636c-60f3gzy4z92a
CSeq: 3 REGISTER
Max-Forwards: 70
Contact: <sip:100@192.168.7.10:32768;line=97dqwc5i>;reg-id=1;q=1.0;+sip.instance="<urn:uuid:e22035de-bfed-4727-82ca-000413741E70>";audio;mobility="fixed";duplex="full";description="snom710";actor="principal";events="dialog";methods="INVITE,ACK,CANCEL,BYE,REFER,OPTIONS,NOTIFY,SUBSCRIBE,PRACK,MESSAGE,INFO"
User-Agent: snom710/8.7.3.19
Allow-Events: dialog
X-Real-IP: 192.168.7.10
Supported: path, gruu
Expires: 3600
Content-Length: 0
[5] 20:40:55.916 PACK: SIP Tx udp:192.168.7.10:32768: SIP/2.0 404 Not Found
Via: SIP/2.0/UDP 192.168.7.10:32768;branch=z9hG4bK-436iray5wp2a;rport=32768
From: <sip:100@192.168.7.2>;tag=m73a4zdrq5
To: <sip:100@192.168.7.2>;tag=56395fda05
Call-ID: 386d43eb636c-60f3gzy4z92a
CSeq: 3 REGISTER
Content-Length: 0
[5] 20:40:59.080 PACK: SIP Rx udp:192.168.7.10:32768: REGISTER sip:192.168.7.2 SIP/2.0
Via: SIP/2.0/UDP 192.168.7.10:32768;branch=z9hG4bK-dti2pr4jjjol;rport
From: <sip:100@192.168.7.2>;tag=mxotntw2b8
To: <sip:100@192.168.7.2>
Call-ID: 386d43eb636c-60f3gzy4z92a
CSeq: 4 REGISTER
Max-Forwards: 70
Contact: <sip:100@192.168.7.10:32768;line=97dqwc5i>;reg-id=1;q=1.0;+sip.instance="<urn:uuid:e22035de-bfed-4727-82ca-000413741E70>";audio;mobility="fixed";duplex="full";description="snom710";actor="principal";events="dialog";methods="INVITE,ACK,CANCEL,BYE,REFER,OPTIONS,NOTIFY,SUBSCRIBE,PRACK,MESSAGE,INFO"
User-Agent: snom710/8.7.3.19
Allow-Events: dialog
X-Real-IP: 192.168.7.10
Supported: path, gruu
Expires: 3600
Content-Length: 0
[5] 20:40:59.093 PACK: SIP Tx udp:192.168.7.10:32768: SIP/2.0 404 Not Found
Via: SIP/2.0/UDP 192.168.7.10:32768;branch=z9hG4bK-dti2pr4jjjol;rport=32768
From: <sip:100@192.168.7.2>;tag=mxotntw2b8
To: <sip:100@192.168.7.2>;tag=56395fda05
Call-ID: 386d43eb636c-60f3gzy4z92a
CSeq: 4 REGISTER
Content-Length: 0
[4] 20:41:02.053 WEBS: Dictionary: Item dom_accounts.htm 4 not found [4] 20:42:23.023 WEBS: Last message repeated 4 times [4] 20:42:23.023 WEBS: Dictionary: Item dom_pstn_trunks.htm select1 not found

[Vodia PBX]

Well the SIP messages seem to be unrelated, but could it be that you don't have the name "localhost" in the domain alias list? You can also filter by IP address when setting up the log levels, so that yo use only the SIP packets from the gateway.

[Dave Alvarado]

The only message we get is this

 

[8] 2000/01/01 02:33:44: Trunk 4: sending discover message for 192.168.7.3

[8] 2000/01/01 02:33:44: Trunk 4 (VIP480) is associated with the following addresses: udp:192.168.7.3:5060

From the trunk , but when trying to make calls or receive calls nothing happens

[Vodia PBX]

For a gateway trunk, that is okay because there are no REGISTER messages being sent.

 

But for an outbound call, there should be a message going out to that IP address. You should be able to see that in the log.

 

For incoming calls you should see a message coming to the PBX. Double-check that the outbound proxy on the PSTN gateway is correct.

 

Also I would try to ping the gateway from the PBX (shell level) or ping the PBX from the gateway. Or at least try to ping them both from a client (e.g. PC) in the LAN. Maybe there is something wrong with the IP configuration, which can easily happen when you are using static IPv4 addresses. For example, if the netmask is incorrect, you may have such effects.

[Dave Alvarado]

what is the shell level user and password for the vodka mini?, also is there a way to reset it to factory settings?

[Vodia PBX]

The shell password is set when you set the admin password for the PBX (it copies the password into the Linux).

 

If you have a USB cable, you can still access the system (see http://elinux.org/Beagleboard:Terminal_Shells). I am not hte biggest expert on this, but there is plenty of information available.