NPD for outgoing after comming in on qsig

Post Reply
zanex
Member
Posts: 395
Joined: 23 Feb 2007 00:32
Location: sydney
Contact:

NPD for outgoing after comming in on qsig

Post by zanex » 10 Oct 2007 22:56

I have a problem that i cant see to solve
I have a 4400 with connections to pstn and qisg connections to a cisco h323 VG.

I am sending a call from another PBX to the voice gateway with a prefix so that it knows that this is call to break out to pstn. I am trying to translate the calling part from the 5 digit internal xtn to a the ISDN's 1st number.

incomming call

Code: Select all

calling party 65602
called party 081887542918
0 ars prefix 8188754 exists as a descrim rule and send to ARS with npd 35 and digit strip 1

npd 35 has installed number sources as npd and i have the number that i want to send in there of 299750500

outgoing call

Code: Select all

calling party 65602
called number 18875542918
why is that not taking effect?
Not All Those Who Wander Are Lost

vad
Alcatel Unleashed Certified Guru
Alcatel Unleashed Certified Guru
Posts: 3461
Joined: 23 Sep 2004 06:47
Location: Russia

Re: NPD for outgoing after comming in on qsig

Post by vad » 10 Oct 2007 23:10

From my practice - you can do something with calling number only in one case - incoming call from TG ISDN all country, where private=yes and network mode=yes.
In another case PBX do nothing with calling number (or send default number from Entity/NPD depends of sigalling protocol for outgoing TG).
I have some case where we manage QSIG from one end and ISDN on another end (for calling number conversion). :lol:
In last case you need to manage some Ignore=yes in system and not send "Status" in ext. sign. parameters.
From my point of view the best way - ask incoming system to send different calling number for transit and local calls.

User avatar
alex
Senior Member
Posts: 1328
Joined: 06 Jul 2004 07:27
Location: Russia
Contact:

Re: NPD for outgoing after comming in on qsig

Post by alex » 11 Oct 2007 04:22

Hi zanex
Which byte 3 CISCO sends to OXE? If it is 00 (Unknown/Unknown) then calling number from i/c call is just copied to o/g call setup.
OXE will take care of translating network numbers if byte 3 says "Private numbering plan" (09).
In all other cases, e.g., "Unknown" OXE will simply copy the number to outgoing call setup.
Also you should manage in local parameters of QSIG TG

Code: Select all

  Charge Calling And ADN Creation + YES 
And manage an entity for QSIG TG with installation number to be appended to calling number.
See an example of my trace. Sbs on 2555 on i/c QSIG TG calls to T2 o/g TG with seizure prefix "9"

Code: Select all

______________________________________________________________________________
| (074939:000227) Physical-Event :
| long: 52  desti: 0  source: 0  cryst: 1  cpl: 6  us: 0  term: 0  type a5
| tei: 0  >>>>  message received : SETUP [05]    Call ref :  00 16
|______________________________________________________________________________
|
| IE:[04] BEARER_CAPABILITY (l=3) 80 90 a3
| IE:[18] CHANNEL (l=3)  a1 83 98 -> T2 : B channel 24 preferred
| IE:[1e] PROGRESS_ID (l=2) 80 83
| IE:[6c] CALLING_NUMBER (l=6)  ->  09  81  Num : 2555
| IE:[70] CALLED_NUMBER (l=2)  ->  80  Num : 9
| IE:[7d] HLC (l=2) 91 81
| [95] Locking shift. codeset : 5
| IE:[32] EI_PARTY_CATEGORY (l=1)  -> EXTENSION (1)
|______________________________________________________________________________

 ______________________________________________________________________________
| (074939:000228) 1165: Send_IO1 (link-nbr=1, sapi=0, tei=0) :
| long: 23  desti: 0  source: 15  cryst: 1  cpl: 6  us: 8  term: 0  type a5
| tei: 0  <<<<  message sent : SETUP ACK [0d]  Call ref :  80 16
|______________________________________________________________________________
|
| IE:[18] CHANNEL (l=3)  a9 83 98 -> T2 : B channel 24 exclusive
|______________________________________________________________________________

 ______________________________________________________________________________
| (074939:000229) 1165: Send_IO1 (link-nbr=1, sapi=0, tei=0) :
| long: 51  desti: 0  source: 15  cryst: 1  cpl: 3  us: 8  term: 0  type a5
| tei: 0  <<<<  message sent : SETUP [05]    Call ref :  00 0f
|______________________________________________________________________________
|
| IE:[04] BEARER_CAPABILITY (l=3) 80 90 a3
| IE:[18] CHANNEL (l=3)  a9 83 91 -> T2 : B channel 17 exclusive
| IE:[1e] PROGRESS_ID (l=2) 80 83
| IE:[6c] CALLING_NUMBER (l=13)  ->  00  81  Num : 78127552555
| IE:[7d] HLC (l=2) 91 81
|______________________________________________________________________________

pax
Member
Posts: 19
Joined: 03 Mar 2015 04:59

Re: NPD for outgoing after comming in on qsig

Post by pax » 27 Nov 2015 06:03

I have the exact same issue, but in my case the call originate from a Lync server via SIP trunk instead. In the SIP protocol the term “byte 3” does not exist. How can you in the SIP protocol set an incoming calling number to be apart on a “private numbering plan” so the OXE NPD table will manipulate the calling number when the call is forwarded over the ISDN to the public operator?

Post Reply

Return to “Translator”