SIP trunk to Avaya IP Office 500 - Can't call between....

[jeffpajor]

Hi all,

Does anyone have a good set of directions about linking an IP Office setup with a 3cx instance. I have the sip trunk setup and communicating (green icon on 3cx and system status shows it up on the Avaya side). But any calls to the Avaya try and then get dropped. Here are the errors on the 3cx side:

04/15/2020 9:54:14 AM - Leg L:419.1[Extn:1139] is terminated: Cause: BYE from PBX

04/15/2020 9:54:13 AM - [CM503020]: Call(C:419): Normal call termination. Call originator: Extn:1139. Reason: No answer

04/15/2020 9:54:13 AM - L:419.1[Extn:1139] failed to reach Line:1000>>1633, reason No Answer

04/15/2020 9:54:13 AM - Leg L:419.2[Line:1000>>1633] is terminated: Cause: 408 Request Timeout/INVITE from local

04/15/2020 9:54:13 AM - Call to T:Line:1000>>1633@[Dev:sip:[email protected]:5060;transport=udp] from L:419.1[Extn:1139] failed, cause: Cause: 408 Request Timeout/INVITE from local

04/15/2020 9:54:13 AM - [CM503003]: Call(C:419): Call to <sip:[email protected]:5060> has failed; Cause: 408 Request Timeout/INVITE from local

04/15/2020 9:54:07 AM - Currently active calls - 1: [419]

04/15/2020 9:53:41 AM - [CM503025]: Call(C:419): Calling T:Line:1000>>1633@[Dev:sip:[email protected]:5060;transport=udp] for L:419.1[Extn:1139]

04/15/2020 9:53:41 AM - [CM503027]: Call(C:419): From: Extn:1139 ("Pieper IT" <sip:[email protected]:0>) to T:Line:1000>>1633@[Dev:sip:[email protected]:5060;transport=udp]

04/15/2020 9:53:41 AM - [CM503004]: Call(C:419): Route 1: from L:419.1[Extn:1139] to T:Line:1000>>1633@[Dev:sip:[email protected]:5060;transport=udp]

04/15/2020 9:53:41 AM - Line limit check: Current # of calls for line Lc:1000(@AVAYA Bridge[<sip:[email protected]:5060/udp>]) is 0; limit is 1

04/15/2020 9:53:41 AM - Call(C:419): Call from Extn:1139 to 81633 matches outbound rule 'Avaya PO Bridge (8)'

04/15/2020 9:53:41 AM - [Flow] Call(C:419): has built target endpoint: Out#:>>Rule{Avaya PO Bridge (8)}>>81633 for call from L:419.1[Extn:1139]

04/15/2020 9:53:41 AM - [Flow] Target endpoint for 81633 is Out#:>>Rule{Avaya PO Bridge (8)}>>81633

04/15/2020 9:53:41 AM - [CM503010]: Call(C:419): Making route(s) from Extn:1139 to <sip:[email protected]:0/UDP>

Looks like it's trying but no cigar.....

Here's the Avaya side:

153152213mS SIP Rx: UDP 208.110.142.47:5060 -> 10.10.1.30:5060
0000 49 4e 56 49 54 45 20 73 69 70 3a 31 36 33 33 40 INVITE sip:1633@
0010 31 30 2e 31 30 2e 31 2e 33 30 3a 35 30 36 30 3b 10.10.1.30:5060;
0020 74 72 61 6e 73 70 6f 72 74 3d 75 64 70 20 53 49 transport=udp SI
0030 50 2f 32 2e 30 0d 0a 56 69 61 3a 20 53 49 50 2f P/2.0..Via: SIP/
0040 32 2e 30 2f 55 44 50 20 32 30 38 2e 31 31 30 2e 2.0/UDP 208.110.
0050 31 34 32 2e 34 37 3a 35 30 36 30 3b 62 72 61 6e 142.47:5060;bran
0060 63 68 3d 7a 39 68 47 34 62 4b 2d 35 32 34 32 38 ch=z9hG4bK-52428
0070 37 2d 31 2d 2d 2d 31 37 30 36 36 34 37 32 64 63 7-1---17066472dc
0080 30 36 34 64 30 39 3b 72 70 6f 72 74 0d 0a 4d 61 064d09;rport..Ma
0090 78 2d 46 6f 72 77 61 72 64 73 3a 20 37 30 0d 0a x-Forwards: 70..
00a0 43 6f 6e 74 61 63 74 3a 20 3c 73 69 70 3a 31 30 Contact: <sip:10
00b0 30 30 40 32 30 38 2e 31 31 30 2e 31 34 32 2e 34 [email protected]
00c0 37 3a 35 30 36 30 3e 0d 0a 54 6f 3a 20 3c 73 69 7:5060>..To: <si
00d0 70 3a 31 36 33 33 40 31 30 2e 31 30 2e 31 2e 33 p:[email protected]
00e0 30 3a 35 30 36 30 3b 74 72 61 6e 73 70 6f 72 74 0:5060;transport
00f0 3d 75 64 70 3e 0d 0a 46 72 6f 6d 3a 20 22 50 69 =udp>..From: "Pi
0100 65 70 65 72 20 49 54 22 3c 73 69 70 3a 31 30 30 xxx IT"<sip:100
0110 30 40 31 30 2e 31 30 2e 31 2e 33 30 3a 35 30 36 [email protected]:506
0120 30 3b 74 72 61 6e 73 70 6f 72 74 3d 75 64 70 3e 0;transport=udp>
0130 3b 74 61 67 3d 31 66 64 30 64 33 31 30 0d 0a 43 ;tag=1fd0d310..C
0140 61 6c 6c 2d 49 44 3a 20 41 4d 71 79 38 5a 63 43 all-ID: AMqy8ZcC
0150 31 68 78 57 47 5f 4b 76 6d 55 53 7a 34 67 2e 2e 1hxWG_KvmUSz4g..

Any thoughts on what's happening. Looks like maybe the Avaya side, but I can't tell.

I followed the first part of these directions to get the trunks setup through Step 6.

https://www.nazaudy.com/index.php/9-technology/53-setup-3cx-phone-system-vs-avaya-ip-500#Z50

Connectivity to 5060 from both sides is good and tested with a telnet attempt.


Thank you....

Jeff

 

[JohnS_3CX]

Hi Jeff,

Try searching the forum to see if other have done this successfully before.

If nothing comes up, you can always run your own captures and see what happens.

This guide below tells you what 3CX expects to see and in which fields (especially the last part at the bottom of the guide) so if you can make it match it should be ok
https://www.3cx.com/docs/

As for the other side receiving calls from 3CX, that needs to be checked on the Avaya end.

 

[jeffpajor]

Thank you, I've searched high and low (forums, google, etc) for this and tried just about everything. Most of what I found was done on older version of the IP office software, but should still be valid. It seems like the IP office box isn't sending anything back, so 3cx says hey I tried and timed out. But the sip trunk is up and running, so I don't get it.....

 

[JohnS_3CX]

You do have some options in the trunk outbound parameter than can be customized, but you would have to know what the other side expects to see and in which field. Also there may be restrictions on the other side as to where it can accept calls FROM or otherwise ignore the calls.