QUINTUM INTEGRATION

[tech_john]

Hi to All,

Good day,

Am treing to configure quintum AFM200 for 3CX.

1.) i tried to setup extension for quintum and registered --- successfull
2.) i tried to setup extension x-lite and registered --- successfull
3.) i tried to setup extesion for quintum as FXO/CO and registered --- successfull
4.) using the 4 as dialing out --- successfull
5.) i tried calling receptionist from x-lite ---- successfull
6.) i tried calling receptionist from quintum extention --- successfull
7.) from PSTN>quintum>3CX> receptionist/ip extension --- failed

Hope you can give me some hints how to configure the parameters.

Thanks in advance.

 

[dmatthysen]

Did you succeed??

 

[charlief]

I am trying to do the same on a Quintum ASM400 (which for all intensive purposes is the same. Just started. I will let you know how I get on. Any progress with you?

 

[charlief]

Hi tech_john (or anybody who can help)

I have Quintum ASM400 and I want to use it to connect to PSTN.

I get this (see below). Does anyone know the config parameters for a Quintum?

I am using a Lnksys PAP2 as the extension and I can dial out to Voip OK, but the Quintum has me defeated! Unsupported Media type?!


01:07:34.406 Call::Terminate [CM503008]: Call(10): Call is terminated
01:07:34.359 Call::RouteFailed [CM503015]: Call(10): Attempt to reach [sip:[email protected]] failed. Reason: Unsupported Media Type
01:07:34.359 CallLeg:nFailure [CM503003]: Call(10): Call to sip:[email protected]:5060 has failed; Cause: 415 Unsupported Media Type; from IP:192.168.0.16:5060
01:07:34.093 CallLeg:nFailure [CM503003]: Call(10): Call to sip:[email protected]:5060 has failed; Cause: 415 Unsupported Media Type; from IP:192.168.0.16:5060
01:07:33.843 CallLeg:nFailure [CM503003]: Call(10): Call to sip:[email protected]:5060 has failed; Cause: 415 Unsupported Media Type; from IP:192.168.0.16:5060
01:07:33.578 CallLeg:nFailure [CM503003]: Call(10): Call to sip:[email protected]:5060 has failed; Cause: 415 Unsupported Media Type; from IP:192.168.0.16:5060
01:07:33.359 CallCtrl:nSelectRouteReq [CM503004]: Call(10): Calling: PSTNline:08232721059@(Ln.10001@Quintum)@[Dev:sip:[email protected]:5060, Dev:sip:[email protected]:5061, Dev:sip:[email protected]:5062, Dev:sip:[email protected]:5063]
01:07:33.343 CallCtrl:nSelectRouteReq [CM503010]: Making route(s) to [sip:[email protected]]
01:07:33.343 Extension:rintEndpointInfo [CM505001]: Ext.10: Device info: Device Not Identified: User Agent not matched; Capabilities:[reinvite, replaces, able-no-sdp, recvonly] UserAgent: [Linksys/PAP2-3.1.22(LS)] Transport: [sip:192.168.0.2:5060]
01:07:33.312 CallCtrl:nIncomingCall [CM503001]: Call(10): Incoming call from Ext.10 to [sip:[email protected]]

 

[dmatthysen]

I am trying to do the same on a Quintum ASM400 (which for all intensive purposes is the same. Just started. I will let you know how I get on. Any progress with you?

PM me; I have a working config. I`m a Quintum Engineer and can assist.

 

[hanserian]

Dears,

Am facing the same problem if anyone can upload or send me the config for Quintum ASM200 for 3CX would be highly appreciative.

Regards,

Hagop

 

[N_G]

We dont support Quintum with 3CX, its best you use a supported gateway.

 

[charlief]

By the way, I have the ASM400 up and running perfectly now, so if anyone needs the config just PM me.

 

[heinbense]

Hi charlief, can you send me the config please?

 

[xavcastro]

Hi charlief. Can you send me the config for the ASM 400 and a brief instrtuctions on how to set it up for 3cx. Thanks.