17 Nov
2015
17 Nov
'15
6:55 p.m.
Hi,
Sorry to ask something probably very simple but I'm difficulty finding
the right kinds of resources to learn from which are succinct enough to
not overload my head.
We have a PBX which we don't control (and hate) which expects only
certain makes/models phones to register (it checks for user agents).
I have a phone which unfortunately doesn't support tweaking its user
agent, so I'd like to pass it through an extremely SIP proxy to have
it's user agent tweaked and all other data to/from the PBX transparently
let through.
I've managed to knock up something (that isn't a proxy) using Asterisk
where I made a trunk and a peer... but obviously since this isn't a
proxy... things like BLF and transferring calls will never work.
If anyone can point me in the direction of a really simple set up to
achieve this, please let me know :)
--
Steven Maddox
18 Nov
18 Nov
11:57 a.m.
Hello,
does the pbx support Path extension (see path module of kamailio for
more details)? If yes, then it should be a rather simple setup of an
edge proxy. A starting point can be the kamailio.cfg example from
dispatcher module:
http://kamailio.org/docs/modules/4.3.x/modules/dispatcher.html#dispatcher.e…
You seed few changes:
- add path headers for REGISTER requests and relay the REGISTER
requests to PBX
- any other sip traffic not coming from PBX, relay it to pbx
- handle initial requests coming from PBX based on Route header
If in dispatcher table you add a single destination address (the PBX),
the you can just reuse the part with dispatcher in that config.
Cheers,
Daniel
On 17/11/15 17:55, Steven Maddox wrote:
Hi,
Sorry to ask something probably very simple but I'm difficulty finding
the right kinds of resources to learn from which are succinct enough to
not overload my head.
We have a PBX which we don't control (and hate) which expects only
certain makes/models phones to register (it checks for user agents).
I have a phone which unfortunately doesn't support tweaking its user
agent, so I'd like to pass it through an extremely SIP proxy to have
it's user agent tweaked and all other data to/from the PBX transparently
let through.
I've managed to knock up something (that isn't a proxy) using Asterisk
where I made a trunk and a peer... but obviously since this isn't a
proxy... things like BLF and transferring calls will never work.
If anyone can point me in the direction of a really simple set up to
achieve this, please let me know :)
--
Daniel-Constantin Mierla
http://twitter.com/#!/miconda - http://www.linkedin.com/in/miconda
Book: SIP Routing With Kamailio - http://www.asipto.com
Kamailio Advanced Training, Nov 30-Dec 2, Berlin - http://asipto.com/kat
24 Nov
24 Nov
1:25 p.m.
Hi,
I do not know if it supports Path extension. I am looking for a
solution which doesn't require knowledge of the PBX anyway, so the PBX
could be anything.
/-------\ /----------\ /-----\
| Phone | ---> | Kamailio | ---> | PBX |
\-------/ \----------/ \-----/
In this set up... any/all communications between Phone and PBX that
would normally be direct - are preserved entirely. The only thing I
want Kamailio to do is change the user agent that the Phone is appearing
to use, allowing it to register with the strict/fussy PBX.
I am wondering if this means the Phones configuration has to use for a
registration server/outbound proxy... an IP/hostname of Kamailio's.
Or if perhaps the Phones configuration can stay the same (as though
Kamailio wasn't there and it directly connected to the PBX... and
Kamailio acts silently in a transparent bridge on a port perhaps?
I'd like to try what you've previously suggested, but it is just way too
over my head at this early stage in my knowledge of Kamailio. Is there
something simpler I can start with an work my way up?
Steven Maddox
On 18/11/15 09:57, Daniel-Constantin Mierla wrote:
Hello,
does the pbx support Path extension (see path module of kamailio for
more details)? If yes, then it should be a rather simple setup of an
edge proxy. A starting point can be the kamailio.cfg example from
dispatcher module:
http://kamailio.org/docs/modules/4.3.x/modules/dispatcher.html#dispatcher.e…
You seed few changes:
- add path headers for REGISTER requests and relay the REGISTER
requests to PBX
- any other sip traffic not coming from PBX, relay it to pbx
- handle initial requests coming from PBX based on Route header
If in dispatcher table you add a single destination address (the PBX),
the you can just reuse the part with dispatcher in that config.
Cheers,
Daniel
On 17/11/15 17:55, Steven Maddox wrote:
Hi,
Sorry to ask something probably very simple but I'm difficulty finding
the right kinds of resources to learn from which are succinct enough to
not overload my head.
We have a PBX which we don't control (and hate) which expects only
certain makes/models phones to register (it checks for user agents).
I have a phone which unfortunately doesn't support tweaking its user
agent, so I'd like to pass it through an extremely SIP proxy to have
it's user agent tweaked and all other data to/from the PBX transparently
let through.
I've managed to knock up something (that isn't a proxy) using Asterisk
where I made a trunk and a peer... but obviously since this isn't a
proxy... things like BLF and transferring calls will never work.
If anyone can point me in the direction of a really simple set up to
achieve this, please let me know :)
3286
days inactive
3293
days old
2 comments
2 participants
participants (2)
-
Daniel-Constantin Mierla -
Steven Maddox