Random problem with sound. Sometimes 1 way sometimes 2 way.

Discussion in '3CX Phone System - General' started by Ralph, Jul 24, 2007.

  1. Ralph

    Ralph Member

    Joined:
    Jun 28, 2007
    Messages:
    417
    Likes Received:
    0
    This problem appears to come up randomly after placing or recieving a call. The call starts normally with two way communication but after a few minutes it becomes one way with either the caller or the called person able to hear but unable to talk.

    Most calls are ok but some calls (to many) seem to have this problem.
    I have tried checking the bind to media server option but it doesn't appear to have helped.

    We are using Polycom Soundpoint IP 501 phones that are on the same subnet as the 3CX server. The 3CX server is behind a firewall and has its own public IP. The VOIP service is Broadvoice.

    Has anyone else run into this problem?

    Any ideas?

    Thanks again
     
  2. Ralph

    Ralph Member

    Joined:
    Jun 28, 2007
    Messages:
    417
    Likes Received:
    0
    I found the following log entries in server status

    I found the following log entries in server status:

    13:48:41.779 StratLink::eek:nHangUp [CM104001] Call(63): Ext.201 hung up call; cause: BYE; from IP:xxx.xxx.xxx.xxx
    13:48:28.661 MediaServerReporting::RTPReceiver [MS005001] Call(63) Ln:10000@BroadVoice 1: payload #18 doesn't correspond initial SDP datalen=20
    13:48:28.631 MediaServerReporting::RTPReceiver [MS005001] Call(63) Ln:10000@BroadVoice 1: payload #18 doesn't correspond initial SDP datalen=20
    13:48:28.611 MediaServerReporting::RTPReceiver [MS005001] Call(63) Ln:10000@BroadVoice 1: payload #18 doesn't correspond initial SDP datalen=20
    13:48:28.601 MediaServerReporting::RTPReceiver [MS005001] Call(63) Ln:10000@BroadVoice 1: payload #18 doesn't correspond initial SDP datalen=20
    13:48:28.581 MediaServerReporting::RTPReceiver [MS005001] Call(63) Ln:10000@BroadVoice 1: payload #18 doesn't correspond initial SDP datalen=20
    13:48:28.561 MediaServerReporting::RTPReceiver [MS005001] Call(63) Ln:10000@BroadVoice 1: payload #18 doesn't correspond initial SDP datalen=20
    13:48:28.541 MediaServerReporting::RTPReceiver [MS005001] Call(63) Ln:10000@BroadVoice 1: payload #18 doesn't correspond initial SDP datalen=20
    13:48:28.521 MediaServerReporting::RTPReceiver [MS005001] Call(63) Ln:10000@BroadVoice 1: payload #18 doesn't correspond initial SDP datalen=20
    13:48:28.501 MediaServerReporting::RTPReceiver [MS005001] Call(63) Ln:10000@BroadVoice 1: payload #18 doesn't correspond initial SDP datalen=20
    13:48:28.481 MediaServerReporting::RTPReceiver [MS005001] Call(63) Ln:10000@BroadVoice 1: payload #18 doesn't correspond initial SDP datalen=20
    13:48:28.461 MediaServerReporting::RTPReceiver [MS005001] Call(63) Ln:10000@BroadVoice 1: payload #18 doesn't correspond initial SDP datalen=20
    13:48:28.441 MediaServerReporting::RTPReceiver [MS005001] Call(63) Ln:10000@BroadVoice 1: payload #18 doesn't correspond initial SDP datalen=20
    13:48:28.421 MediaServerReporting::RTPReceiver [MS005001] Call(63) Ln:10000@BroadVoice 1: payload #18 doesn't correspond initial SDP datalen=20
    13:48:28.401 MediaServerReporting::RTPReceiver [MS005001] Call(63) Ln:10000@BroadVoice 1: payload #18 doesn't correspond initial SDP datalen=20
    13:48:28.381 MediaServerReporting::RTPReceiver [MS005001] Call(63) Ln:10000@BroadVoice 1: payload #18 doesn't correspond initial SDP datalen=20
    13:48:28.361 MediaServerReporting::RTPReceiver [MS005001] Call(63) Ln:10000@BroadVoice 1: payload #18 doesn't correspond initial SDP datalen=20
    13:48:28.341 MediaServerReporting::RTPReceiver [MS005001] Call(63) Ln:10000@BroadVoice 1: payload #18 doesn't correspond initial SDP datalen=20
    13:48:28.321 MediaServerReporting::RTPReceiver [MS005001] Call(63) Ln:10000@BroadVoice 1: payload #18 doesn't correspond initial SDP datalen=20
    13:48:28.301 MediaServerReporting::RTPReceiver [MS005001] Call(63) Ln:10000@BroadVoice 1: payload #18 doesn't correspond initial SDP datalen=20
    13:48:28.281 MediaServerReporting::RTPReceiver [MS005001] Call(63) Ln:10000@BroadVoice 1: payload #18 doesn't correspond initial SDP datalen=20
    13:48:28.261 MediaServerReporting::RTPReceiver [MS005001] Call(63) Ln:10000@BroadVoice 1: payload #18 doesn't correspond initial SDP datalen=20

    It looks like there is something going on with the MediaServer?
     
  3. landfiets

    landfiets New Member

    Joined:
    Jul 17, 2007
    Messages:
    242
    Likes Received:
    0
    same

    I have the same with my Telfree acount. But not always
     
  4. SY

    SY Well-Known Member
    3CX Staff

    Joined:
    Jan 26, 2007
    Messages:
    1,821
    Likes Received:
    1
    Re: I found the following log entries in server status

    Remote party uses G.729 codec to send audio. Media server never declare this codec as supported, so it is a question to stream source: Why does it ignore SDP negotiations.
     
  5. Ralph

    Ralph Member

    Joined:
    Jun 28, 2007
    Messages:
    417
    Likes Received:
    0
    Thanks Sy

    Thank you Sy,

    When you say the stream source, do you mean the VOIP provider? in this case BroadVoice?

    Thanks again
     
  6. archie

    archie Well-Known Member
    3CX Staff

    Joined:
    Aug 18, 2006
    Messages:
    1,309
    Likes Received:
    0
    Re: Thanks Sy

    Exactly.
     
  7. SY

    SY Well-Known Member
    3CX Staff

    Joined:
    Jan 26, 2007
    Messages:
    1,821
    Likes Received:
    1
    Re: Thanks Sy

    If you provide PBX logs (verbose level) for this situation, I will be able to describe this problem in details. Sure, some probability of bugs (even in 3CX PBX :D ) always present, but I'm almost (=completely :) ) sure, that G.729 never appear in Media Server SDP.
     
  8. Ralph

    Ralph Member

    Joined:
    Jun 28, 2007
    Messages:
    417
    Likes Received:
    0
    You are definitely on target Sy.

    Well you are in the money on this one Sy. I contacted BroadVoice and apparently they have a "known" problem with one way audio that began popping up last week and has been getting progressively worse. They are working on it and don't have an ETA yet.

    Guess I could have saved myself some time and effort by calling them first :roll:
     
  9. SY

    SY Well-Known Member
    3CX Staff

    Joined:
    Jan 26, 2007
    Messages:
    1,821
    Likes Received:
    1
    Re: You are definitely on target Sy.

    Why did't you send me a logs of 3CX PBX first? We would have a more information right now! :)

    Anyway, thanks a lot for your persistency! Please let us know about results.

    Thanks again!
    Stepan
     
  10. SY

    SY Well-Known Member
    3CX Staff

    Joined:
    Jan 26, 2007
    Messages:
    1,821
    Likes Received:
    1
    Re: same

    Seems we have two possible results:
    1. it is the same problem inside software of different providers
    2. it is a problem inside 3CX software.

    It is really interesting where is a source of problem.
    Let's wait for Ralph's feedback.

    Thanks,
    Stepan
     
  11. Ralph

    Ralph Member

    Joined:
    Jun 28, 2007
    Messages:
    417
    Likes Received:
    0
    BroadVoice is still working on it

    Well BroadVoice is apparently still working on it. They are not sure if it is their network or their carriers network. This keeps getting worse and worse.

    Here are logs from the 3cx server taken during a call that lost voice after starting out ok:

    Any ideas??

    Thanks again
     
  12. SY

    SY Well-Known Member
    3CX Staff

    Joined:
    Jan 26, 2007
    Messages:
    1,821
    Likes Received:
    1
    It is a messages from 3CX PBX.
    "18" never appears at the selected part of line "m=audio 9002 RTP/AVP 0 8 3 101"

    May be this information will help to "other side of force"... :)

    Thanks a lot for information
    Stepan
     
  13. Ralph

    Ralph Member

    Joined:
    Jun 28, 2007
    Messages:
    417
    Likes Received:
    0
    What?

    I'm not sure I understand Sy.

    Do you mean that 18 is supposed to appear in that line somewhere?

    What does this do or mean?

    Thanks again
     
  14. SY

    SY Well-Known Member
    3CX Staff

    Joined:
    Jan 26, 2007
    Messages:
    1,821
    Likes Received:
    1
    Re: What?

    I mean that "18" never appears in this line (in specified content), so #18 payload must not be delivered to media server.

    P.S. My previous answers was in context of "#18 payload"

    Regarding log and "disappearing" of audio.
    Log you provided doesn't highlight any problems. Which of parties stopped to hear other, you or your interlocutor? Did this problem appear right after upgrade(installation) or later?
     
  15. Ralph

    Ralph Member

    Joined:
    Jun 28, 2007
    Messages:
    417
    Likes Received:
    0
    BroadVoice seems to think it their system

    BroadVoice thinks it is a problem on their end since they have a large number of customers complaining about the same one way audio problem.

    I'm inclined to wait till next week and see if they solve the problem. So far today I haven't had the problem resurface. Maybe they are onto a fix on their end :shock:

    Thanks again,
     

Share This Page