Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations bkrike on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

Placetel with IPO 2

Status
Not open for further replies.

LJDirk

Programmer
Jun 14, 2002
157
DE
Hello Board,

did anybody know, how i can configure the SIP Provider "Placetel" to the IPO in Germany?
My Problem is, that i can´t do inbound calls. Outbound work fine.

In the Moni i see, that die IPO send "404 - not found" (Reason: Q.850;cause=1;text="Unallocated (unassigned) number") to the provider.
I don´t unterstand yet, how IPO work internal with "SIP-URI", "incomming Number-assignment" and "SIP-Line". The "help" is more bad, than right at this point...

Any Solution?

(QSC is working well on the IPO...)
 
Maybe 2 x SIP URI will do the trick for you.

First:
Put in * in Local URI/Contact/Display Name. This will make calls match ICR for the Trunk group as you are used to.
Incoming Group: 17 (this will be the Line Group ID in your ICR)
Outgoing Group: 99
Channels: As many as you are licensed for

Second:
Leave all default except for these three:
Incoming Group: 99
Outgoing Group: 17
Channels: As many as you are licensed for

Kind regards

Gunnar
__________________________________________________________________
Hippos have bad eyesight, but considering their weight, it’s hardly their problem

2cnvimggcac8ua2fg.jpg
 
i´m feeling ... happy, happy, happy

great thanks for this! It work.
 
How absolutely wonderful for you [smile]

As you are on a happy trip, how about handing over that pink star? (not feeling modest today) [smile]

Kind regards

Gunnar
__________________________________________________________________
Hippos have bad eyesight, but considering their weight, it’s hardly their problem

2cnvimggcac8ua2fg.jpg
 
Ahhh, thank you! :)

You should take a look at Placetel support pages, they have some hints and tips for setting up trunks. P asserted, etc....

Kind regards

Gunnar
__________________________________________________________________
Hippos have bad eyesight, but considering their weight, it’s hardly their problem

2cnvimggcac8ua2fg.jpg
 
Hi, now we implement on Customer Side.

Problem: the Customer have four Numbers from Placetel. Not as Trunking (how i tested) because as "normal Numbers".
In the SIP Invite we don´t see any Numbers only the Reg.Data. IPO pick allways the first Line are configured. We can´t route the diffrent Numbers.

How we can route the diffrent Placetelnumbers to diffrent targets in VMpro (VM:xxx)? Any Ideas?
 
No incoming numbers? I'd love to see a trace of that.

Code:
INVITE sip:0221123445@fpbx.de SIP/2.0.
...
From: <sip:777zXXXXX@fpbx.de>;tag=ac184a8-0-13c4-50022-1912b-72623b10-1912b.
To: <sip: 0221123445@fpbx.de>.
...
Contact: <sip: 777zXXXXX@78.158.7022:61016>.
...
P-Preferred-Identity: <sip:0221999998@fpbx.de>.
...

Have you searched the Placetel support section?
Looks like you have to configure the trunk on the far end yourself, aber ich bin ausländer und spreche nicht gut Deutsch....[smile]

Your ICR needs:

- A Line Group ID (the number you assigned the SIP trunk, probably 17)
- An Incoming Number (the DDI, zum Beispiel 0221123445 oder 022112XXXX)
- A Destination (This could be VM:xyz, extn number, # -for best match to XXXX above)

Kind regards

Gunnar
__________________________________________________________________
Hippos have bad eyesight, but considering their weight, it’s hardly their problem

2cnvimggcac8ua2fg.jpg
 
Ich auch ;-)

The Solution: in the "incomming Number" Field you must insert: "sip:77740xxxxx". Then the IPO can route the call to the right destination. This is not a trunking (fpbx.de - that i´ve tested) from Placetel, but one Number from the Provider - see the diffrent domain. One Number - one registration. Here by the Customer: four Numbers, four Registrations.
The IPO route in default config to the URI. Here stand: "sip:77740xxxxx". Same in the "to: Header".

That´s all (after a Nightwork...)


Code:
INVITE sip:77740xxxxx@192.168.85.20:5060;transport=udp SIP/2.0
                    Record-Route: <sip:62.134.52.210;ftag=as292b3ec4;avp=igIBCgBhY2NvdW50aW5nAQAAAA;lr=on>
                    Via: SIP/2.0/UDP 62.134.52.210;branch=z9hG4bKc13b.d2c4cb92.0
                    Via: SIP/2.0/UDP 62.180.25.131:7018;branch=z9hG4bK3e8b2a1c;rport=7018
                    Max-Forwards: 69
                    From: "yyyyyyyyyyyyyyy" <sip:yyyyyyyyyyyyyyy@sip.finotel.com>;tag=as292b3ec4
                    To: <sip:77740xxxxx@sip.finotel.com:5060>
                    Contact: <sip:yyyyyyyyyyyyyyy@62.180.25.131:7018>
                    Call-ID: 5c2a40a449608c5f18af483047be9897@sip.finotel.com
                    CSeq: 103 INVITE
                    User-Agent: PlacetelPBX
 
Sounds like a pimped analog trunk, meant as direct line to a single sip phone.
Can't say I've tried that on an IPO before.

Then you need to make four lines and four ICR's.



Kind regards

Gunnar
__________________________________________________________________
Hippos have bad eyesight, but considering their weight, it’s hardly their problem

2cnvimggcac8ua2fg.jpg
 
Can't say I understand why the provider would set it up like that, unless the IPO serves 4 different companies.
But it works now, right?

Kind regards

Gunnar
__________________________________________________________________
Hippos have bad eyesight, but considering their weight, it’s hardly their problem

2cnvimggcac8ua2fg.jpg
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top