Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations Mike Lewis on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

Session Manager / SIP Phone CDR

Status
Not open for further replies.

wpetilli

Technical User
May 17, 2011
1,877
US
I'm running a few SIP phones using the dual registration feature and need to be able to capture CDR from these phones. I have a 3rd party Call Accounting system and have looked at how to enable CDR on Session Manager, but this system only uses a port # and node-name/IP address that's setup in IP-Services. It doesn't have the option for a setting up a login, which ASM looks like it requires. Is anyone utilizing any creative way to pull this data from SM?

The only other thing I can do is run trunk reports since the SIP calls traverse CM to the PSTN, but that won't tell me down to an extension level.
 
Set up a trusted entity link between the two?

I you can do that and get them talking on the right ports you should be good.
 
Might need to add the extensions to the intra switch cdr table, change intra xxxx
 
Circling back on this. CDR is enabled on ASM with a password assigned to the CDR_User account. I currently do not have an adjunct that can be setup to access this directory in ASM, but I want to be able to pull the files off the box. The 'cust' account doesn't have access to this directory and the newer versions of ASM don't give access to the root account. Is there a way to get into these?
 
CM added local disk storage CDR once upon a time. It can either stream like in ip-services or save to disk and you make a FTP username and your application ftp's in, grabs new files, deletes them, etc. SM's structure is similar.

And then in 7.1 Avaya's "policy" is to expire passwords after 90 days on SM. Even the FTP one. And you need root to change it. And you can't change it from "not" expiring every 90 days. So even if you do get it working, it'll guaranteed break in 3 months.

SM has a spot in "tracer configuration" where you can make it syslog all sip messages to a remote destination.

Like HOMER

It's free as in beer, by some high up European telecom SIP guys, and with a built in parser for SM's syslog. Haven't had a chance to play with it, but there ya go.

And it'll give you signaling diagrams, MOS scores if you point RTCP at it, etc. Think of a poor man's Empirix or Oracle EOM. APIs to build whatever you want too. If that's your bag. Otherwise, if you just spin up an instance and don't put too much of that five nines planning into it, it's your hobby SIP machine.

You get what you pay for, but I didn't know this stuff was free.
 
Have began to tinker with getting HOMER installed.. definitely challenging to say the least.
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top