Calling number modification?!
Re: Calling number modification?!
If number absent - what managed in Ext. callback translation (at least DEF-0 must be present).
Re: Calling number modification?!
This table is empty - what should i put there?
UPD! The doc (/cdrom/content/1_1_7_1_5.html#dm09011b0280003dc0.xmls2) says that if I use the External Callback translation table, I should route incoming calls (from PSTN) via ARS, not direct seizure. My current setup is based on direct seizure (see above) and I'm afraid to break the inward dialing...
UPD! The doc (/cdrom/content/1_1_7_1_5.html#dm09011b0280003dc0.xmls2) says that if I use the External Callback translation table, I should route incoming calls (from PSTN) via ARS, not direct seizure. My current setup is based on direct seizure (see above) and I'm afraid to break the inward dialing...
Re: Calling number modification?!
DEF-0 helped!!!!!!! Vad, you're the Incredible. Who but you could suggest this?!
However I noticed some strange behaviour on incoming (from PSTN) transit calls now. I'm playing with my setup, switching the client's PBX from one PRA/T2 card to another (old trunk group remains untouched). So the incoming calls are routed to the old TG for a while. And despite the TG is totally out of service (RJ45 unplugged) the caller hears the calling tone (КПВ)!!! I'm pretty sure that this is NOT the way it behaved before. Is it ok?!
However I noticed some strange behaviour on incoming (from PSTN) transit calls now. I'm playing with my setup, switching the client's PBX from one PRA/T2 card to another (old trunk group remains untouched). So the incoming calls are routed to the old TG for a while. And despite the TG is totally out of service (RJ45 unplugged) the caller hears the calling tone (КПВ)!!! I'm pretty sure that this is NOT the way it behaved before. Is it ok?!
Re: Calling number modification?!
Check private TG parameter:
- public network COS - inconing DID overflow on total busy=0.
- public network COS - inconing DID overflow on total busy=0.