Avaya extension on Android devices using CSipSimple?

[HBcity]

Has anyone had any luck with getting CSipSimple to work on a Android device? I already created the extension in Session Manager but have no idea how to configure CSipSimple on my Android tablet.

 

[fataldata]

Yes, I have it working on CM 6.0.1 over wifi to session manager.

I used the Advanced Account Setup
Put in the IP of session manager
Login was my extension
Password was the one I setup in the session manager user under "Communication Profile"

Created a station in CM
Had to setup OPS mapping in CM to send my extensions calls to session manager

 

[HBcity]

Hi Fataldata,

in advanced there are the following fields:

Acct. Name: what do I insert here?
Caller ID: what do I insert here?
Server: <-- I inserted the IP address of my System Manager
Username: <-- do I put the extension here?
Sip authentication ID: what do I insert here?
Password: use TCP (not UDP): Select UDP?
Proxy: leave blank

I create a SIP ext. on the Session Manager for this.

 

[kyle555]

I've gotten 3rd party free SIP clients working. Typically, I use traceSM in Session Manager to watch the register messages from an Avaya phone and compare/contrast with the 3rd party client.

To be honest, all you need is the Session Manager traffic IP (not the management IP), the username, the SIP domain, and the Communication Profile Password. Its just a guessing game of where you might need to put those things. Is your user 1234? Or 1234@yourdomain.com? Maybe user is 1234 and authID is 1234@yourdomain.com?

traceSM will at least let you see where in that app's setup that those values truly get into a register message.

 

[fataldata]

Acct. Name: Whatever you would like to refer to this account as?
Caller ID: Doesn't seem to matter I have not gotten this field to work, all caller ID is handled through Public Unknown.
Server: Session Manager SIP IP (not system manager)
Username: Yes I put the extension here. I believe this comes from the "Handle" on the users Communication Profile > Communication Address but as Kyle555 mentioned this can be determined with traces as well.
Sip authentication ID: Mine is blank to use the same as the Username. You could use the extension again i believe.
Password: This is the Users Communication Profile Password not the one from the Identity tab.
use TCP (not UDP): I like UDP
Proxy: blank

I create a SIP ext. on the Session Manager for this.

You create a user through System Manager > User Management > New

 

[HBcity]

I got it working! Well half way..
I did get the SIP ext. to register and when I dial the ext. on the device from a desk phone it does ring.

But I cannot make an outbound call from the device.
When I dial a 7 digit number I see on the screen sipthe 7 digits number)@ (ip address of the Session Manager) so it looks like this 915452522222@192.10.10.10

Is there a setting that needs to be configured for outbound dialing?

 

[fataldata]

Have you ever used a SIP endpoint (registered to Session Manager) to make a call in the past? If not you likely need to put the routing in Session Manager to tell it to route outbound calls to your CM where your trunks are, unless of course you have SIP trunks terminated to Session Manager. I know it sounds counter intuitive because the SIP endpoint is and OPS in CM but you need to tell Session Manager to route calls that begin with a 9 and have 12 digits (in your example) to your CM.

You can do this in System Manager Home>Elements>Routing>Dial Patterns

Assuming of course you have routing policies setup already.