Questions about SMDR format

[KurpeusLondon]

Hi guys,

I've few issue working with SMDR format.

The call sequence identifier increment each time a controller emits a SMDR log regarding a specific call. IT works fine in most scenario but not for an inbound call on a specific ISDN trunk (A0083624 A then again A0083624 A and again A0083624 A, ...)


05/05 09:43:31 0000:00:16 T3121 **** P202 102 P202 R 8201 008 08004###### 4404519 A0083624 A
05/05 09:43:47 0000:00:16 T3121 **** P202 105 P202 R 8004 008 08004###### 4404519 A0083624 A
05/05 09:44:03 0000:00:00 T3121 **** P202 P202 U 8502 008 08004###### 4404519 A0083624 A
05/05 09:44:24 0000:00:28 T3121 0021 8502 4202 4100 4116 008 08004###### 4404519 A0083624 A


As a example, this incoming trunk works fine (SIP trunk) (A0033672 A then A0033672 B, then A0033672 C)

05/05 12:30:20 0000:00:54 T9001 0006 T08442###### 4404510 98782 X9999 003 08442###### 4404510 A0033672 A
05/05 12:30:20 0000:00:52 X9999 T08442###### 9878230 00000ASX9999 003 8442##### A0033672 B
05/05 12:30:20 0000:00:52 X9999 0006 T08442###### 98782300 2350 2008 008 08442###### 2300 A0033672 C


It is to note the difference between these two examples is they terminate on different controller and are different trunk (SIP vs ISDN)

I checked system option, SMDR option and CoS between trunks, I can find any reason why this does not increment.


Also, event if I turn all SMDR options to yes on the SMDR form, I can only get something like 165 characters when the help file says it goes up to 198 characters. I also noted few differences between the help file and the actual fields order.

My system is an ICP 3300 with MCD 4.1 SP1. I checked the latest patches (up to 4.2 SP1) but no mention to SMDR modification.

Any thought about what could cause this ?

Cheers,

 

[KurpeusLondon]

Ignore what I said about the 165 characters, it's just that the fields followings are empty

 

[Supernova99]

The first example you posted shows a call being presented to different ACD agents and it is not answered no tries the next
**** is no answer that is why the suffix A is always the same it is the same Trunk

where as

The second example shows a trunk calling on to IP trunking and that is why you get suffix A, B, C etc. (tandem trunk calling)

Share what you know - Learn what you don't

 

[KurpeusLondon]

I see,

That's not extactly the way I was hoping it works but thanks Supernova99