×
INTELLIGENT WORK FORUMS
FOR COMPUTER PROFESSIONALS

Contact US

*
*
*
*

Thanks. We have received your request and will respond promptly.

Log In

Come Join Us!

Are you a
Computer / IT professional?
Join Tek-Tips Forums!
  • Talk With Other Members
  • Be Notified Of Responses
    To Your Posts
  • Keyword Search
  • One-Click Access To Your
    Favorite Forums
  • Automated Signatures
    On Your Posts
  • Best Of All, It's Free!
*Tek-Tips's functionality depends on members receiving e-mail. By joining you are opting in to receive e-mail.

Posting Guidelines

Promoting, selling, recruiting, coursework and thesis posting is forbidden.

Students Click Here

UCx SIP trunk to Avaya Session Manager

thread1812-1818042

UCx SIP trunk to Avaya Session Manager

UCx SIP trunk to Avaya Session Manager

(OP)
Has anyone ever set up a SIP trunk to Avaya Aura Session Manager. I have added the trunk in the UCx and I have added the UCx as a SIP Entity on the Session Manager. Its all UDP. I can place calls from the UCx to the Aura but the Aura cannot place calls to the UCx. When I do a call routing test in Session Manager it says it will send it to the UCx but actual calls fail. Even though the Session shows the connection and link status as "UP" it doesnt look like it is actually sending IP traffic to the UCx. the Session Manager cannot ping the UCx but the network switch the Session Manager is on can ping the UCx so I know it isnt a network problem. There is also no firewall between the SM and UCx they are on the same network.

RE: UCx SIP trunk to Avaya Session Manager

Can you provide the failed call Traces from Aura to the UCx?

RE: UCx SIP trunk to Avaya Session Manager

(OP)
I changed/masked some IP info and the domain. 6###1 is the Aura Phone and 6###2 is the UCx phone. These are traces from my CM, I will get some from the SM as well but I found there is more info in the CM trace. First trace is UCx --> Aura that works. Second trace is Aura-->UCx that fails.

LIST TRACE – Call from UCx to Aura (completed good)

time data

08:54:54 TRACE STARTED 07/08/2022 CM Release String cold-01.0.890.0-27348
08:54:59 SIP<INVITE sip:6###1@domain.com SIP/2.0
08:54:59 Call-ID: 5c344e1a357f12a31578e8aa763b49d7@domain.com
08:54:59 Calling party trunk-group 600(SIP Trunk) member 156 cid 0x111e
08:54:59 Calling Number & Name 6###2 UCx Phone
08:54:59 dial 6###1
08:54:59 term station 6###1 cid 0x111e
08:54:59 dial 6###1
08:54:59 term trunk-group 600(SIP Trunk) cid 0x111f
08:54:59 dial 6###1
08:54:59 route-pattern 100 preference 1 location ALL cid 0x111f
08:54:59 seize trunk-group 600(SIP Trunk) member 26 cid 0x111f
08:54:59 Calling Number & Name 6###2 UCx Phone
08:54:59 SIP>INVITE sip:6###1@domain.com SIP/2.0
08:54:59 Call-ID: f034de50fecd41ec99a60c298c80cb
08:54:59 Setup digits 6###1
08:54:59 Calling Number & Name 6###2 UCx Phone
08:54:59 SIP<SIP/2.0 100 Trying
08:54:59 Call-ID: f034de50fecd41ec99a60c298c80cb
08:54:59 Proceed trunk-group 600(SIP Trunk) member 26 cid 0x111f
08:54:59 SIP<SIP/2.0 180 Ringing
08:54:59 Call-ID: f034de50fecd41ec99a60c298c80cb
08:54:59 SIP>SIP/2.0 180 Ringing
08:54:59 Call-ID: 5c344e1a357f12a31578e8aa763b49d7@domain.com
08:54:59 ring station 6###1 cid 0x111e
08:54:59 Alert trunk-group 600(SIP Trunk) member 26 cid 0x111f
08:54:59 Alerting party uses private-numbering
08:54:59 G711MU ss:off ps:20
rgn:2 [###.###.106.29]:13980
rgn:2 [###.###.144.42]:2060
08:54:59 xoip options: fax:T38 modem:PT tty:US uid:0x500196
xoip ip: [###.###.144.42]:2060
08:55:02 SIP<SIP/2.0 200 OK
08:55:02 Call-ID: f034de50fecd41ec99a60c298c80cb
08:55:02 SIP>ACK sips:6###1@###.###.80.235:28804;transport=tls;gsid=f
08:55:02 SIP>0341a60-fecd-11ec-9b5d-000c29f6eeee;av-iptol;asm=1 SIP/
08:55:02 SIP>2.0
08:55:02 Call-ID: f034de50fecd41ec99a60c298c80cb
08:55:02 SIP>SIP/2.0 200 OK
08:55:02 Call-ID: 5c344e1a357f12a31578e8aa763b49d7@domain.com
08:55:02 active station 6###1 cid 0x111e
08:55:02 Connected party uses private-numbering
08:55:02 SIP<ACK sip:6###1@###.###.191.30:5061;transport=tls;asm=1;ep
08:55:02 SIP<v=%3Csips:+1208526###1%40domain.com%3Bgr%3D746199641f0b226
08:55:02 SIP<fd260b80ac3633459%3E SIP/2.0
08:55:02 Call-ID: 5c344e1a357f12a31578e8aa763b49d7@domain.com
08:55:02 SIP>INVITE sip:6###2@###.###.106.29:5060;gsid=f0341a60-fecd-
08:55:02 SIP>11ec-9b5d-000c29f6eeee;asm=1 SIP/2.0
08:55:02 Call-ID: 5c344e1a357f12a31578e8aa763b49d7@domain.com
08:55:02 SIP<SIP/2.0 100 Trying
08:55:02 Call-ID: 5c344e1a357f12a31578e8aa763b49d7@domain.com
08:55:02 SIP<SIP/2.0 200 OK
08:55:02 Call-ID: 5c344e1a357f12a31578e8aa763b49d7@domain.com
08:55:02 SIP>INVITE sips:6###1@###.###.80.235:28804;transport=tls;gsi
08:55:02 SIP>d=f0341a60-fecd-11ec-9b5d-000c29f6eeee;av-iptol;asm=1 S
08:55:02 SIP>IP/2.0
08:55:02 Call-ID: f034de50fecd41ec99a60c298c80cb
08:55:02 SIP<SIP/2.0 100 Trying
08:55:02 Call-ID: f034de50fecd41ec99a60c298c80cb
08:55:02 SIP<SIP/2.0 200 OK
08:55:02 Call-ID: 5c344e1a357f12a31578e8aa763b49d7@domain.com
08:55:02 SIP<SIP/2.0 200 OK
08:55:02 Call-ID: f034de50fecd41ec99a60c298c80cb
08:55:02 SIP>ACK sips:6###1@###.###.80.235:28804;transport=tls;gsid=f
08:55:02 SIP>0341a60-fecd-11ec-9b5d-000c29f6eeee;asm=1 SIP/2.0
08:55:02 Call-ID: f034de50fecd41ec99a60c298c80cb
08:55:02 SIP>ACK sip:6###2@###.###.106.29:5060;gsid=f0341a60-fecd-11e
08:55:02 SIP>c-9b5d-000c29f6eeee;asm=1 SIP/2.0
08:55:02 Call-ID: 5c344e1a357f12a31578e8aa763b49d7@domain.com
08:55:05 SIP<BYE sip:6###2@###.###.191.30:5061;transport=tls;asm=1 SI
08:55:05 SIP<P/2.0
08:55:05 Call-ID: f034de50fecd41ec99a60c298c80cb
08:55:05 SIP>SIP/2.0 200 OK
08:55:05 Call-ID: f034de50fecd41ec99a60c298c80cb
08:55:05 SIP>BYE sip:6###2@###.###.106.29:5060;gsid=f0341a60-fecd-11e
08:55:05 SIP>c-9b5d-000c29f6eeee;asm=1 SIP/2.0
08:55:05 Call-ID: 5c344e1a357f12a31578e8aa763b49d7@domain.com
08:55:05 idle station 6###1 cid 0x111e
----------------------------------------------------------------------------------
LIST TRACE Call from Aura to UCx (Failed)

time data

08:56:39 TRACE STARTED 07/08/2022 CM Release String cold-01.0.890.0-27348
08:56:43 SIP<INVITE sips:6###1@domain.com;avaya-cm-fnu=off-hook SIP/2.0
08:56:43 Call-ID: a57_62c845ab-49c30b90254a41x2h5x3o1gx32531d_I6
08:56:43 8746
08:56:43 SIP>SIP/2.0 183 Session Progress
08:56:43 Call-ID: a57_62c845ab-49c30b90254a41x2h5x3o1gx32531d_I6
08:56:43 8746
08:56:43 active station 6###1 cid 0x1123
08:56:43 Calling party uses private-numbering
08:56:43 SIP>SIP/2.0 484 Address Incomplete
08:56:43 Call-ID: a57_62c845ab-49c30b90254a41x2h5x3o1gx32531d_I6
08:56:43 8746
08:56:43 SIP<INVITE sips:6###2@domain.com SIP/2.0
08:56:43 Call-ID: a57_62c845ab-49c30b90254a41x2h5x3o1gx32531d_I6
08:56:43 8746
08:56:43 SIP>SIP/2.0 100 Trying
08:56:43 Call-ID: a57_62c845ab-49c30b90254a41x2h5x3o1gx32531d_I6
08:56:43 8746
08:56:43 dial 6###2 route:UDP|AAR
08:56:43 term trunk-group 600(SIP Trunk) cid 0x1123
08:56:43 dial 6###2 route:UDP|AAR
08:56:43 route-pattern 100 preference 1 location 10/ALL cid 0x1123
08:56:43 seize trunk-group 600(SIP Trunk) member 28 cid 0x1123
08:56:43 Calling Number & Name 6###1 AURA USER
08:56:43 SIP>INVITE sip:6###2@domain.com SIP/2.0
08:56:43 Call-ID: 2e793184fece41ec9a60c298c80cb
08:56:43 Setup digits 6###2
08:56:43 Calling Number & Name 6###1 AURA USER
08:56:43 SIP<ACK sips:6###1@domain.com;avaya-cm-fnu=off-hook SIP/2.0
08:56:43 Call-ID: a57_62c845ab-49c30b90254a41x2h5x3o1gx32531d_I6
08:56:43 8746
08:56:43 SIP<SIP/2.0 100 Trying
08:56:43 Call-ID: 2e793184fece41ec9a60c298c80cb
08:56:43 Proceed trunk-group 600(SIP Trunk) member 28 cid 0x1123
08:56:43 SIP<SIP/2.0 500 Service Unavailable
08:56:43 Call-ID: 2e793184fece41ec9a60c298c80cb
08:56:43 SIP>ACK sip:6###2@domain.com SIP/2.0
08:56:43 Call-ID: 2e793184fece41ec9a60c298c80cb
08:56:43 denial event 1191: Network failure D1=0x9e70 D2=0x26
08:56:43 route-pattern 100 preference 1 location 10/ALL cid 0x1123
08:56:43 dial 6###2 route:UDP|AAR
08:56:43 term trunk-group 601 cid 0x1123
08:56:43 dial 6###2 route:UDP|AAR
08:56:43 route-pattern 100 preference 2 location 10/ALL cid 0x1123
08:56:43 seize trunk-group 601 member 9 cid 0x1123
08:56:43 Calling Number & Name 6###1 AURA USER
08:56:43 INVITE going via Sig Grp 600(SIP Trunk), ignoring called number routing
08:56:43 SIP>INVITE sips:6###2@domain.com SIP/2.0
08:56:43 Call-ID: 2e89938afece41ec9a90c298c80cb
08:56:43 Setup digits 6###2
08:56:43 Calling Number & Name 6###1 AURA USER
08:56:43 SIP<SIP/2.0 100 Trying
08:56:43 Call-ID: 2e89938afece41ec9a90c298c80cb
08:56:43 Proceed trunk-group 601 member 9 cid 0x1123
08:56:43 SIP<SIP/2.0 480 SIPS Not Allowed
08:56:43 Call-ID: 2e89938afece41ec9a90c298c80cb
08:56:43 SIP>ACK sips:6###2@domain.com SIP/2.0
08:56:43 Call-ID: 2e89938afece41ec9a90c298c80cb
08:56:44 denial event 1191: Network failure D1=0x9e70 D2=0x26
08:56:44 term trunk-group 600(SIP Trunk) cid 0x1123
08:56:44 route-pattern 100 preference 2 location 10/ALL cid 0x1123
08:56:44 dial 6###2 route:UDP|AAR
08:56:44 term trunk-group 602 cid 0x1123
08:56:44 dial 6###2 route:UDP|AAR
08:56:44 route-pattern 100 preference 3 location 10/ALL cid 0x1123
08:56:44 seize trunk-group 602 member 75 cid 0x1123
08:56:44 Calling Number & Name 6###1 AURA USER
08:56:44 SIP>INVITE sip:6###2@domain.com SIP/2.0
08:56:44 Call-ID: 2ea52dcfece41ec9af0c298c80cb
08:56:44 Setup digits 6###2
08:56:44 Calling Number & Name 6###1 AURA USER
08:56:44 SIP<SIP/2.0 100 Trying
08:56:44 Call-ID: 2ea52dcfece41ec9af0c298c80cb
08:56:44 Proceed trunk-group 602 member 75 cid 0x1123
08:56:44 SIP<SIP/2.0 500 Service Unavailable
08:56:44 Call-ID: 2ea52dcfece41ec9af0c298c80cb
08:56:44 SIP>ACK sip:6###2@domain.com SIP/2.0
08:56:44 Call-ID: 2ea52dcfece41ec9af0c298c80cb
08:56:44 denial event 1191: Network failure D1=0x9e70 D2=0x26
08:56:44 term trunk-group 600(SIP Trunk) cid 0x1123
08:56:44 route-pattern 100 preference 3 location 10/ALL cid 0x1123
08:56:44 dial 6###2 route:UDP|AAR
08:56:44 term trunk-group 603 cid 0x1123
08:56:44 dial 6###2 route:UDP|AAR
08:56:44 route-pattern 100 preference 4 location 10/ALL cid 0x1123
08:56:44 seize trunk-group 603 member 98 cid 0x1123
08:56:44 Calling Number & Name 6###1 AURA USER
08:56:44 INVITE going via Sig Grp 600(SIP Trunk), ignoring called number routing
08:56:44 SIP>INVITE sip:6###2@domain.com SIP/2.0
08:56:44 Call-ID: 2eba68fcfece41ec9a120c298c80cb
08:56:44 Setup digits 6###2
08:56:44 Calling Number & Name 6###1 AURA USER
08:56:44 SIP<SIP/2.0 100 Trying
08:56:44 Call-ID: 2eba68fcfece41ec9a120c298c80cb
08:56:44 Proceed trunk-group 603 member 98 cid 0x1123
08:56:44 SIP<SIP/2.0 500 Service Unavailable
08:56:44 Call-ID: 2eba68fcfece41ec9a120c298c80cb
08:56:44 SIP>ACK sip:6###2@domain.com SIP/2.0
08:56:44 Call-ID: 2eba68fcfece41ec9a120c298c80cb
08:56:44 denial event 1191: Network failure D1=0x9e70 D2=0x26
08:56:44 term trunk-group 600(SIP Trunk) cid 0x1123
08:56:44 route-pattern 100 preference 4 location 10/ALL cid 0x1123
08:56:44 dial 6###2 route:UDP|AAR
08:56:44 term trunk-group 604 cid 0x1123
08:56:44 dial 6###2 route:UDP|AAR
08:56:44 route-pattern 100 preference 5 location 10/ALL cid 0x1123
08:56:44 seize trunk-group 604 member 202 cid 0x1123
08:56:44 Calling Number & Name 6###1 AURA USER
08:56:44 SIP>INVITE sip:6###2@domain.com SIP/2.0
08:56:44 Call-ID: 2ecfc58fece41ec9a150c298c80cb
08:56:44 Setup digits 6###2
08:56:44 Calling Number & Name 6###1 AURA USER
08:56:44 SIP<SIP/2.0 100 Trying
08:56:44 Call-ID: 2ecfc58fece41ec9a150c298c80cb
08:56:44 Proceed trunk-group 604 member 202 cid 0x1123
08:56:44 SIP<SIP/2.0 500 Service Unavailable
08:56:44 Call-ID: 2ecfc58fece41ec9a150c298c80cb
08:56:44 SIP>ACK sip:6###2@domain.com SIP/2.0
08:56:44 Call-ID: 2ecfc58fece41ec9a150c298c80cb
08:56:44 denial event 1191: Network failure D1=0x9e70 D2=0x26
08:56:44 term trunk-group 600(SIP Trunk) cid 0x1123
08:56:44 route-pattern 100 preference 5 location 10/ALL cid 0x1123
08:56:44 dial 6###2 route:UDP|AAR
08:56:44 term trunk-group 605 cid 0x1123
08:56:44 dial 6###2 route:UDP|AAR
08:56:44 route-pattern 100 preference 6 location 10/ALL cid 0x1123
08:56:44 seize trunk-group 605 member 77 cid 0x1123
08:56:44 Calling Number & Name 6###1 AURA USER
08:56:44 INVITE going via Sig Grp 600(SIP Trunk), ignoring called number routing
08:56:44 SIP>INVITE sip:6###2@domain.com SIP/2.0
08:56:44 Call-ID: 2ee51b10fece41ec9a180c298c80cb
08:56:44 Setup digits 6###2
08:56:44 Calling Number & Name 6###1 AURA USER
08:56:44 SIP<SIP/2.0 100 Trying
08:56:44 Call-ID: 2ee51b10fece41ec9a180c298c80cb
08:56:44 Proceed trunk-group 605 member 77 cid 0x1123
08:56:44 SIP<SIP/2.0 500 Service Unavailable
08:56:44 Call-ID: 2ee51b10fece41ec9a180c298c80cb
08:56:44 SIP>ACK sip:6###2@domain.com SIP/2.0
08:56:44 Call-ID: 2ee51b10fece41ec9a180c298c80cb
08:56:44 idle trunk-group 605 member 77 cid 0x1123
08:56:44 SIP>SIP/2.0 500 Service Unavailable
08:56:44 Call-ID: a57_62c845ab-49c30b90254a41x2h5x3o1gx32531d_I6
08:56:44 8746
08:56:44 idle station 6###1 cid 0x1123

RE: UCx SIP trunk to Avaya Session Manager

(OP)
Here are the SM traces. Again I have masked domain and IP info. 6AURA is the Aura phone and 6UCX is the UCx phone. First trace is a completed good call UCx-->Aura and the second is failed Aura-->UCx
On the failed attempt the Aura tries to hand the call off to a different SIP entity when it cant reach the UCx.
---------------Good call from UCx to Aura----------------------
UCX2930 | SM100 | CM | 6###1 Aura Phone
21:36.0 │◄──Trying── │ │ │ (48) 100 Trying
21:36.0 │ │──INVITE──► │ │ (48) T:6Aura F:6UCX U:6Aura P:imsterm
21:36.0 │ │◄──Trying── │ │ (48) 100 Trying
21:36.0 │ │◄──INVITE── │ │ (49) T:6Aura F:6UCX U:6Aura P:termdone
21:36.0 │ │──Trying──► │ │ (49) 100 Trying
21:36.0 │ │────────INV ITE────────► │ (49) T:+1208526Aura F:6UCX
21:36.0 │ │◄────────Tr ying──────── │ (49) 100 Trying
21:36.1 │ │◄────────Ri nging─────── │ (49) 180 Ringing
21:36.1 │ │──Ringing─► │ │ (49) 180 Ringing
21:36.1 │ │◄──Ringing─ │ │ (48) 180 Ringing
21:36.1 │◄──Ringing─ │ │ │ (48) 180 Ringing
21:39.9 │ │◄────────20 0 OK──────── │ (49) 200 OK (INVITE)
21:39.9 │ │──200 OK──► │ │ (49) 200 OK (INVITE)
21:39.9 │ │◄────ACK─── │ │ (49) sips:6Aura@###.###.80.235:28804
21:39.9 │ │──────────A CK─────────► │ (49) sips:6Aura@###.###.80.235:28804
21:39.9 │ │◄──PUBLISH─ │ │ (79) sips:6Aura@inl.gov
21:39.9 │ │◄──200 OK── │ │ (48) 200 OK (INVITE)
21:39.9 │◄──200 OK── │ │ │ (48) 200 OK (INVITE)
21:39.9 │────ACK───► │ │ │ (48) sip:6Aura@###.###.191.30:5061
21:39.9 │ │────ACK───► │ │ (48) sip:6Aura@###.###.191.30:5061
21:39.9 │ │◄──reINVIT─ │ │ (48) sip:6UCX@###.###.106.29:5060 F:6Aura U:6UCX
21:39.9 │ │──Trying──► │ │ (48) 100 Trying
21:39.9 │ │────────NOT IFY────────► │ (80) <sips:6Aura@inl.gov> Ev:dialog
21:39.9 │◄──reINVIT─ │ │ │ (48) sip:6UCX@###.###.106.29:5060 F:6Aura U:6UCX
21:39.9 │ │──200 OK──► │ │ (79) 200 OK (PUBLISH)
21:39.9 │──Trying──► │ │ │ (48) 100 Trying
21:39.9 │──200 OK──► │ │ │ (48) 200 OK (INVITE)
21:39.9 │ │──200 OK──► │ │ (48) 200 OK (INVITE)
21:39.9 │ │◄──reINVIT─ │ │ (49) T:6Aura F:6UCX
21:40.0 │ │──Trying──► │ │ (49) 100 Trying
21:40.0 │ │───────reIN VITE───────► │ (49) T:+1208526Aura F:6UCX
21:40.0 │ │◄────────20 0 OK──────── │ (80) 200 OK (NOTIFY)
21:40.0 │ │◄────────Tr ying──────── │ (49) 100 Trying
21:40.0 │──200 OK──► │ │ │ (48) 200 OK (INVITE)
21:40.0 │ │──200 OK──► │ │ (48) 200 OK (INVITE)
21:40.2 │ │◄────────20 0 OK──────── │ (49) 200 OK (INVITE)
21:40.2 │ │──200 OK──► │ │ (49) 200 OK (INVITE)
21:40.2 │ │◄────ACK─── │ │ (49) sips:6Aura@###.###.80.235:28804
21:40.2 │ │◄────ACK─── │ │ (48) sip:6UCX@###.###.106.29:5060
21:40.2 │ │──────────A CK─────────► │ (49) sips:6Aura@###.###.80.235:28804
21:40.2 │◄────ACK─── │ │ │ (48) sip:6UCX@###.###.106.29:5060
21:46.3 │ │◄────────── BYE───────── │ (49) sip:6UCX@###.###.191.30:5061
21:46.3 │ │──Proxy Aut henticatio─► │ (49) 407 Proxy Authentication Required
21:46.3 │ │◄────────── BYE───────── │ (49) sip:6UCX@###.###.191.30:5061
21:46.3 │ │────BYE───► │ │ (49) sip:6UCX@###.###.191.30:5061
21:46.3 │ │◄──200 OK── │ │ (49) 200 OK (BYE)
21:46.3 │ │◄──PUBLISH─ │ │ (125) sips:6Aura@inl.gov
21:46.3 │ │────────200 OK────────► │ (49) 200 OK (BYE)
21:46.3 │ │◄────BYE─── │ │ (48) sip:6UCX@###.###.106.29:5060
21:46.3 │ │────────NOT IFY────────► │ (80) <sips:6Aura@inl.gov> Ev:dialog
21:46.3 │ │──200 OK──► │ │ (125) 200 OK (PUBLISH)
21:46.3 │◄────BYE─── │ │ │ (48) sip:6UCX@###.###.106.29:5060
21:46.3 │──200 OK──► │ │ │ (48) 200 OK (BYE)
21:46.3 │ │──200 OK──► │ │ (48) 200 OK (BYE)
21:46.3 │ │◄────────20 0 OK──────── │ (80) 200 OK (NOTIFY)

---------------------Failed call from Aura to UCx----------------------------
6###1 | SM100 | CM01 | SIP Entity not Ucx
31:06.1 │──INVITE──► │ │ │ (24) sips:6Aura@domain.com
31:06.1 │◄──Trying── │ │ │ (24) 100 Trying
31:06.1 │◄──Proxy A─ │ │ │ (24) 407 Proxy Authentication Required
31:06.1 │────ACK───► │ │ │ (24) sips:6Aura@domain.com
31:06.2 │──INVITE──► │ │ │ (24) sips:6Aura@domain.com
31:06.2 │◄──Trying── │ │ │ (24) 100 Trying
31:06.2 │ │──INVITE──► │ │ (24) sips:6Aura@domain.com P:imsorig
31:06.2 │ │◄──Trying── │ │ (24) 100 Trying
31:06.2 │ │◄──Session─ │ │ (24) 183 Session Progress
31:06.2 │ │◄──PUBLISH─ │ │ (26) sips:6Aura@domain.com
31:06.2 │◄──NOTIFY── │ │ │ (27) <sips:6Aura@domain.com> Ev:dialog
31:06.2 │ │──200 OK──► │ │ (26) 200 OK (PUBLISH)
31:06.2 │◄──Session─ │ │ │ (24) 183 Session Progress
31:06.2 │──200 OK──► │ │ │ (27) 200 OK (NOTIFY)
31:06.3 │──INVITE──► │ │ │ (24) sips:6UCX@domain.com
31:06.3 │◄──Trying── │ │ │ (24) 100 Trying
31:06.3 │◄──Proxy A─ │ │ │ (24) 407 Proxy Authentication Required
31:06.3 │────ACK───► │ │ │ (24) sips:6UCX@domain.com
31:06.3 │──INVITE──► │ │ │ (24) sips:6UCX@domain.com
31:06.4 │◄──Trying── │ │ │ (24) 100 Trying
31:06.4 │ │──INVITE──► │ │ (24) sips:6UCX@domain.com P:imsorig
31:06.4 │ │◄──Address─ │ │ (24) 484 Address Incomplete
31:06.4 │ │◄──Trying── │ │ (24) 100 Trying
31:06.4 │ │────ACK───► │ │ (24) sips:6Aura@domain.com
31:06.4 │◄──Address─ │ │ │ (24) 484 Address Incomplete
31:06.4 │ │◄──INVITE── │ │ (28) T:6UCX F:6Aura U:6UCX P:origdone
31:06.4 │ │──Trying──► │ │ (28) 100 Trying
31:06.4 │ │────────INV ITE────────► │ (28) T:6UCX F:6Aura U:6UCX P:terminating
31:06.4 │ │◄────────Tr ying──────── │ (28) 100 Trying
31:06.4 │ │◄────────IN VITE──────── │ (29) T:6UCX;phone-context=cdp.udp F:6Aura;phone-context=UnknownUnknown U:6UCX;phone-context=cdp.udp
31:06.4 │ │────────Try ing────────► │ (29) 100 Trying
31:06.4 │ │────────INV ITE────────► │ (29) T:6UCX F:6Aura;phone-context=UnknownUnknown U:6UCX P:terminating
31:06.4 │ │◄────────Tr ying──────── │ (29) 100 Trying
31:06.4 │────ACK───► │ │ │ (24) sips:6Aura@domain.com
31:06.4 │ │◄──Service Unavailable─ │ (29) 503 Service Unavailable
31:06.4 │ │──────────A CK─────────► │ (29) sip:6UCX@domain.com
31:06.4 │ │──Service U navailable─► │ (29) 500 Service Unavailable
31:06.4 │ │◄────────── ACK───────── │ (29) sip:6UCX
31:06.5 │ │◄──Service Unavailable─ │ (28) 503 Service Unavailable
31:06.5 │ │──────────A CK─────────► │ (28) sip:6UCX@domain.com
31:06.5 │ │──Service─► │ │ (28) 500 Service Unavailable
31:06.5 │ │◄────ACK─── │ │ (28) sip:6UCX@domain.com
31:06.5 │ │◄──INVITE── │ │ (31) sips:6UCX@domain.com P:origdone
31:06.5 │ │──Trying──► │ │ (31) 100 Tryin
31:06.5 │ │◄────ACK─── │ │ (31) sips:6UCX@domain.com
31:06.5 │ │◄──INVITE── │ │ (32) T:6UCX F:6Aura U:6UCX P:origdone
31:06.5 │ │──Trying──► │ │ (32) 100 Trying
31:06.5 │ │────────INV ITE────────► │ (32) T:6UCX F:6Aura U:6UCX P:terminating
31:06.5 │ │◄────────Tr ying──────── │ (32) 100 Trying
31:06.6 │ │◄────────IN VITE──────── │ (33) T:6UCX;phone-context=cdp.udp F:6Aura;phone-context=UnknownUnknown U:6UCX;phone-context=cdp.udp
31:06.6 │ │────────Try ing────────► │ (33) 100 Trying
31:06.6 │ │────────INV ITE────────► │ (33) T:6UCX F:6Aura;phone-context=UnknownUnknown U:6UCX P:terminating
31:06.6 │ │◄────────Tr ying──────── │ (33) 100 Trying
31:06.6 │ │◄──Service Unavailable─ │ (33) 503 Service Unavailable
31:06.6 │ │──────────A CK─────────► │ (33) sip:6UCX@domain.com
31:06.6 │ │──Service U navailable─► │ (33) 500 Service Unavailable
31:06.6 │ │◄────────── ACK───────── │ (33) sip:6UCX
31:06.6 │ │◄──Service Unavailable─ │ (32) 503 Service Unavailable
31:06.6 │ │──────────A CK─────────► │ (32) sip:6UCX@domain.com
31:06.6 │ │──Service─► │ │ (32) 500 Service Unavailable
31:06.6 │ │◄────ACK─── │ │ (32) sip:6UCX@domain.com
31:06.6 │ │◄──INVITE── │ │ (34) T:6UCX F:6Aura U:6UCX P:origdone
31:06.7 │ │──Trying──► │ │ (34) 100 Trying
31:06.7 │ │────────INV ITE────────► │ (34) T:6UCX F:6Aura U:6UCX P:terminating
31:06.7 │ │◄────────Tr ying──────── │ (34) 100 Trying
31:06.7 │ │◄────────IN VITE──────── │ (36) T:6UCX;phone-context=cdp.udp F:6Aura;phone-context=UnknownUnknown U:6UCX;phone-context=cdp.udp
31:06.7 │ │────────Try ing────────► │ (36) 100 Trying
31:06.7 │ │────────INV ITE────────► │ (36) T:6UCX F:6Aura;phone-context=UnknownUnknown U:6UCX P:terminating
31:06.7 │ │◄────────Tr ying──────── │ (36) 100 Trying
31:06.8 │ │◄──Service Unavailable─ │ (36) 503 Service Unavailable
31:06.8 │ │──────────A CK─────────► │ (36) sip:6UCX@domain.com
31:06.8 │ │──Service U navailable─► │ (36) 500 Service Unavailable
31:06.8 │ │◄────────── ACK───────── │ (36) sip:6UCX
31:06.8 │ │◄──Service Unavailable─ │ (34) 503 Service Unavailable
31:06.8 │ │──────────A CK─────────► │ (34) sip:6UCX@domain.com
31:06.8 │ │──Service─► │ │ (34) 500 Service Unavailable
31:06.8 │ │◄────ACK─── │ │ (34) sip:6UCX@domain.com
31:06.8 │ │◄──INVITE── │ │ (37) T:6UCX F:6Aura U:6UCX P:origdone
31:06.8 │ │──Trying──► │ │ (37) 100 Trying
31:06.8 │ │────────INV ITE────────► │ (37) T:6UCX F:6Aura U:6UCX P:terminating
31:06.8 │ │◄────────Tr ying──────── │ (37) 100 Trying
31:06.9 │ │◄────────IN VITE──────── │ (40) T:6UCX;phone-context=cdp.udp F:6Aura;phone-context=UnknownUnknown U:6UCX;phone-context=cdp.udp
31:06.9 │ │────────Try ing────────► │ (40) 100 Trying
31:06.9 │ │────────INV ITE────────► │ (40) T:6UCX F:6Aura;phone-context=UnknownUnknown U:6UCX P:terminating
31:06.9 │ │◄────────Tr ying──────── │ (40) 100 Trying
31:06.9 │ │◄──Service Unavailable─ │ (40) 503 Service Unavailable
31:06.9 │ │──────────A CK─────────► │ (40) sip:6UCX@domain.com
31:06.9 │ │──Service U navailable─► │ (40) 500 Service Unavailable
31:06.9 │ │◄────────── ACK───────── │ (40) sip:6UCX
31:06.9 │ │◄──Service Unavailable─ │ (37) 503 Service Unavailable
31:06.9 │ │──────────A CK─────────► │ (37) sip:6UCX@domain.com
31:06.9 │ │──Service─► │ │ (37) 500 Service Unavailable
31:06.9 │ │◄────ACK─── │ │ (37) sip:6UCX@domain.com
31:06.9 │ │◄──INVITE── │ │ (41) T:6UCX F:6Aura U:6UCX P:origdone
31:07.0 │ │──Trying──► │ │ (41) 100 Trying
31:07.0 │ │────────INV ITE────────► │ (41) T:6UCX F:6Aura U:6UCX P:terminating
31:07.0 │ │◄────────Tr ying──────── │ (41) 100 Trying
31:07.0 │ │◄────────IN VITE──────── │ (42) T:6UCX;phone-context=cdp.udp F:6Aura;phone-context=UnknownUnknown U:6UCX;phone-context=cdp.udp
31:07.0 │ │────────Try ing────────► │ (42) 100 Trying
31:07.0 │ │────────INV ITE────────► │ (42) T:6UCX F:6Aura;phone-context=UnknownUnknown U:6UCX P:terminating
31:07.0 │ │◄────────Tr ying──────── │ (42) 100 Trying
31:07.0 │ │◄──Service Unavailable─ │ (42) 503 Service Unavailable
31:07.0 │ │──────────A CK─────────► │ (42) sip:6UCX@domain.com
31:07.0 │ │──Service U navailable─► │ (42) 500 Service Unavailable
31:07.0 │ │◄────────── ACK───────── │ (42) sip:6UCX
31:07.1 │ │◄──Service Unavailable─ │ (41) 503 Service Unavailable
31:07.1 │ │──────────A CK─────────► │ (41) sip:6UCX@domain.com
31:07.1 │ │──Service─► │ │ (41) 500 Service Unavailable
31:07.1 │ │◄────ACK─── │ │ (41) sip:6UCX@domain.com
31:07.1 │ │◄──INVITE── │ │ (43) T:6UCX F:6Aura U:6UCX P:origdone
31:07.1 │ │──Trying──► │ │ (43) 100 Trying
31:07.1 │ │────────INV ITE────────► │ (43) T:6UCX F:6Aura U:6UCX P:terminating
31:07.1 │ │◄────────Tr ying──────── │ (43) 100 Trying
31:07.1 │ │◄────────IN VITE──────── │ (44) T:6UCX;phone-context=cdp.udp F:6Aura;phone-context=UnknownUnknown U:6UCX;phone-context=cdp.udp
31:07.1 │ │────────Try ing────────► │ (44) 100 Trying
31:07.1 │ │────────INV ITE────────► │ (44) T:6UCX F:6Aura;phone-context=UnknownUnknown U:6UCX P:terminating
31:07.1 │ │◄────────Tr ying──────── │ (44) 100 Trying
31:07.2 │ │◄──Service Unavailable─ │ (44) 503 Service Unavailable
31:07.2 │ │──────────A CK─────────► │ (44) sip:6UCX@domain.com
31:07.2 │ │──Service U navailable─► │ (44) 500 Service Unavailable
31:07.2 │ │◄────────── ACK───────── │ (44) sip:6UCX
31:07.2 │ │◄──Service Unavailable─ │ (43) 503 Service Unavailable
31:07.2 │ │──────────A CK─────────► │ (43) sip:6UCX@domain.com
31:07.2 │ │──Service─► │ │ (43) 500 Service Unavailable
31:07.2 │ │◄────ACK─── │ │ (43) sip:6UCX@domain.com
31:07.2 │ │◄──Service─ │ │ (24) 500 Service Unavailable
31:07.2 │ │────ACK───► │ │ (24) sips:6UCX@domain.com
31:07.2 │ │◄──PUBLISH─ │ │ (45) sips:6Aura@domain.com
31:07.2 │◄──Service─ │ │ │ (24) 500 Service Unavailable
31:07.2 │◄──NOTIFY── │ │ │ (27) <sips:6Aura@domain.com> Ev:dialog
31:07.2 │ │──200 OK──► │ │ (45) 200 OK (PUBLISH)
31:07.2 │────ACK───► │ │ │ (24) sips:6UCX@domain.com
31:07.2 │──200 OK──► │ │ │ (27) 200 OK (NOTIFY)

RE: UCx SIP trunk to Avaya Session Manager

Thanks Alfordap Do you currently have anything configured in your Public unknown numbering table on the CM side? are you also able to share the configuration of your Trunk group, and signaling group?

RE: UCx SIP trunk to Avaya Session Manager

I know nothing about Aura but have connected SIP Trunks to Avaya Call Manager. Since they are both Avaya maybe they will be similar.
The Avaya CM prefers signaling over TCP not UDP.
In the UCx under SIP Settings / Advanced SIP settings enter tcpenable = yes in Other SIP settings. See if this does anything for you.
I am attaching a Document from our company that explains the setup for connecting UCx to Avaya CM.

Not sure if it will have any bearing on the Aura but worth a shot.

www.ucxdirect.com

RE: UCx SIP trunk to Avaya Session Manager

(OP)
The public unknown sends to the other NON-UCx SIP Entity in the failed call. I think it is treating it the same once it realizes it cant send a call to the UCx. I do have a dial pattern in for each extension I am trying to send to the UCx
I already have multiple other SIP Entities working just fine both TCP and UDP

Here is the signaling group.

SIGNALING GROUP

Group Number: 600 Group Type: sip
IMS Enabled? n Transport Method: tls
Q-SIP? n
IP Video? n Enforce SIPS URI for SRTP? n
Peer Detection Enabled? y Peer Server: SM Clustered? n
Prepend '+' to Outgoing Calling/Alerting/Diverting/Connected Public Numbers? y
Remove '+' from Incoming Called/Calling/Alerting/Diverting/Connected Numbers? n
Alert Incoming SIP Crisis Calls? n
Near-end Node Name: procr Far-end Node Name: ---FQDN---
Near-end Listen Port: 5061 Far-end Listen Port: 5061
Far-end Network Region: 241

Far-end Domain: inl.gov
Bypass If IP Threshold Exceeded? n
Incoming Dialog Loopbacks: eliminate RFC 3389 Comfort Noise? n
DTMF over IP: rtp-payload Direct IP-IP Audio Connections? y
Session Establishment Timer(min): 3 IP Audio Hairpinning? n
Enable Layer 3 Test? y Initial IP-IP Direct Media? n
H.323 Station Outgoing Direct Media? n Alternate Route Timer(sec): 6

LIMIT SIGNALING GROUP USAGE

Enable on the main Processor(s)? y

Enable on Survivable Processors (ESS and LSP): all

RE: UCx SIP trunk to Avaya Session Manager

(OP)
getsomesun1, Thanks for the document. I had thought about setting up the link to our CM instead of SM but we would prefer to use SM. I did try the TCP but this is UCX 7 and so I added this string to the Peer details (transport=tcp) and still did not work. I am thinking this is either a network setting on the UCx that doesnt send the traffic back correctly or on the SM.

Red Flag This Post

Please let us know here why this post is inappropriate. Reasons such as off-topic, duplicates, flames, illegal, vulgar, or students posting their homework.

Red Flag Submitted

Thank you for helping keep Tek-Tips Forums free from inappropriate posts.
The Tek-Tips staff will check this out and take appropriate action.

Reply To This Thread

Posting in the Tek-Tips forums is a member-only feature.

Click Here to join Tek-Tips and talk with other members! Already a Member? Login
Close Box

Join Tek-Tips® Today!

Join your peers on the Internet's largest technical computer professional community.
It's easy to join and it's free.

Here's Why Members Love Tek-Tips Forums:

Register now while it's still free!

Already a member? Close this window and log in.

Join Us             Close