Show Posts

This section allows you to view all posts made by this member. Note that you can only see posts made in areas you currently have access to.


Messages - fghjkl

Pages: [1]
1
Mitel MiVoice Business/MCD/3300 / Sending the Peer Address
« on: October 25, 2018, 02:54:05 PM »
Is there a way to get the MBG/SRC to send not only the MAC address of the SIP trunk but also the peer address? This currently only exists in the trunk_status_event

Thank you

2
Mitel MiVoice Business/MCD/3300 / SIP Peer Profile by Incoming DID
« on: October 23, 2018, 10:58:59 AM »
Hi everyone

So a call comes in on Peer1

I have SIP Peer Profile by Incoming DID set for Peer2

So the DID range matches and the MCD correctly sends MiTAI events for Peer2

But the MBG/SRC is sending a stream_start_event with the MAC address of the SIP Trunk Peer1


Is there any way to get the MBG/SRC to send MAC address of Peer2?

Thanks for your time

3
SIP On Mitel / Random INVITE sip, causing garbled audio recording
« on: September 18, 2018, 02:13:23 PM »
Mitel5000 v 6.2.5.80
MBG
SIP trunks
MiVCR 9.1 SP4
Port mirroring

I'm completely new to this area bare with me :)

There are many cases, but this is not consistent -- where we will get 1 packet RTP streams..

Example:
Recording audio stream between 192.168.168.60:6112 to 192.168.168.65:29840 , all good

Then there's a 1 packet RTP sent from 192.168.168.60:6112 to 192.168.168.65:25382 (payload is all Fs)

What causes these 1 packet RTP streams? There's a whole SIP flow associated with it.. but it's all for one packet!


--
INVITE sip:###@192.168.168.60:5060;user=phone SIP/2.0
Via: SIP/2.0/UDP 192.168.168.65:5060;branch=z9hG4bK-d8754z-e0fda911a8aa4a4f-1---d8754z-;rport
Max-Forwards: 82
Record-Route: <sip:192.168.168.65:5060;lr;transport=UDP>
Contact: <sip:###@192.168.168.65:5060;transport=UDP;user=phone>
To: <sip:###@192.168.168.60:5060;user=phone>
From: "" <sip:###@68.68.123.167:5060;user=phone>;tag=4b315d750a020200
Call-ID: 1-4b315d750a020200.47096686@68.68.123.167X
CSeq: 2 INVITE
Allow: ACK, BYE, CANCEL, INVITE, OPTIONS, PRACK
Content-Type: application/sdp
Supported: 100rel
User-Agent: Mitel Border GW/4.7.0.10-01
P-Asserted-Identity: "" <sip:###@68.68.123.167:5060>
Content-Length: 223

v=0
o=- 1527080289 1527080290 IN IP4 192.168.168.65
s=IGW
c=IN IP4 192.168.168.65
t=0 0
m=audio 29840 RTP/AVP 0 101
a=rtpmap:0 PCMU/8000
a=rtpmap:101 telephone-event/8000
a=fmtp:101 0-15
a=maxptime:20
a=ptime:20
SIP/2.0 100 Trying
Via: SIP/2.0/UDP 192.168.168.65:5060;received=192.168.168.65;branch=z9hG4bK-d8754z-e0fda911a8aa4a4f-1---d8754z-;rport=5060
From: "" <sip:###@68.68.123.167:5060;user=phone>;tag=4b315d750a020200
To: <sip:###@192.168.168.60:5060;user=phone>;tag=Mitel-5000_343457639-896
Call-ID: 1-4b315d750a020200.47096686@68.68.123.167X
CSeq: 2 INVITE
Contact: <sip:###@192.168.168.60:5060>
Allow: NOTIFY,REGISTER,REFER,SUBSCRIBE,INFO,INVITE,ACK,OPTIONS,CANCEL,BYE
User-Agent: Mitel-5000-ICP-6.2.5.80
Content-Length: 0

SIP/2.0 200 OK
Via: SIP/2.0/UDP 192.168.168.65:5060;received=192.168.168.65;branch=z9hG4bK-d8754z-e0fda911a8aa4a4f-1---d8754z-;rport=5060
Record-Route: <sip:192.168.168.65:5060;lr;transport=UDP>
From: "" <sip:###@68.68.123.167:5060;user=phone>;tag=4b315d750a020200
To: <sip:###@192.168.168.60:5060;user=phone>;tag=Mitel-5000_343457639-896
Call-ID: 1-4b315d750a020200.47096686@68.68.123.167X
CSeq: 2 INVITE
Contact: <sip:###@192.168.168.60:5060>
Allow: NOTIFY,REGISTER,REFER,SUBSCRIBE,INFO,INVITE,ACK,OPTIONS,CANCEL,BYE
User-Agent: Mitel-5000-ICP-6.2.5.80
P-Asserted-Identity: "" <sip:###@68.68.123.167>
Content-Type: application/sdp
Content-Length: 264

v=0
o=Mitel-5000-ICP 1088539704 1527080261 IN IP4 192.168.168.60
s=SIP Call
c=IN IP4 192.168.168.60
t=0 0
a=sendrecv
m=audio 6112 RTP/AVP 0 101
a=rtpmap:0 PCMU/8000
a=rtpmap:101 telephone-event/8000
a=fmtp:101 0-15
a=ptime:20
a=maxptime:20
a=sendrecv
ACK sip:###@192.168.168.60:5060 SIP/2.0
Via: SIP/2.0/UDP 192.168.168.65:5060;branch=z9hG4bK-d8754z-88277e4fc61a565d-1---d8754z-;rport
Max-Forwards: 70
To: <sip:###@192.168.168.60:5060;user=phone>;tag=Mitel-5000_343457639-896
From: "" <sip:###@68.68.123.167:5060;user=phone>;tag=4b315d750a020200
Call-ID: 1-4b315d750a020200.47096686@68.68.123.167X
CSeq: 2 ACK
User-Agent: Mitel Border GW/4.7.0.10-01
Content-Length: 0



INVITE sip:###@192.168.168.65:5060;transport=UDP;user=phone SIP/2.0
Via: SIP/2.0/UDP 192.168.168.60:5060;branch=z9hG4bK361013219-896
Route: <sip:192.168.168.65:5060;lr;transport=UDP>
Max-Forwards: 70
Allow: NOTIFY,REGISTER,REFER,SUBSCRIBE,INFO,INVITE,ACK,OPTIONS,CANCEL,BYE
P-Asserted-Identity: "" <sip:###@68.68.123.167>
User-Agent: Mitel-5000-ICP-6.2.5.80
From: <sip:###@192.168.168.60:5060;user=phone>;tag=Mitel-5000_343457639-896
To: "" <sip:###@68.68.123.167:5060;user=phone>;tag=4b315d750a020200
Call-ID: 1-4b315d750a020200.47096686@68.68.123.167X
CSeq: 2 INVITE
Contact: <sip:####@192.168.168.60:5060>
Content-Type: application/sdp
Content-Length: 299

v=0
o=Mitel-5000-ICP 1088539704 1527080279 IN IP4 192.168.168.60
s=SIP Call
c=IN IP4 192.168.168.60
t=0 0
m=audio 6112 RTP/AVP 0 8 101
a=rtpmap:0 PCMU/8000
a=rtpmap:8 PCMA/8000
a=rtpmap:101 telephone-event/8000
a=fmtp:101 0-15
a=ptime:20
a=maxptime:30
a=sqn:0
a=cdsc:1 image udptl t38
SIP/2.0 100 Trying
Via: SIP/2.0/UDP 192.168.168.60:5060;branch=z9hG4bK361013219-896
To: "" <sip:###@68.68.123.167:5060;user=phone>;tag=4b315d750a020200
From: <sip:###@192.168.168.60:5060;user=phone>;tag=Mitel-5000_343457639-896
Call-ID: 1-4b315d750a020200.47096686@68.68.123.167X
CSeq: 2 INVITE
User-Agent: Mitel Border GW/4.7.0.10-01
Content-Length: 0

SIP/2.0 200 OK
Via: SIP/2.0/UDP 192.168.168.60:5060;branch=z9hG4bK361013219-896
Record-Route: <sip:192.168.168.65:5060;lr;transport=UDP>
Contact: <sip:###@192.168.168.65:5060;transport=UDP;user=phone>
To: "" <sip:###@68.68.123.167:5060;user=phone>;tag=4b315d750a020200
From: <sip:###@192.168.168.60:5060;user=phone>;tag=Mitel-5000_343457639-896
Call-ID: 1-4b315d750a020200.47096686@68.68.123.167X
CSeq: 2 INVITE
Allow: ACK, BYE, CANCEL, INVITE, OPTIONS, PRACK
Content-Type: application/sdp
Date: Wed, 23 May 2018 12:58:26 GMT
User-Agent: Mitel Border GW/4.7.0.10-01
Content-Length: 235

v=0
o=- 1527080289 1527080308 IN IP4 192.168.168.65
s=IGW
c=IN IP4 192.168.168.65
t=0 0
m=audio 25382 RTP/AVP 0 101
a=rtpmap:0 PCMU/8000
a=rtpmap:101 telephone-event/8000
a=fmtp:101 0-15
a=maxptime:20
a=ptime:20
a=sendrecv
ACK sip:####@192.168.168.65:5060;transport=UDP;user=phone SIP/2.0
Via: SIP/2.0/UDP 192.168.168.60:5060;branch=z9hG4bK361145899-896
Route: <sip:192.168.168.65:5060;lr;transport=UDP>
Max-Forwards: 70
From: <sip:###@192.168.168.60:5060;user=phone>;tag=Mitel-5000_343457639-896
To: "" <sip:###@68.68.123.167:5060;user=phone>;tag=4b315d750a020200
Call-ID: 1-4b315d750a020200.47096686@68.68.123.167X
CSeq: 2 ACK
Contact: <sip:####@192.168.168.60:5060>
Content-Length: 0

4
MiVoice Office 250/Mitel 5000 / Random INVITE sip, causing garbled audio recording
« on: September 18, 2018, 02:00:06 PM »
Mitel5000 v 6.2.5.80
MBG
SIP trunks
MiVCR 9.1 SP4
Port mirroring

I'm completely new to this area bare with me :)

There are many cases, but this is not consistent -- where we will get 1 packet RTP streams..

Example:
Recording audio stream between 192.168.168.60:6112 to 192.168.168.65:29840 , all good

Then there's a 1 packet RTP sent from 192.168.168.60:6112 to 192.168.168.65:25382 (payload is all Fs)

What causes these 1 packet RTP streams? There's a whole SIP flow associated with it.. but it's all for one packet!


--
INVITE sip:###@192.168.168.60:5060;user=phone SIP/2.0
Via: SIP/2.0/UDP 192.168.168.65:5060;branch=z9hG4bK-d8754z-e0fda911a8aa4a4f-1---d8754z-;rport
Max-Forwards: 82
Record-Route: <sip:192.168.168.65:5060;lr;transport=UDP>
Contact: <sip:###@192.168.168.65:5060;transport=UDP;user=phone>
To: <sip:###@192.168.168.60:5060;user=phone>
From: "" <sip:###@68.68.123.167:5060;user=phone>;tag=4b315d750a020200
Call-ID: 1-4b315d750a020200.47096686@68.68.123.167X
CSeq: 2 INVITE
Allow: ACK, BYE, CANCEL, INVITE, OPTIONS, PRACK
Content-Type: application/sdp
Supported: 100rel
User-Agent: Mitel Border GW/4.7.0.10-01
P-Asserted-Identity: "" <sip:###@68.68.123.167:5060>
Content-Length: 223

v=0
o=- 1527080289 1527080290 IN IP4 192.168.168.65
s=IGW
c=IN IP4 192.168.168.65
t=0 0
m=audio 29840 RTP/AVP 0 101
a=rtpmap:0 PCMU/8000
a=rtpmap:101 telephone-event/8000
a=fmtp:101 0-15
a=maxptime:20
a=ptime:20
SIP/2.0 100 Trying
Via: SIP/2.0/UDP 192.168.168.65:5060;received=192.168.168.65;branch=z9hG4bK-d8754z-e0fda911a8aa4a4f-1---d8754z-;rport=5060
From: "" <sip:###@68.68.123.167:5060;user=phone>;tag=4b315d750a020200
To: <sip:###@192.168.168.60:5060;user=phone>;tag=Mitel-5000_343457639-896
Call-ID: 1-4b315d750a020200.47096686@68.68.123.167X
CSeq: 2 INVITE
Contact: <sip:###@192.168.168.60:5060>
Allow: NOTIFY,REGISTER,REFER,SUBSCRIBE,INFO,INVITE,ACK,OPTIONS,CANCEL,BYE
User-Agent: Mitel-5000-ICP-6.2.5.80
Content-Length: 0

SIP/2.0 200 OK
Via: SIP/2.0/UDP 192.168.168.65:5060;received=192.168.168.65;branch=z9hG4bK-d8754z-e0fda911a8aa4a4f-1---d8754z-;rport=5060
Record-Route: <sip:192.168.168.65:5060;lr;transport=UDP>
From: "" <sip:###@68.68.123.167:5060;user=phone>;tag=4b315d750a020200
To: <sip:###@192.168.168.60:5060;user=phone>;tag=Mitel-5000_343457639-896
Call-ID: 1-4b315d750a020200.47096686@68.68.123.167X
CSeq: 2 INVITE
Contact: <sip:###@192.168.168.60:5060>
Allow: NOTIFY,REGISTER,REFER,SUBSCRIBE,INFO,INVITE,ACK,OPTIONS,CANCEL,BYE
User-Agent: Mitel-5000-ICP-6.2.5.80
P-Asserted-Identity: "" <sip:###@68.68.123.167>
Content-Type: application/sdp
Content-Length: 264

v=0
o=Mitel-5000-ICP 1088539704 1527080261 IN IP4 192.168.168.60
s=SIP Call
c=IN IP4 192.168.168.60
t=0 0
a=sendrecv
m=audio 6112 RTP/AVP 0 101
a=rtpmap:0 PCMU/8000
a=rtpmap:101 telephone-event/8000
a=fmtp:101 0-15
a=ptime:20
a=maxptime:20
a=sendrecv
ACK sip:###@192.168.168.60:5060 SIP/2.0
Via: SIP/2.0/UDP 192.168.168.65:5060;branch=z9hG4bK-d8754z-88277e4fc61a565d-1---d8754z-;rport
Max-Forwards: 70
To: <sip:###@192.168.168.60:5060;user=phone>;tag=Mitel-5000_343457639-896
From: "" <sip:###@68.68.123.167:5060;user=phone>;tag=4b315d750a020200
Call-ID: 1-4b315d750a020200.47096686@68.68.123.167X
CSeq: 2 ACK
User-Agent: Mitel Border GW/4.7.0.10-01
Content-Length: 0



INVITE sip:###@192.168.168.65:5060;transport=UDP;user=phone SIP/2.0
Via: SIP/2.0/UDP 192.168.168.60:5060;branch=z9hG4bK361013219-896
Route: <sip:192.168.168.65:5060;lr;transport=UDP>
Max-Forwards: 70
Allow: NOTIFY,REGISTER,REFER,SUBSCRIBE,INFO,INVITE,ACK,OPTIONS,CANCEL,BYE
P-Asserted-Identity: "" <sip:###@68.68.123.167>
User-Agent: Mitel-5000-ICP-6.2.5.80
From: <sip:###@192.168.168.60:5060;user=phone>;tag=Mitel-5000_343457639-896
To: "" <sip:###@68.68.123.167:5060;user=phone>;tag=4b315d750a020200
Call-ID: 1-4b315d750a020200.47096686@68.68.123.167X
CSeq: 2 INVITE
Contact: <sip:####@192.168.168.60:5060>
Content-Type: application/sdp
Content-Length: 299

v=0
o=Mitel-5000-ICP 1088539704 1527080279 IN IP4 192.168.168.60
s=SIP Call
c=IN IP4 192.168.168.60
t=0 0
m=audio 6112 RTP/AVP 0 8 101
a=rtpmap:0 PCMU/8000
a=rtpmap:8 PCMA/8000
a=rtpmap:101 telephone-event/8000
a=fmtp:101 0-15
a=ptime:20
a=maxptime:30
a=sqn:0
a=cdsc:1 image udptl t38
SIP/2.0 100 Trying
Via: SIP/2.0/UDP 192.168.168.60:5060;branch=z9hG4bK361013219-896
To: "" <sip:###@68.68.123.167:5060;user=phone>;tag=4b315d750a020200
From: <sip:###@192.168.168.60:5060;user=phone>;tag=Mitel-5000_343457639-896
Call-ID: 1-4b315d750a020200.47096686@68.68.123.167X
CSeq: 2 INVITE
User-Agent: Mitel Border GW/4.7.0.10-01
Content-Length: 0

SIP/2.0 200 OK
Via: SIP/2.0/UDP 192.168.168.60:5060;branch=z9hG4bK361013219-896
Record-Route: <sip:192.168.168.65:5060;lr;transport=UDP>
Contact: <sip:###@192.168.168.65:5060;transport=UDP;user=phone>
To: "" <sip:###@68.68.123.167:5060;user=phone>;tag=4b315d750a020200
From: <sip:###@192.168.168.60:5060;user=phone>;tag=Mitel-5000_343457639-896
Call-ID: 1-4b315d750a020200.47096686@68.68.123.167X
CSeq: 2 INVITE
Allow: ACK, BYE, CANCEL, INVITE, OPTIONS, PRACK
Content-Type: application/sdp
Date: Wed, 23 May 2018 12:58:26 GMT
User-Agent: Mitel Border GW/4.7.0.10-01
Content-Length: 235

v=0
o=- 1527080289 1527080308 IN IP4 192.168.168.65
s=IGW
c=IN IP4 192.168.168.65
t=0 0
m=audio 25382 RTP/AVP 0 101
a=rtpmap:0 PCMU/8000
a=rtpmap:101 telephone-event/8000
a=fmtp:101 0-15
a=maxptime:20
a=ptime:20
a=sendrecv
ACK sip:####@192.168.168.65:5060;transport=UDP;user=phone SIP/2.0
Via: SIP/2.0/UDP 192.168.168.60:5060;branch=z9hG4bK361145899-896
Route: <sip:192.168.168.65:5060;lr;transport=UDP>
Max-Forwards: 70
From: <sip:###@192.168.168.60:5060;user=phone>;tag=Mitel-5000_343457639-896
To: "" <sip:###@68.68.123.167:5060;user=phone>;tag=4b315d750a020200
Call-ID: 1-4b315d750a020200.47096686@68.68.123.167X
CSeq: 2 ACK
Contact: <sip:####@192.168.168.60:5060>
Content-Length: 0

Pages: [1]