Mitel Forums - The Unofficial Source
Mitel Forums => Mitel MiVoice Business/MCD/3300 => Topic started by: SPSX on February 17, 2023, 06:36:05 PM
-
I am trying to set up an Axis A8105-E Network Video intercom with our local MiVoice Business server. I have been able to register the device with the server and it is able to receive calls.
The trouble comes when I try to place a call with the device, however.
I've tried calling multiple combinations of SIP addresses. For example, trying to call extension 1998 I've tried the following to no avail.
[Server IP is 10.2.16.5]
1998
1998@10.2.16.5
1998@10.2.16.5:5060
I am able to get WireShark traces on the device and here are the relevant bits (outgoing call, failed):
Request: INVITE sip:1937@10.2.16.5:5060 |
Status: 100 Trying |
Status: 401 Unauthorized |
Request: ACK sip:1937@10.2.16.5:5060 |
Request: INVITE sip:1937@10.2.16.5:5060 |
Status: 100 Trying |
Status: 503 Service Unavailable |
When I get a trace on an incoming call, here is what the relevant data looks like (successful incoming call):
Request: INVITE sip:1998@10.5.6.145:5060 |
Status: 100 Trying |
Status: 200 OK (INVITE) |
Request: ACK sip:1998@10.5.6.145:5060;ob |
Request: BYE sip:1998@10.5.6.145:5060;ob |
Status: 200 OK (BYE) |
Does anyone have any idea what I'm missing?
-
Disable the video on the Axis camera...
Otherwise, can you get a full SIP trace, not just the overview?
-
Disable the video on the Axis camera...
Otherwise, can you get a full SIP trace, not just the overview?
SIP video is disabled.
Attached is a trace of both a failed outgoing call as well as a successful incoming call.
According to the logs on the Axis device, the "Last status code" is 503.
2023-02-20T15:28:45.524+00:00 axis-b8a44f6a066f [ INFO ] sipd[2662]: 15:28:45.960 Making call Out-0-1676906925.523695-zBYjeapf.ylvWuGk.YWDFdk0x10vyHT- from sip_account_1 to 1937.
2023-02-20T15:28:45.589+00:00 axis-b8a44f6a066f [ WARNING ] sipd[2662]: 15:28:45.313 SIP session disconnected (calling), last status code: 503
2023-02-20T15:28:45.590+00:00 axis-b8a44f6a066f [ INFO ] sipd[2662]: 15:28:45.129 Terminated outgoing call: Out-0-1676906925.523695-zBYjeapf.ylvWuGk.YWDFdk0x10vyHT-
-
I think the 503 is telling you the Axis is trying to use a protocol the MiVB doesn't support. Also the INVITE packet from the AXIS is over MTU and getting fragmented. Turn off/disable all voice codecs except G.711 U-law (sometimes just shortened to ulaw).
-
I think the 503 is telling you the Axis is trying to use a protocol the MiVB doesn't support. Also the INVITE packet from the AXIS is over MTU and getting fragmented. Turn off/disable all voice codecs except G.711 U-law (sometimes just shortened to ulaw).
It doesn't seem that G.711 U-law is an option. Here are the available codecs:
L16/8000 (8000 Hz)
speex/16000 (16000 Hz)
speex/8000 (8000 Hz)
G.726-32 (8000 Hz)
PCMU (8000 Hz)
PCMA (8000 Hz)
opus (48000 Hz)
L16/16000 (16000 Hz)
I disabled all codecs except for PCMCU (8000 Hz) because it is the codec with which I am able to call the intercom.
-
I got it working!!!
I had to change the Service Level to "Full" instead of "Multi-device."
Thanks for everyone's help and suggestions!
-
I got it working!!!
I had to change the Service Level to "Full" instead of "Multi-device."
Thanks for everyone's help and suggestions!
For future reference, because this will bite you again on something else: if a device is set with a Service Level of "Multi-device", it has to be a member of a Mutli Device User Group.