mipt310 with Motorola Controller (no SVP) problem
Posted: 31 Mar 2009 03:52
Topic closed.
Hi guys,
I'm installing my first mipt system on Motorola WS5100 AP system (OXE 9.0 h1.301.24.none; mipt version: 119.045 120.013 121.005) . The issue I'm facing is that my mipt registers ok to the system (I can see the number, time/date from the system ok), but when trying to call other device or even trying to access the menu (or calling inbound) returns "Net busy <AP MAC addr>". (maintenance description of error: Handset cannot obtain sufficient bandwidth to support a call; displays MAC of failing AP --->resolution: Try the call again later.
)
Tryed with compression (G.729 ) and without (G.711) no joy. Domain configured ok, multi algorithms in system, etc.
Played with UDP param (lost, reinit and keep alive) --- used the ones recommended in doc and on forum (+other values).
Played with reset for update yes/no still no joy.
I even reproduced the issue back home in my lab on a Linksys WRT54GL with WMM support from DD-WRT firmware -- and played with all sorts of parameters that Linksys has, but I just don't seem to find a way to clear it. In the lab (on Linksys mobile SJ phone -- sip end point and my pocket communicator work both well).
When using WMM it the ping of the mipt is very high (and loss occurs) - on both Linksys and Motorola
Ping from CS to mipt:
PING 192.168.0.125 (192.168.0.125): 56 octets data
64 octets from 192.168.0.125: icmp_seq=0 ttl=255 time=526.9 ms
64 octets from 192.168.0.125: icmp_seq=1 ttl=255 time=1063.9 ms
wrong data byte #0 should be 0x9e but was 0x9d9d 2b bf 49 16 c a 0
8 9 a b c d e f 10 11 12 13 14 15 16 17 18 19 1a 1b 1c 1d 1e 1f 20 21 22
23 24 25 26 27
28 29 2a 2b 2c 2d 2e 2f
64 octets from 192.168.0.125: icmp_seq=2 ttl=255 time=67.8 ms
64 octets from 192.168.0.125: icmp_seq=3 ttl=255 time=600.3 ms
64 octets from 192.168.0.125: icmp_seq=4 ttl=255 time=1126.1 ms
wrong data byte #0 should be 0xa1 but was 0xa0a0 2b bf 49 94 32 a 0
8 9 a b c d e f 10 11 12 13 14 15 16 17 18 19 1a 1b 1c 1d 1e 1f 20 21 22
23 24 25 26 27
28 29 2a 2b 2c 2d 2e 2f
64 octets from 192.168.0.125: icmp_seq=5 ttl=255 time=130.0 ms
64 octets from 192.168.0.125: icmp_seq=6 ttl=255 time=653.3 ms
--- 192.168.0.125 ping statistics ---
8 packets transmitted, 7 packets received, 12% packet loss
When CS is down ping is good to the mipt device.
I have same subnet, no firewall, no routing rules etc
Any idea?
Hi guys,
I'm installing my first mipt system on Motorola WS5100 AP system (OXE 9.0 h1.301.24.none; mipt version: 119.045 120.013 121.005) . The issue I'm facing is that my mipt registers ok to the system (I can see the number, time/date from the system ok), but when trying to call other device or even trying to access the menu (or calling inbound) returns "Net busy <AP MAC addr>". (maintenance description of error: Handset cannot obtain sufficient bandwidth to support a call; displays MAC of failing AP --->resolution: Try the call again later.
)Tryed with compression (G.729 ) and without (G.711) no joy. Domain configured ok, multi algorithms in system, etc.
Played with UDP param (lost, reinit and keep alive) --- used the ones recommended in doc and on forum (+other values).
Played with reset for update yes/no still no joy.
I even reproduced the issue back home in my lab on a Linksys WRT54GL with WMM support from DD-WRT firmware -- and played with all sorts of parameters that Linksys has, but I just don't seem to find a way to clear it. In the lab (on Linksys mobile SJ phone -- sip end point and my pocket communicator work both well).
When using WMM it the ping of the mipt is very high (and loss occurs) - on both Linksys and Motorola
Ping from CS to mipt:
PING 192.168.0.125 (192.168.0.125): 56 octets data
64 octets from 192.168.0.125: icmp_seq=0 ttl=255 time=526.9 ms
64 octets from 192.168.0.125: icmp_seq=1 ttl=255 time=1063.9 ms
wrong data byte #0 should be 0x9e but was 0x9d9d 2b bf 49 16 c a 0
8 9 a b c d e f 10 11 12 13 14 15 16 17 18 19 1a 1b 1c 1d 1e 1f 20 21 22
23 24 25 26 27
28 29 2a 2b 2c 2d 2e 2f
64 octets from 192.168.0.125: icmp_seq=2 ttl=255 time=67.8 ms
64 octets from 192.168.0.125: icmp_seq=3 ttl=255 time=600.3 ms
64 octets from 192.168.0.125: icmp_seq=4 ttl=255 time=1126.1 ms
wrong data byte #0 should be 0xa1 but was 0xa0a0 2b bf 49 94 32 a 0
8 9 a b c d e f 10 11 12 13 14 15 16 17 18 19 1a 1b 1c 1d 1e 1f 20 21 22
23 24 25 26 27
28 29 2a 2b 2c 2d 2e 2f
64 octets from 192.168.0.125: icmp_seq=5 ttl=255 time=130.0 ms
64 octets from 192.168.0.125: icmp_seq=6 ttl=255 time=653.3 ms
--- 192.168.0.125 ping statistics ---
8 packets transmitted, 7 packets received, 12% packet loss
When CS is down ping is good to the mipt device.
I have same subnet, no firewall, no routing rules etc
Any idea?