AVAYA CTI-Application > CM > SIP Trunks to Session Manager

[DanielAT]

Hello all,

hopefully you'll have some tipps for us.

We're using a self-developed application for our agents. This application is using clip no screening to transmit different ANI - depending on the customer or project.
Everything works well as long we use E1's. Now we have to migrate to SIP and this function stopped working.

As long we modify the ANI via this application and route the outbound calls via SIP no number will be displayed with the called party.
It's working fine when we modify the public-unknown-details and route the call (same path) via SIP. Anonymous will be displayed just while using the application.

Our developer told me that he's using the ASAIUUI and a Prefix "*!", then he inform the CM to use a specific VDN > vector for makecall.

Our Setup:

Doesn't work:
Self-developed app > AES 7> CM 7 (VDN/Vector) > SIP Trunk > Session Manager > SBCE > SIP Carrier

Works fine:
Self-developed app > AES 7> CM 7 (VDN/Vector)> E1 Trunk > PSTN​

Is there perhaps a different way to send the needed informations to the SM instead to the E1 necessary? Would it be possible that "*!" isn't the correct prefix for SIP?
We tested already the UUI-Treatment Shared and Service-Provider but without success.

Any clue what we're doing wrong?

Many thanks for any tipps.

Cheers,
Daniel

 

[kyle555]

TraceSM and traceSBC

See what comes from CM to SM - maybe your problem is there.
See what comes from SM to SBC - maybe your problem is there
See what comes from SBC to carrier - maybe your problem is there

Maybe nothing changed except the SIP carrier doesn't let you send out anything you want.