Author Topic: MBG SIP trunk behaviour  (Read 2516 times)

Offline dk39dj24lsm

  • Contributer
  • *
  • Posts: 5
  • Karma: +0/-0
    • View Profile
MBG SIP trunk behaviour
« on: March 09, 2012, 11:49:28 AM »
Hi,

I have some issues with a MCD + MBG configuration.
There are some MiNet and SIP softphones registered through MBG to MCD.
The MCD have a SIP trunk which connect it with an Asterisk box.

For all the calls between the devices registered to MCD, the <stream_start>
events are correctly supplied by MBG.
For the calls between any of those devices and other devices registered to the
Asterisk box, MGB have a strange behaviour:
When the call starts, an <stream_start> event is issued and after precisely 45
secs an <stream_stop> event is issued, for no apparent reason. The call is not
interrupted and immediately a new <stream_start> event is issued.


What can be the reason of this behaviour?

Thank you,


Offline Mitel100

  • Sr. Member
  • ****
  • Posts: 262
  • Country: gb
  • Karma: +6/-0
    • View Profile
Re: MBG SIP trunk behaviour
« Reply #1 on: March 12, 2012, 05:45:23 PM »
I haven't seen this before, but ideally we would need to see a SIP trace of the call.

Offline dk39dj24lsm

  • Contributer
  • *
  • Posts: 5
  • Karma: +0/-0
    • View Profile
Re: MBG SIP trunk behaviour
« Reply #2 on: March 13, 2012, 11:15:26 AM »
What's strange is that the audio of the call is not interrupted.
The monitor of the DN of the MCD extension with Mitai Browser does not indicate the call to stop. So I don't think the issue is in MCD or in SIP trunk settings.
I think the issue is somewhere in MBG. What would be the conditions when MBG supply a stop_stream event?


 

Sitemap 1 2 3 4 5 6 7 8 9 10