Avaya SES Question

[sliderplot]

Hello,

I am new to Avaya SES services and getting a fast busy signal when sending call to extension 8998. SIP sends 'invite' to xx.xx.xx.65 our SES server, when ACK SIP statement we get a denial because SIP is sending it to xx.xx.xx.65 SES server again which causes fast busy. ACK line should be set as 'sip:8998@xx.xx.xx.104 SIP/2.0' which is our development AVP service. Can not put the pieces together on where the configuration for extension 8998 to use the correct IP address for extension, can not figure out where extension 8998 is assembled with the correct IP xx.xx.xx.104 address instead of xx.xx.xx.65

Any help would be greatly helpful.

LIST TRACE
15:31:36 active station 6330 cid 0x265c
15:31:36 G711MU ssff ps:20
rgn:1 [xx.xx.xx.xx]:xxxxx
rgn:1 [xx.xx.x.xx]:xxxxx
15:31:45 SIP>INVITE sip:8998@xx.x.xx.65 SIP/2.0 (START OF SIP)
15:31:45 Call-ID: 80f0e38da155e6122c356f72e2300
15:31:45 dial 8998 route:UDP|AAR
15:31:45 term trunk-group 52 cid 0x265c
15:31:45 dial 8998 route:UDP|AAR
15:31:45 route-pattern 52 preference 1 location 1/ALL cid 0x265c
15:31:45 seize trunk-group 52 member 12 cid 0x265c
15:31:45 Setup digits 8998
15:31:45 Calling Number & Name 9727536330 Bruce Dana
15:31:45 SIP<SIP/2.0 100 Trying
15:31:45 Call-ID: 80f0e38da155e6122c356f72e2300
15:31:45 Proceed trunk-group 52 member 12 cid 0x265c
15:31:45 SIP<SIP/2.0 500 Server Internal Error
15:31:45 Call-ID: 80f0e38da155e6122c356f72e2300
15:31:45 SIP>ACK sip:8998@xx.xx.x.65 SIP/2.0 (THIS LINE HAVING ISSUES WITH)
15:31:45 Call-ID: 80f0e38da155e6122c356f72e2300
15:31:45 denial event 1192: Temporary failure D1=0x816d D2=0x229
15:31:45 idle trunk-group 52 member 12 cid 0x265c
15:31:47 idle station 6330 cid 0x265c

 

[janni78]

You get "500 Server Internal Error" from SES so guess the extension isn't setup properly there.

"Trying is the first step to failure..." - Homer

 

[sliderplot]

Thanks, would you be able to tell how I could verify this and other extensions are set up. Just a FYI, I started this position a couple of weeks again and members did tell me that these extensions were working three weeks ago. If you could direct me the steps to verify extensions are set up correctly and also how the SES assembles the extension with IP address.

 

[janni78]

In SES you need to setup a user and also add the extension to the CM in SES.

"Trying is the first step to failure..." - Homer

 

[sliderplot]

Hello,
Below are the options under 'user' tab and I have looked thru all tabs to try to find all extensions that have been set up. I have found about six extensions set up on SES but am still looking for about 25 more extensions that I can't find. I have looked under 'search registered device' and 'search registered users' and can not find all list extensions that I am being told should be set up. Are these the correct area under 'users' tab? Still trying learn and understand SES server, if you have any good manuals that to help me understand the full services would be great too.



User Administration

Add User Add a new user.
Edit Default User Profile Edit the default user profile.
Delete User Delete a user by user id.
Edit User Profile Edit a user by user id.
List Users List all users.
Update Password Change a password by user id.
Search Users Search for users.
Manage All Registered Users Apply to all registered users
Search Registered Devices Search for registered and provisioned devices.
Search Registered Users Search for registered and provisioned users.

 

[gwebster]

Look on support.avaya.com for documentation based upon the release you are running. SES is old technology which has been superseded by Session Manager.

 

[janni78]

All SIP accounts should show under "List all users".
All extensions should also be tied to the correct Communication Manager in SES.


"Search Registered Users" only show the devices that are currently registered to SES.



"Trying is the first step to failure..." - Homer

 

[immike]

SIP is a pain to setup as it is not native to CM, make sure route patterns are setup properly for your SIP station. You might want to look at your network regions, your call seems to stay in region 1.

It could also be a licensing issue too, some BP's installed with 1 basic license.

I would ssh into the SES, use "traceSES". this is a list trace from the SES, it will give you a bit more information too.


-Mike