Really could use help 3cx v11 sangoma a101de

Discussion in '3CX Phone System - General' started by hoosier1077, Jan 12, 2013.

Thread Status:
Not open for further replies.
  1. hoosier1077

    Joined:
    Mar 5, 2011
    Messages:
    52
    Likes Received:
    0
    Hello,
    I have a few 3cx setups and they are basically all the same. I have 2 running v10 with sangoma a101de cards along with a pri from carrier. Those 2 have been up for year now no problems. I setup a another 3cx system in our other store, running v11 with same sangoma a101de card. I have it syncd up to pri and calls coming in and out, however after a number of calls, the next one to come in has one way audio? Its always we can hear them but they cant hear us. I have the verbos log below, it clearly shows me calling a few times and getting the voicemail i inteded to get. Then out of nowhere my next call I get dead air, the call completes and goes to voicemail box but I cant hear the voicemail greeting anymore, rtp error. I could really use some help on this, my sangoma card is configured same as my other two 3cx servers, so i dont know whats going on. Thanks in advance!
     
  2. hoosier1077

    Joined:
    Mar 5, 2011
    Messages:
    52
    Likes Received:
    0
    Sorry, forgot logs...

    12-Jan-2013 07:06:21.279 Leg L:3.1[Line:10000<<3177100787] is terminated: Cause: BYE from 10.198.66.201:5066
    12-Jan-2013 07:06:11.912 [MS004000] C:3.1: (PASSTHROUGH): Can't send RTP stream to 127.0.0.1:14014 destination unreachable (0)
    12-Jan-2013 07:06:11.859 [CM503007]: Call(C:3): VMail:999 has joined, contact <sip:999@127.0.0.1:40600>
    12-Jan-2013 07:06:11.856 [CM503007]: Call(C:3): Line:10000<<3177100787 has joined, contact <sip:10000@127.0.0.1:5066>
    12-Jan-2013 07:06:11.856 L:3.2[VMail] has joined to L:3.1[Line:10000<<3177100787]
    12-Jan-2013 07:06:11.855 NAT/ALG check:L:3.2[VMail] RESPONSE 200 on 'INVITE' - basic check passed. No information for extended checks
    12-Jan-2013 07:06:11.719 [CM503025]: Call(C:3): Calling T:VMail:999@[Dev:sip:999@127.0.0.1:40600;rinstance=fd4c26ce6a5288d2] for L:3.1[Line:10000<<3177100787]
    12-Jan-2013 07:06:11.674 [CM503027]: Call(C:3): From: Line:10000<<3177100787 ("Cell Phone IN" <sip:3177100787@10.198.66.201:5060>) to T:VMail:999@[Dev:sip:999@127.0.0.1:40600;rinstance=fd4c26ce6a5288d2]
    12-Jan-2013 07:06:11.674 [CM503004]: Call(C:3): Route 1: from L:3.1[Line:10000<<3177100787] to T:VMail:999@[Dev:sip:999@127.0.0.1:40600;rinstance=fd4c26ce6a5288d2]
    12-Jan-2013 07:06:11.672 [CM503001]: Call(C:3): Incoming call from Line:10000<<3177100787 to <sip:118@10.198.66.201:5060>
    12-Jan-2013 07:06:11.672 Line limit check: Current # of calls for line Lc:10000(@Sangoma5[<sip:10000@127.0.0.1:5066>]) is 1; limit is 12
    12-Jan-2013 07:06:11.672 NAT/ALG check:L:3.1[Line:10000<<3177100787] REQUEST 'INVITE' - some of SIP/SDP headers may contain inconsistent information or modified by intermediate hop
    Media session IP ('c=' attribute) is not equal to the IP specified in contact header:
    Media session IP:127.0.0.1
    Contact IP:10.198.66.201
    Media session IP ('c=' attribute) is not equal to the SIP packet source(IP:port):
    Media session IP: 127.0.0.1
    Received from: 10.198.66.201
    12-Jan-2013 07:06:11.667 [CM503012]: Inbound any hours rule (unnamed) for 10000 forwards to VM:118
    12-Jan-2013 07:03:02.905 Leg L:2.2[VMail] is terminated: Cause: BYE from PBX
    12-Jan-2013 07:03:02.905 [CM503008]: Call(C:2): Call is terminated
    12-Jan-2013 07:03:02.904 Leg L:2.1[Line:10000<<3177100787] is terminated: Cause: BYE from 127.0.0.1:5066
    12-Jan-2013 07:02:56.526 [CM503007]: Call(C:2): VMail:999 has joined, contact <sip:999@127.0.0.1:40600>
    12-Jan-2013 07:02:56.524 [CM503007]: Call(C:2): Line:10000<<3177100787 has joined, contact <sip:10000@127.0.0.1:5066>
    12-Jan-2013 07:02:56.523 L:2.2[VMail] has joined to L:2.1[Line:10000<<3177100787]
    12-Jan-2013 07:02:56.523 NAT/ALG check:L:2.2[VMail] RESPONSE 200 on 'INVITE' - basic check passed. No information for extended checks
    12-Jan-2013 07:02:56.372 [CM503025]: Call(C:2): Calling T:VMail:999@[Dev:sip:999@127.0.0.1:40600;rinstance=fd4c26ce6a5288d2] for L:2.1[Line:10000<<3177100787]
    12-Jan-2013 07:02:56.325 [CM503027]: Call(C:2): From: Line:10000<<3177100787 ("Cell Phone IN" <sip:3177100787@10.198.66.201:5060>) to T:VMail:999@[Dev:sip:999@127.0.0.1:40600;rinstance=fd4c26ce6a5288d2]
    12-Jan-2013 07:02:56.325 [CM503004]: Call(C:2): Route 1: from L:2.1[Line:10000<<3177100787] to T:VMail:999@[Dev:sip:999@127.0.0.1:40600;rinstance=fd4c26ce6a5288d2]
    12-Jan-2013 07:02:56.324 [CM503001]: Call(C:2): Incoming call from Line:10000<<3177100787 to <sip:118@10.198.66.201:5060>
    12-Jan-2013 07:02:56.324 Line limit check: Current # of calls for line Lc:10000(@Sangoma5[<sip:10000@127.0.0.1:5066>]) is 1; limit is 12
    12-Jan-2013 07:02:56.324 NAT/ALG check:L:2.1[Line:10000<<3177100787] REQUEST 'INVITE' - some of SIP/SDP headers may contain inconsistent information or modified by intermediate hop
    Media session IP ('c=' attribute) is not equal to the IP specified in contact header:
    Media session IP:127.0.0.1
    Contact IP:10.198.66.201
    Media session IP ('c=' attribute) is not equal to the SIP packet source(IP:port):
    Media session IP: 127.0.0.1
    Received from: 10.198.66.201
    12-Jan-2013 07:02:56.320 [CM503012]: Inbound any hours rule (unnamed) for 10000 forwards to VM:118
    12-Jan-2013 06:57:53.127 Leg L:1.2[VMail] is terminated: Cause: BYE from PBX
    12-Jan-2013 06:57:53.127 [CM503008]: Call(C:1): Call is terminated
    12-Jan-2013 06:57:53.125 Leg L:1.1[Line:10000<<3177100787] is terminated: Cause: BYE from 127.0.0.1:5066
    12-Jan-2013 06:57:43.388 [CM503007]: Call(C:1): VMail:999 has joined, contact <sip:999@127.0.0.1:40600>
    12-Jan-2013 06:57:43.386 [CM503007]: Call(C:1): Line:10000<<3177100787 has joined, contact <sip:10000@127.0.0.1:5066>
    12-Jan-2013 06:57:43.385 L:1.2[VMail] has joined to L:1.1[Line:10000<<3177100787]
    12-Jan-2013 06:57:43.384 NAT/ALG check:L:1.2[VMail] RESPONSE 200 on 'INVITE' - basic check passed. No information for extended checks
    12-Jan-2013 06:57:43.233 [CM503025]: Call(C:1): Calling T:VMail:999@[Dev:sip:999@127.0.0.1:40600;rinstance=fd4c26ce6a5288d2] for L:1.1[Line:10000<<3177100787]
    12-Jan-2013 06:57:43.188 [CM503027]: Call(C:1): From: Line:10000<<3177100787 ("Cell Phone IN" <sip:3177100787@10.198.66.201:5060>) to T:VMail:999@[Dev:sip:999@127.0.0.1:40600;rinstance=fd4c26ce6a5288d2]
    12-Jan-2013 06:57:43.188 [CM503004]: Call(C:1): Route 1: from L:1.1[Line:10000<<3177100787] to T:VMail:999@[Dev:sip:999@127.0.0.1:40600;rinstance=fd4c26ce6a5288d2]
    12-Jan-2013 06:57:43.187 [CM503001]: Call(C:1): Incoming call from Line:10000<<3177100787 to <sip:118@10.198.66.201:5060>
    12-Jan-2013 06:57:43.187 Line limit check: Current # of calls for line Lc:10000(@Sangoma5[<sip:10000@127.0.0.1:5066>]) is 1; limit is 12
    12-Jan-2013 06:57:43.187 NAT/ALG check:L:1.1[Line:10000<<3177100787] REQUEST 'INVITE' - some of SIP/SDP headers may contain inconsistent information or modified by intermediate hop
    Media session IP ('c=' attribute) is not equal to the IP specified in contact header:
    Media session IP:127.0.0.1
    Contact IP:10.198.66.201
    Media session IP ('c=' attribute) is not equal to the SIP packet source(IP:port):
    Media session IP: 127.0.0.1
    Received from: 10.198.66.201
    12-Jan-2013 06:57:43.181 [CM503012]: Inbound any hours rule (unnamed) for 10000 forwards to VM:118
    12-Jan-2013 06:57:35.891 IP(s) added:[10.198.66.201]
    12-Jan-2013 06:57:35.400 [CM504001]: Endpoint Conf:704: new contact is registered. Contact(s): [sip:704@127.0.0.1:40300 / 704]
    12-Jan-2013 06:57:35.400 [CM504001]: Endpoint Conf:703: new contact is registered. Contact(s): [sip:703@127.0.0.1:40300 / 703]
    12-Jan-2013 06:57:35.399 [CM504001]: Endpoint Conf:702: new contact is registered. Contact(s): [sip:702@127.0.0.1:40300 / 702]
    12-Jan-2013 06:57:35.396 [CM504001]: Endpoint Conf:701: new contact is registered. Contact(s): [sip:701@127.0.0.1:40300 / 701]
    12-Jan-2013 06:57:35.391 [CM504001]: Endpoint Conf:700: new contact is registered. Contact(s): [sip:700@127.0.0.1:40300 / 700]
    12-Jan-2013 06:57:34.579 [CM504001]: Endpoint ParkOrb:SP9: new contact is registered. Contact(s): [sip:SP9@127.0.0.1:40000 / SP9]
    12-Jan-2013 06:57:34.490 [CM504001]: Endpoint ParkOrb:SP8: new contact is registered. Contact(s): [sip:SP8@127.0.0.1:40000 / SP8]
    12-Jan-2013 06:57:34.490 [CM504001]: Endpoint ParkOrb:SP7: new contact is registered. Contact(s): [sip:SP7@127.0.0.1:40000 / SP7]
    12-Jan-2013 06:57:34.490 [CM504001]: Endpoint ParkOrb:SP6: new contact is registered. Contact(s): [sip:SP6@127.0.0.1:40000 / SP6]
    12-Jan-2013 06:57:34.489 [CM504001]: Endpoint ParkOrb:SP5: new contact is registered. Contact(s): [sip:SP5@127.0.0.1:40000 / SP5]
    12-Jan-2013 06:57:34.489 [CM504001]: Endpoint ParkOrb:SP4: new contact is registered. Contact(s): [sip:SP4@127.0.0.1:40000 / SP4]
    12-Jan-2013 06:57:34.486 [CM504001]: Endpoint ParkOrb:SP3: new contact is registered. Contact(s): [sip:SP3@127.0.0.1:40000 / SP3]
    12-Jan-2013 06:57:34.484 [CM504001]: Endpoint ParkOrb:SP2: new contact is registered. Contact(s): [sip:SP2@127.0.0.1:40000 / SP2]
    12-Jan-2013 06:57:34.479 [CM504001]: Endpoint ParkOrb:SP1: new contact is registered. Contact(s): [sip:SP1@127.0.0.1:40000 / SP1]
    12-Jan-2013 06:57:34.474 [CM504001]: Endpoint ParkOrb:SP0: new contact is registered. Contact(s): [sip:SP0@127.0.0.1:40000 / SP0]
    12-Jan-2013 06:57:34.467 [CM504001]: Endpoint ParkOrb:*1: new contact is registered. Contact(s): [sip:*1@127.0.0.1:40000 / *1]
    12-Jan-2013 06:57:34.463 [CM504001]: Endpoint ParkOrb:*0: new contact is registered. Contact(s): [sip:*0@127.0.0.1:40000 / *0]
    12-Jan-2013 06:57:34.463 [CM504001]: Endpoint ParkOrb:*777: new contact is registered. Contact(s): [sip:*777@127.0.0.1:40000 / *777]
    12-Jan-2013 06:57:31.404 [CM504001]: Endpoint Ivr:RecordFile: new contact is registered. Contact(s): [sip:RecordFile@127.0.0.1:40600 / RecordFile]
    12-Jan-2013 06:57:31.401 [CM504001]: Endpoint Ivr:playFile: new contact is registered. Contact(s): [sip:playFile@127.0.0.1:40600 / PlayFile]
    12-Jan-2013 06:57:31.400 [CM504001]: Endpoint Ivr:MakeCall: new contact is registered. Contact(s): [sip:MakeCall@127.0.0.1:40600 / MakeCall]
    12-Jan-2013 06:57:31.400 [CM504001]: Endpoint Ivr:IVRForward: new contact is registered. Contact(s): [sip:IVRForward@127.0.0.1:40600 / IVRForward]
    12-Jan-2013 06:57:31.399 [CM504001]: Endpoint Ivr:EndCall: new contact is registered. Contact(s): [sip:EndCall@127.0.0.1:40600 / EndCall]
    12-Jan-2013 06:57:31.398 [CM504001]: Endpoint Ivr:777: new contact is registered. Contact(s): [sip:777@127.0.0.1:40600 / 777]
    12-Jan-2013 06:57:31.390 [CM504001]: Endpoint Ivr:HOL: new contact is registered. Contact(s): [sip:HOL@127.0.0.1:40600 / HOL]
    12-Jan-2013 06:57:31.379 [CM504001]: Endpoint VMail:999: new contact is registered. Contact(s): [sip:999@127.0.0.1:40600 / 999]
    12-Jan-2013 06:57:29.966 [CM504008]: Fax Service: Fax.888 registered as sip:888@127.0.0.1:5060 with contact sip:888@127.0.0.1:5100;user=phone
    12-Jan-2013 06:57:28.883 [EC200002]: Media server is connected:
    application:lcspbx1:0/MediaServer
    local:127.0.0.1:5482
    remote:127.0.0.1:55104
    12-Jan-2013 06:57:28.575 [CM504001]: Endpoint Ivr:DialCode: new contact is registered. Contact(s): [sip:DialCode@127.0.0.1:5488 / DialCode]
    12-Jan-2013 06:57:27.103 [CM504002]: Endpoint Ivr:DialCode: a contact is unregistered. Contact(s): []
    12-Jan-2013 06:57:26.980 [CM506005]: Public IP=50.195.146.97 is used for WAN communications through local interface with IP=10.198.66.201
    12-Jan-2013 06:57:25.900 [CM501006]: Default Local IP address: [10.198.66.201]
    12-Jan-2013 06:57:25.899 [CM501002]: Version: 11.0.27565.0
    12-Jan-2013 06:57:25.899 [CM501001]: Start 3CX PhoneSystem Call Manager
    12-Jan-2013 06:57:25.899 [CM501009]: License Info: Loaded Succeeded
    12-Jan-2013 06:57:25.796 [CM501007]: *** Started Calls Controller thread ***
     
  3. lneblett

    lneblett Well-Known Member

    Joined:
    Sep 7, 2010
    Messages:
    2,083
    Likes Received:
    61
    You may need to run a wireshark trace as port 14014 appears to be unreachable which is where the RTP packets are wanting to go. I can't tell from the posting what ports the other 2 calls used. You might also run a netstat to see if other processes are running that may occupy that particular port. Given that you have several of the cards in use and all are set-up identically, it seems possible that the 3CX instances might be running on machines that use different applications and therefore tie up different ports.
     
  4. hoosier1077

    Joined:
    Mar 5, 2011
    Messages:
    52
    Likes Received:
    0
    Thanks for getting back to me today. Its weird, the servers are all clean installs 2008r2 with no other apps installed exepct 3cx and netborder express. The only difference is this is new install so 3cx is v11 while the others are 10. When we get the one way audio issue, which happens after 20min or so of calls where audio works fine both ways, what I have found works is jumping in the 2008 server services and restarting the netborder express gateway and gateway manager. After doing that, the audio comes back to working, but only for about 15-20min worth of calls. This 3cx install is also using IIS, as the other 2 servers use abyss. Does any of that stand out to you? Thanks again very much for help
     
  5. lneblett

    lneblett Well-Known Member

    Joined:
    Sep 7, 2010
    Messages:
    2,083
    Likes Received:
    61
    Nothing about the different instances stands out to me, but for some reason the port is unreachable. Again, I would run netstat and look to see if the port is in use by something and run a wireshark.
     
  6. badsushi

    Joined:
    Mar 26, 2011
    Messages:
    27
    Likes Received:
    0
    Change the IP in the routing rules from 127.0.0.1 to the actual IP of your 3CX box.

    Also for good measure open a dos box and run:
    wanpipemon -i wanpipe1_if1 -c sc

    make sure none of your error counters are incrementing
     
  7. badsushi

    Joined:
    Mar 26, 2011
    Messages:
    27
    Likes Received:
    0
    I'm curious... Do your other installs also use DE boards

    When i had this exact same problem it was also on a PCI express board but most if my installs since have been just PCI and haven't seen it again although i do change the IP's every time now.
     
  8. Marcus Ribeiro

    Joined:
    Jun 25, 2017
    Messages:
    1
    Likes Received:
    0
    Hi,

    Do you solved that? I Have a similar problem with 3cx v11 and sangoma a101.

    I have upgraded to v11 and I don't have two ways audios.

    Thanks,
     
Thread Status:
Not open for further replies.