Cisco Support Community
cancel
Showing results for 
Search instead for 
Did you mean: 
New Member

UC320W and Mediatrix 4404

Hello all,

We are doing our first UC320 install right now and are having serious difficulties!

The UC320 itself works fine and we can configure it to work with an analogue line. The client has 3 ISDN line they want to use with the system and we were told to get the Mediatrix 4404 by Cisco sales (and all the online Cisco marketing points to this).

We have followed the Cisco procedure sheet to get this setup but we can't get a functioning system.

https://supportforums.cisco.com/docs/DOC-14795  see attachment.

we get a solid tone when we try to dial in or out.

However, if we change the connection type from "point to multipoint" to "point to point" then we can make outgoing calls fine but not recieve any, same constant tone noise.

Cisco support have tried to get it working but can't and are blaming the Mediatrix 4404, we have tried to contact Media5 (mediatrix manufacturer) but they are very hard to get a hold of for support. You can get to their sales fine ok though!!!

Got a deadline of end of play tomorrow to get this working or the client is going elsewhere....not a good situation!

Anyone got any experience of this setup that can give me some assistance?

Many thanks, Paul.

15 REPLIES

UC320W and Mediatrix 4404

Hi Paul,

The Cisco docs say to use 'Point to Multipoint', not 'Point to Point'.  Also, make sure you configure the SIP Proxy Host port that aligns with the Local SIP port on the SIP/BRI page of the UC320W.

Chris

New Member

UC320W and Mediatrix 4404

Hi Chris,

Thanks for the reply!

We have been using point to multipoint but when things didn't work we started to experiment. The ports match up, 5060 on both devices.

Paul

UC320W and Mediatrix 4404

Are you up an working now or still having problems?  If you are still having problems, make sure you turn on SIP logs under Status -> Support Tools of the UC320W GUI as they might provide a clue.

New Member

UC320W and Mediatrix 4404

Hi Chris,

Yes still having problems. I've turned on the logs for "mediatrix" (the name we've given it under sip\bri trunks -- description).

now what? Nothing comes up in the system log box, how do get info in there?

Thanks

Paul

New Member

UC320W and Mediatrix 4404

I've rebooted the UC320 and tried calling in again, nothing is coming up in the logs, does this mean that the call is not getting as far as the UC320 and getting stuck at the mediatrix 4404?

Paul

New Member

UC320W and Mediatrix 4404

Ok, i'm getting info in the system log.

Where do I set the date\time? it's way out in the sys log.

an  2 07:50:22 UC320W syslog.info syslogd started: Busybox v1.00
Jan  2 07:50:22 UC320W user.notice kernel: klogd started: Busybox v1.00
Jan  2 07:50:42 UC320W user.debug voice: fs:ap:019538:019957:065536:058406167999

Jan  2 07:50:42 UC320W user.debug voice: PB:eecv = 0

Jan  2 07:50:42 UC320W user.debug voice: Merged config to /home/usb_disk/cfg/gateways/uc320w_000000000000.xml --> 0

Jan  2 07:50:42 UC320W user.debug voice: Firmware downgrade limit()

Jan  2 07:50:42 UC320W user.debug voice: fu:0:06b77, 03eb 0001

Jan  2 07:50:42 UC320W user.debug voice: SYS_init_after_ether(R128)

Jan  2 07:50:42 UC320W user.debug voice: get_dhcp_option66_67_info, voice interface is 'br0'

Jan  2 07:51:09 UC320W user.debug voice: fs:ap:019538:019957:065536:058406167999

Jan  2 07:51:09 UC320W user.debug voice: PB:eecv = 0

Jan  2 07:51:09 UC320W user.debug voice: Merged config to /home/usb_disk/cfg/gateways/uc320w_000000000000.xml --> 0

Jan  2 07:51:09 UC320W user.debug voice: Firmware downgrade limit()

Jan  2 07:51:09 UC320W user.debug voice: fu:0:06b8a, 1018 0001

Jan  2 07:51:09 UC320W user.debug voice: SYS_init_after_ether(R128)

Jan  2 07:51:09 UC320W user.debug voice: get_dhcp_option66_67_info, voice interface is 'br0'

Jan  2 07:51:21 UC320W user.debug voice: fs:ap:019538:019957:065536:058406167999

Jan  2 07:51:21 UC320W user.debug voice: PB:eecv = 0

Jan  2 07:51:21 UC320W user.debug voice: Merged config to /home/usb_disk/cfg/gateways/uc320w_000000000000.xml --> 0

Jan  2 07:51:21 UC320W user.debug voice: Firmware downgrade limit()

Jan  2 07:51:21 UC320W user.debug voice: fu:0:06b9d, 101e 0001

Jan  2 07:51:21 UC320W user.debug voice: SYS_init_after_ether(R128)

Jan  2 07:51:21 UC320W user.debug voice: get_dhcp_option66_67_info, voice interface is 'br0'

Jan  2 07:51:23 UC320W user.debug voice: CHECK: type = 0, idle_timer = 0, delayed_count = -1, clock = 1861926, flag = 0, event = 4

Jan  2 07:51:42 UC320W user.debug kernel: sysevt_comm_sendto: (60, rc)=>
Jan  2 07:51:44 UC320W user.debug kernel: sysevt_comm_sendto: (60, rc)=>
Jan  2 07:51:45 UC320W user.debug kernel: sysevt_comm_sendto: (60, rc)=>
Jan  2 07:51:45 UC320W user.debug kernel: sysevt_comm_sendto: (60, rc)=>
Jan  2 07:51:48 UC320W user.debug voice: fs:ap:019538:019957:065536:058406167999

Jan  2 07:51:48 UC320W user.debug voice: PB:eecv = 0

Jan  2 07:51:48 UC320W user.debug voice: Merged config to /home/usb_disk/cfg/gateways/uc320w_000000000000.xml --> 0

Jan  2 07:51:48 UC320W user.debug voice: Firmware downgrade limit()

Jan  2 07:51:48 UC320W user.debug voice: fu:0:06bb0, 1024 0001

Jan  2 07:51:48 UC320W user.debug voice: SYS_init_after_ether(R128)

Jan  2 07:51:48 UC320W user.debug voice: get_dhcp_option66_67_info, voice interface is 'br0'

Jan  2 07:51:50 UC320W user.debug kernel: sysevt_comm_sendto: (60, rc)=>
Jan  2 07:51:51 UC320W user.debug kernel: sysevt_comm_sendto: (60, rc)=>
Jan  2 07:51:51 UC320W user.debug kernel: sysevt_comm_sendto: (60, rc)=>
Jan  2 07:51:54 UC320W user.debug voice: fs:ap:019538:019957:065536:058406167999

Jan  2 07:51:54 UC320W user.debug voice: PB:eecv = 0

Jan  2 07:51:54 UC320W user.debug voice: Merged config to /home/usb_disk/cfg/gateways/uc320w_000000000000.xml --> 0

Jan  2 07:51:54 UC320W user.debug voice: Firmware downgrade limit()

Jan  2 07:51:54 UC320W user.debug voice: fu:0:06bc3, 102a 0001

Jan  2 07:51:54 UC320W user.debug voice: SYS_init_after_ether(R128)

Jan  2 07:51:54 UC320W user.debug voice: get_dhcp_option66_67_info, voice interface is 'br0'

Jan  2 07:51:54 UC320W user.debug voice: [9]RegOK. NextReg in 118 (1)

Jan  2 07:52:00 UC320W user.debug voice: fs:ap:019538:019957:065536:058406167999

Jan  2 07:52:00 UC320W user.debug voice: PB:eecv = 0

Jan  2 07:52:00 UC320W user.debug voice: Merged config to /home/usb_disk/cfg/gateways/uc320w_000000000000.xml --> 0

Jan  2 07:52:00 UC320W user.debug voice: Firmware downgrade limit()

Jan  2 07:52:01 UC320W user.debug voice: fu:0:06bd6, 03eb 0001

Jan  2 07:52:01 UC320W user.debug voice: SYS_init_after_ether(R128)

Jan  2 07:52:01 UC320W user.debug voice: get_dhcp_option66_67_info, voice interface is 'br0'

Jan  2 07:53:48 UC320W user.debug kernel: sysevt_comm_sendto: (60, rc)=>
Jan  2 07:53:50 UC320W user.debug kernel: sysevt_comm_sendto: (60, rc)=>
Jan  2 07:53:50 UC320W user.debug kernel: sysevt_comm_sendto: (60, rc)=>
Jan  2 07:53:51 UC320W user.debug voice: [9]RegOK. NextReg in 118 (1)

Jan  2 07:53:51 UC320W user.debug kernel: sysevt_comm_sendto: (60, rc)=>
Jan  2 07:53:53 UC320W user.debug kernel: sysevt_comm_sendto: (60, rc)=>
Jan  2 07:53:55 UC320W user.debug kernel: sysevt_comm_sendto: (60, rc)=>
Jan  2 07:53:56 UC320W user.debug kernel: sysevt_comm_sendto: (60, rc)=>
Jan  2 07:55:49 UC320W user.debug voice: [9]RegOK. NextReg in 118 (1)

Jan  2 07:55:55 UC320W user.debug kernel: sysevt_comm_sendto: (60, rc)=>
Jan  2 07:55:55 UC320W user.debug kernel: sysevt_comm_sendto: (60, rc)=>
Jan  2 07:55:57 UC320W user.debug kernel: sysevt_comm_sendto: (60, rc)=>
Jan  2 07:55:57 UC320W user.debug kernel: sysevt_comm_sendto: (60, rc)=>
Jan  2 07:55:58 UC320W user.debug kernel: sysevt_comm_sendto: (60, rc)=>
Jan  2 07:55:58 UC320W user.debug kernel: sysevt_comm_sendto: (60, rc)=>
Jan  2 07:55:59 UC320W user.debug kernel: sysevt_comm_sendto: (60, rc)=>
Jan  2 07:56:10 UC320W user.debug voice: fs:ap:019538:019957:065536:058406167999

Jan  2 07:56:10 UC320W user.debug voice: PB:eecv = 0

Jan  2 07:56:10 UC320W user.debug voice: Merged config to /home/usb_disk/cfg/gateways/uc320w_000000000000.xml --> 0

Jan  2 07:56:10 UC320W user.debug voice: Firmware downgrade limit()

Jan  2 07:56:10 UC320W user.debug voice: SYS_init_after_ether(R128)

Jan  2 07:56:10 UC320W user.debug voice: get_dhcp_option66_67_info, voice interface is 'br0'

Jan  2 07:56:17 UC320W user.debug voice: fs:ap:019538:019957:065536:058406167999

Jan  2 07:56:17 UC320W user.debug voice: PB:eecv = 0

Jan  2 07:56:17 UC320W user.debug voice: Merged config to /home/usb_disk/cfg/gateways/uc320w_000000000000.xml --> 0

Jan  2 07:56:17 UC320W user.debug voice: Firmware downgrade limit()

Jan  2 07:56:17 UC320W user.debug voice: fu:0:06bfc, 1024 0001

Jan  2 07:56:17 UC320W user.debug voice: SYS_init_after_ether(R128)

Jan  2 07:56:17 UC320W user.debug voice: get_dhcp_option66_67_info, voice interface is 'br0'

Jan  2 07:56:20 UC320W user.debug voice: CHECK: type = 0, idle_timer = 61, delayed_count = -1, clock = 1891926, flag = 0, event = 4

Jan  2 07:56:21 UC320W user.debug voice: fs:ap:019538:019957:065536:058406167999

Jan  2 07:56:22 UC320W user.debug voice: PB:eecv = 0

Jan  2 07:56:22 UC320W user.debug voice: Merged config to /home/usb_disk/cfg/gateways/uc320w_000000000000.xml --> 0

Jan  2 07:56:22 UC320W user.debug voice: Firmware downgrade limit()

Jan  2 07:56:22 UC320W user.debug voice: SYS_init_after_ether(R128)

Jan  2 07:56:22 UC320W user.debug voice: get_dhcp_option66_67_info, voice interface is 'br0'

Jan  2 07:57:06 UC320W user.debug voice: File path='/home/usb_disk/cdr/voicecdr.01012000-00-05-35.xml'

Jan  2 07:57:06 UC320W user.debug voice: File complete

Jan  2 07:57:22 UC320W user.debug voice: fs:ap:019538:019957:065536:058406167999

Jan  2 07:57:22 UC320W user.debug voice: PB:eecv = 0

Jan  2 07:57:22 UC320W user.debug voice: Merged config to /home/usb_disk/cfg/gateways/uc320w_000000000000.xml --> 0

Jan  2 07:57:22 UC320W user.debug voice: Firmware downgrade limit()

Jan  2 07:57:44 UC320W user.debug voice: [9]RegOK. NextReg in 118 (1)

Jan  2 07:57:56 UC320W user.debug kernel: sysevt_comm_sendto: (60, rc)=>
Jan  2 07:57:57 UC320W user.debug kernel: sysevt_comm_sendto: (60, rc)=>
Jan  2 07:57:59 UC320W user.debug kernel: sysevt_comm_sendto: (60, rc)=>
Jan  2 07:58:01 UC320W user.debug kernel: sysevt_comm_sendto: (60, rc)=>
Jan  2 07:58:02 UC320W user.debug kernel: sysevt_comm_sendto: (60, rc)=>
Jan  2 07:58:02 UC320W user.debug kernel: sysevt_comm_sendto: (60, rc)=>
Jan  2 07:58:04 UC320W user.debug kernel: sysevt_comm_sendto: (60, rc)=>

UC320W and Mediatrix 4404

Hi Paul,

The time is set by connecting to a Cloud based NTP server.  You need to have WAN access to the internet.  After a reboot of the device it is OK for the time to be off for a minute while the system initializes then will update clocks on the phones.  Check to make sure SIP logs (Mediatrix in your case) is enabled after the restart.  You should see SIP logs only when you make calls.  Start with making a call from the UC320 to PSTN and you should see those logs appear.

Chris

New Member

UC320W and Mediatrix 4404

Hi Chris,

Tony here, I am helping Paul and thought I would update this question.  To clarify what is happening.  When we configure the point to multipoint the lines are dead for outgoing and you get an error on the line if you try to call any of the DDI numbers.  When we changed it to point to point we could make outgoing calls, but incoming calls got a constant tone instead of a ringing phone.

I will check the logs that Paul gets when I am next in the office.

Thanks, Tony

Cisco Employee

UC320W and Mediatrix 4404

Dear Paul, Tony;

I thought I replied to this already. Lets start the troubleshooting by checking step by step configuration:

- Are UC320 WAN and Mediatrix 4404 IP address on the same subnet? (I assume yes because at some point you get calls coming in)

- How is the ISDN line (PHYSICAL) status on the Mediatrix? (Please check the status on the ISDN menu bar. Under normal conditions Link should be UP and channels idle. If the link is not up then check physical connectivity and configuration.

- If the ISDN line is UP then we need to look at the logs on both machines when placing calls:

* Place an outbound call and save the UC320W syslog AND the Mediatrix 4404 syslog as well.

* Place an inbound call and save both configurations as well.

The system should work when following the configuration so would like to make sure there is no configuration issues.

Regards;

Alberto

New Member

UC320W and Mediatrix 4404

Hello Alberto,

I now have the network exactly reflecting the diagram in the Cisco document.  So we have:

Router     192.168.75.1

UC320W     192.168.75.100 (WAN), 192.186.20.1 (LAN)

Mediatrix     192.168.75.101

With the Bri configured as "Point to Point" the link and signalling is up and the channels are idle.

I don't know how to save the syslog on the mediatrix, but I will update the call in a bit with the log file from the UC320W.

Thank you,

Tony

New Member

UC320W and Mediatrix 4404

Time ran out on this one and we lost the client.

I think that there is a fundamental flaw in the Mediatrix ISDN gateway and the UC320. It's not a solution I would recommend.

Cisco won't support the mediatrix box and were out of ideas, getting assistance from Media5 in painfully slow.

I wouldn't recommend the use of the Mediatrix box unless you have lots of time to get it working in a test environment first.

Cisco Employee

UC320W and Mediatrix 4404

Hi Paul;

I am very sorry this happened. I will contact you via email first (phone after if possible) to understand what went wrong. This is the first time this happens so definitively we will take action for this not to happen again, even on first installation, where I understand, you may not have all the practice on setting up the system.

As a side note, I would like to understand whether it is still possible to troubleshoot this issue, I just would like to understand what the technical issue is/was.

Regards;

Alberto

New Member

UC320W and Mediatrix 4404

Hello,

This email is more for anyone reading this forum thread rather than Alberto as he is now aware of the issue.  The documentation we were using from https://supportforums.cisco.com/docs/DOC-14795 was an old revision that misses out the step to configure the incoming calls route.  The newer version was on the cisco.com site and did include the step allthough it was still for the older version of the firmware.

Cisco are removing the incorrect copy from the support site and I beleive are working on an updated document for the firmware version 2.0.

Thank you,

Tony

New Member

Re: UC320W and Mediatrix 4404

SOLVED

Hi,

I'm also unable to make one of these work - following the corrected document.

It mentions Point to Multipoint (In-dial in Australia is generally Point to Point) selecting this enables layer 1 & 2

That all being said I cannot get the UC320 to register to the 4404. I can ping it fine the IP and port of the UC are entered correctly and the IP of the 4404 has been entered.

--- ** Update the Mediatrix DOESNT stay registered according to Cisco --- **

The firmware on the 4404 appears to be version dgw 2.0.15.260  yet the website only has version 1.1.13.186

However I'm still not able to make calls - the phone shows "Internal Server Error" - unplugging the ISDN then says service unavailable

The solution was two part - the ISDN service MUST be changed to Point to Multipoint and channels set to 2

https://supportforums.cisco.com/message/3474250#3474250

Cisco Employee

Re: UC320W and Mediatrix 4404

Thanks Tim;

To all, please note we have posted an appendix for covering configuration for Telstra Australia (additional settings)

https://supportforums.cisco.com/docs/DOC-21838

We are also working to include additional countries on this page

https://supportforums.cisco.com/docs/DOC-15130

Regards;
Alberto

2901
Views
0
Helpful
15
Replies
CreatePlease to create content