forwarding rules from extern

[MarcelvanKuilenburg]

Hi there,

working with v8 16calls i tried to make a ring group wich should make to ring to extensions (100 and 101). by making forwarding rule from ext. 100 to group 802 this forwarding will only work if i make it for RULE TYPE forward all. if I use for example no answer as a rule, I do get the standard voice of 'the person you try to reach is not responding' speak message.
this is only the case with external calls. Internal call are no problem. they function as expected

anyone an idea

M

 

[leejor]

So you have , say, ring group 800, with extensions 100 and 101, and you now want calls in that ring group (ringing 100 to then go to a second ring group 802), is this correct? When a call is presented to a ring group, one extension doesn't "own it". You have to specify in the ring group where to send a call that isn't answered. Are you talking about calls made to 100 or calls ringing 100 but made to the first ring group?

 

[mfm]

Why are you passing the call to an extension and then the ring group, do you want to give extension 100 a chance to pick p the call before you pass it on? Please try and be a bit more clear so I may be able to offer you some kind of indication of the correct settings.

 

[MarcelvanKuilenburg]

First of all thanks for the reaction

during office hours I would like to ring ext 100 and 101 together.
during out of office hours I would like to have the digital receptionist (virt.ext. 801) to ring.

The trunk is connected to ext. 100. from ext. 100 all calls are going to group 802 (100 and 101). If I make rule type other than forward all I do get the message
"the person you are trying to reach is not available. please leave a message"
So I can not make rule type "no answer" or "busy" because I get the above mentioned message.

I want that f.e. no answering goes to virt. ext 801 and busy to virt. ext. 803 which I can not do because if I use this forward options I get the above mentioned message.

incoming trunk1--> ext 100---> rule type 'forward all' virt. 802 ----> virt. 801 dig.recept. (the last step does not work)

What I want: incoming trunk1-->ringing 100 and 101 (ext group 802? (100 and 101)
---> rule type 'no answering' --> virt. ext. 800 (ringing whole office)
---> rule type 'busy' ---> virt. ext. 801 (dig.recept)

As mentioned i do not get this to work because any other rule type than 'forward all' makes the above mentioned message starts to play.

ext. 100 is the ext. which is put in general rules as incoming.

I hope my problem is clearer.

thx
M.

 

[mfm]

Hi,

Why havent you connected the trunk to go to the ring group during office hours and to the DR during out of office hours? Why are you passing to an extension are you looking for specfic hours?

 

[MarcelvanKuilenburg]

because i want to distinguish between no answer and busy to connect through

 

[SY]

because i want to distinguish between no answer and busy to connect through

Could you please specify expected call scenario and conditions appeared there?
What is the "no answer" in case if both(100 and 101) extensions ring?
What is the "busy" if both extensions(100 and 101) should, supposedly, ring?

Thanks

 

[MarcelvanKuilenburg]

what i want is that the 2 ext at the reception ring together. if neither is picked up (no answer) the call should go to DR.
if both are busy, the call should go to a queue. I hope i explained this in an understanding way.

thx

 

[mfm]

Yes it more clear now but I am still unable to understand what you are trying to achieve, there is only a "destination if no answer " option for both ring groups and ques. So you cannot route it the way your saying. What I would recommend you do is create a queue. And tell the agents involved in answering the calls to log out of the queue so that it will then divert all calls to the DR ( as per forwarding rule ). You could then set the queue wait time to for example 4 minutes so if no one answers it goes to the DR ( good if an agent forget to log out of queue).

 

[MarcelvanKuilenburg]

mfm. thanks. But I still have the problem that if I want to connect ext 100 to DR and do forwarding rule other than rule type 'forward all' p.e. rule type 'no answer', the message as above mentioned is playing. Connection to p.e. DR is not playing. What is it I do wrong.

 

[SY]

mfm. thanks. But I still have the problem that if I want to connect ext 100 to DR and do forwarding rule other than rule type 'forward all' p.e. rule type 'no answer', the message as above mentioned is playing. Connection to p.e. DR is not playing. What is it I do wrong.

"the person you are trying to reach is not available. please leave a message" is not a prompt from 3CX PBX. Do you use customized prompt set?

Could you please provide call log and specify phone model (ext 100)? It will help us to avoid a search for a grey cat in a dark room.

Thanks

 

[MarcelvanKuilenburg]

kindly place your server logs in code and /code brackets- mfm

19:44:59.992  [MS105000] C:22.8: No RTP packets were received:remoteAddr=127.0.0.1:40626,extAddr=0.0.0.0:0,localAddr=127.0.0.1:7454
19:44:58.960  [CM503008]: Call(22): Call is terminated
19:44:58.945  [CM505001]: Ext.801: Device info: Device Identified: [Man: 3CX Ltd.;Mod: 3CX IVR;Rev: General] Capabilities:[reinvite, replaces, able-no-sdp, recvonly] UserAgent: [3CX IVR] PBX contact: [sip:[email protected]:5060]
19:44:58.945  [CM503002]: Call(22): Alerting sip:[email protected]:40600;rinstance=391d211b390d5dff
19:44:58.867  [CM503003]: Call(22): Call to sip:[email protected] has failed; Cause: 487 Request Terminated; from IP:192.168.128.100:5064
19:44:58.820  [CM503025]: Call(22): Calling Ext:Ext.801@[Dev:sip:[email protected]:40600;rinstance=391d211b390d5dff]
19:44:58.804  [CM503005]: Call(22): Forwarding: Ext:Ext.801@[Dev:sip:[email protected]:40600;rinstance=391d211b390d5dff]
19:44:58.804  [CM503003]: Call(22): Call to sip:[email protected] has failed; Cause: 487 Request Terminated; from IP:192.168.128.100:5063
19:44:58.726  [CM503003]: Call(22): Call to sip:[email protected] has failed; Cause: 487 Request Terminated; from IP:192.168.128.100:5061
19:44:53.289  Active calls counted toward license limit: [22]
19:44:39.227  [CM505001]: Ext.100: Device info: Device Identified: [Man: Linksys;Mod: SPA Series;Rev: General] Capabilities:[reinvite, no-replaces, able-no-sdp, recvonly] UserAgent: [Linksys/SPA962-6.1.5(a)] PBX contact: [sip:[email protected]:5060]
19:44:39.227  [CM503002]: Call(22): Alerting sip:[email protected]:5064
19:44:39.211  [CM505001]: Ext.100: Device info: Device Identified: [Man: Linksys;Mod: SPA Series;Rev: General] Capabilities:[reinvite, no-replaces, able-no-sdp, recvonly] UserAgent: [Linksys/SPA962-6.1.5(a)] PBX contact: [sip:[email protected]:5060]
19:44:39.211  [CM503002]: Call(22): Alerting sip:[email protected]:5062
19:44:38.789  [CM505001]: Ext.100: Device info: Device Identified: [Man: Linksys;Mod: SPA Series;Rev: General] Capabilities:[reinvite, no-replaces, able-no-sdp, recvonly] UserAgent: [Linksys/SPA962-6.1.5(a)] PBX contact: [sip:[email protected]:5060]
19:44:38.789  [CM503002]: Call(22): Alerting sip:[email protected]:5065
19:44:38.774  [CM505001]: Ext.100: Device info: Device Identified: [Man: Linksys;Mod: SPA Series;Rev: General] Capabilities:[reinvite, no-replaces, able-no-sdp, recvonly] UserAgent: [Linksys/SPA962-6.1.5(a)] PBX contact: [sip:[email protected]:5060]
19:44:38.774  [CM503002]: Call(22): Alerting sip:[email protected]:5063
19:44:38.758  [CM505001]: Ext.100: Device info: Device Identified: [Man: Linksys;Mod: SPA Series;Rev: General] Capabilities:[reinvite, no-replaces, able-no-sdp, recvonly] UserAgent: [Linksys/SPA962-6.1.5(a)] PBX contact: [sip:[email protected]:5060]
19:44:38.758  [CM503002]: Call(22): Alerting sip:[email protected]:5061
19:44:38.743  [CM505001]: Ext.100: Device info: Device Identified: [Man: Linksys;Mod: SPA Series;Rev: General] Capabilities:[reinvite, no-replaces, able-no-sdp, recvonly] UserAgent: [Linksys/SPA962-6.1.5(a)] PBX contact: [sip:[email protected]:5060]
19:44:38.743  [CM503002]: Call(22): Alerting sip:[email protected]:5060
19:44:38.633  [CM503025]: Call(22): Calling Ext:Ext.100@[Dev:sip:[email protected]:5062]
19:44:38.633  [CM503025]: Call(22): Calling Ext:Ext.100@[Dev:sip:[email protected]:5065]
19:44:38.633  [CM503025]: Call(22): Calling Ext:Ext.100@[Dev:sip:[email protected]:5064]
19:44:38.618  [CM503025]: Call(22): Calling Ext:Ext.100@[Dev:sip:[email protected]:5060]
19:44:38.618  [CM503025]: Call(22): Calling Ext:Ext.100@[Dev:sip:[email protected]:5063]
19:44:38.602  [CM503025]: Call(22): Calling Ext:Ext.100@[Dev:sip:[email protected]:5061]
19:44:38.602  [CM503004]: Call(22): Route 1: Ext:Ext.100@[Dev:sip:[email protected]:5061,Dev:sip:[email protected]:5063,Dev:sip:[email protected]:5060,Dev:sip:[email protected]:5064,Dev:sip:[email protected]:5065,Dev:sip:[email protected]:5062]
19:44:38.602  [CM503010]: Making route(s) to <sip:[email protected]:5060>
19:44:38.602  [CM505003]: Provider:[prionet_84] Device info: Device Not Identified: User Agent not matched; Capabilities:[reinvite, replaces, able-no-sdp, recvonly] UserAgent: [Sippy] PBX contact: [sip:[email protected]:5060]
19:44:38.586  [CM503001]: Call(22): Incoming call from None@(Ln.10006@prionet_84) to <sip:[email protected]:5060>
19:44:38.446  [CM503012]: Inbound office hours rule (unnamed) for 10006 forwards to DN:100

the phone is a linksys/cisco spa 962 +932

 

[SY]

19:44:38.633 [CM503025]: Call(22): Calling Ext:Ext.100@[Dev:sip:[email protected]:5062]
19:44:38.633 [CM503025]: Call(22): Calling Ext:Ext.100@[Dev:sip:[email protected]:5065]
19:44:38.633 [CM503025]: Call(22): Calling Ext:Ext.100@[Dev:sip:[email protected]:5064]
19:44:38.618 [CM503025]: Call(22): Calling Ext:Ext.100@[Dev:sip:[email protected]:5060]
19:44:38.618 [CM503025]: Call(22): Calling Ext:Ext.100@[Dev:sip:[email protected]:5063]
19:44:38.602 [CM503025]: Call(22): Calling Ext:Ext.100@[Dev:sip:[email protected]:5061]

Is it expected that your phone registers itself 6 times on PBX and all accounts are account of the extension 100?
How to configure a Linksys/SPA962-6.1.5(a) to do it?
Thanks

 

[MarcelvanKuilenburg]

Yes, 6 incoming/outgoing lines on ext. 100.

You can configure this in the configuration file of the 962 als admin and advanced. then under tab PHONE you make each line key an extension. furthermore under tab ext1 etc, make the line enabled.

 

[SY]

Yes, 6 incoming/outgoing lines on ext. 100.

You can configure this in the configuration file of the 962 als admin and advanced. then under tab PHONE you make each line key an extension. furthermore under tab ext1 etc, make the line enabled.

This question is not directly related to the issue:
What is the reason to have 6 accounts registered as the same extension from one phone? Why is not acceptable to register only one?

 

[MarcelvanKuilenburg]

dear all, after the remark that the mentioned voice reply was not standard I checked with the provider. Unfortunately there were some points (UM and forwarding) clicked on. After put them off everything is working well.

PROBLEM SOLVED

everybody thanks for the help

 

[SY]

dear all, after the remark that the mentioned voice reply was not standard I checked with the provider. Unfortunately there were some points (UM and forwarding) clicked on. After put them off everything is working well.

PROBLEM SOLVED

everybody thanks for the help

Thanks for your tolerance to the "fuzzy" comments provided in this topic