[SIPForum-discussion] ACME: SIP header manipulation
Santosh Iyer
spi6281 at yahoo.com
Wed May 2 18:41:27 UTC 2012
Clarifying the earlier statement... It might be possible to come up with a HMR on the ACME SBC based on some scheme/code, but not sure how much CPU intensive it might become, thats the reason for the discouragement.
Santosh.
--- On Sun, 4/29/12, Michael Muller <excelsio at gmx.com> wrote:
From: Michael Muller <excelsio at gmx.com>
Subject: [SIPForum-discussion] ACME: SIP header manipulation
To: discussion at sipforum.org
Date: Sunday, April 29, 2012, 1:04 PM
Hello,
my users want to dial SIP-URIs on their phones. The devices themselves
are able to do so, i.e. they actually send out the correct URI.
Unfortunately the PBX doesn´t accept non E.164 numbers for routing, it
simply rejects the invite. According to the manual, the only characters
it accepts are: 0-9, A-F,*,#
So, if the PBX needs those ones, let´s deliver it.
Idea:
- Take a SIP-URI (e.g. sip:bob-m.mulder at foreigndomain.com) and translate
each character. Let´s take ASCI and put in some "*". So the user dials:
"*098*111*098*045*109*046*109*117*108*100*101*114@@foreigndomain.com".
(hint: the "sip:" part is automatically added on the phones)
- Hopefully the PBX accepts this and it simply forwards it to the ACME SBC.
Question:
- Will the ACME be able to translate it back to
"bob-m.mulder at foreigndomain.com" and will actually setup and hold the
connection?
Hopefully, it is clear what I´d like to achieve. It´s just an idea, so
it would be great if you could give some hints. If ACME isn´t able to do
so, which software could make it?
Michael
_______________________________________________
This is the SIP Forum discussion mailing list
TO UNSUBSCRIBE, or edit your delivery options, please visit http://sipforum.org/mailman/listinfo/discussion
Post to the list at discussion at sipforum.org
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://sipforum.org/pipermail/discussion/attachments/20120502/c652440e/attachment-0002.html>
More information about the discussion
mailing list