ISDN to SIP

[krzysioD]

Hello,
maybe a strange but question how you guys would do it the right way:
many different numbers from PSTN (standard T2 ISDN trunk) should go to SIP trunk.

just create many abbreviated numbers and route this into sip gateway? anyway not to use separate ARS list etc... ?

[MrAnMo]

Use a network prefix.

I think you have already:
Sip trunk
External Sip Gateway


All you have to do is:
put the nr of the external sip Gateway in a network routing number.
Create a prefix with meaning network no.
network number is your network routing number
node /abcf trunk nr is your siptrunk nr.

Now every new ddi nr which have to go to the siptrunk is just a simple creation of a new network no prefix.
Or if you have a bunch like 3600 to 3699 create a prefix 36 with meaning routing nr. nr of digits is 4.

[krzysioD]

I think, i'm to stiupid to understand this:
1332501234 -> Retry: Waiting for the trunk group to be declared (SIP_CH_READY).

[FN_DK]

Sorry to break in with a diffrent subject on this thread but maybe some of you are able to help me with a problem.

I have:

OXE R10.1
Ext. SIP Gateway
ISDN SIP Trunk
T2 ISDN to public provider with PRA T2

I have setup the call flow between the Ext. SIP Gateway and the T2 ISDN Public. They all work fine. I am able to make internal and external call both ways.


Basiclly the problem is about CLI (Caller ID). When a call is coming from the Ext. SIP Gateway and going out the T2 ISDN public trunk the user ID is showen:

From: "User, User" <sip:4384@10.64.48.201:5060>;tag=922849CEF99D9742989CEC26CBB32805

And as I can see, that is not a good thing sending out 4384 on a public trunk....

So my main question: Can you change it?

I have tried working with ARS routes, Entitys, trunk settings ect ect. Nothing seems be affecting this caller ID issue.

Best Regards